Gimp Photoshop Plugin

[Hebe Zuelke]

DoesGimp have anything like Photoshop's patch tool?

The healing brush isn't quite what this feature is. I found some cool tutorials on how to use the Photoshop patch tool to fix the dark circles under people's eyes...

11:25AM, 5 March 2009 PDT(permalink)

The resynthesizer plugin gets its filling information from the surrounding area. The same you do when you remove skin irregularities like the mentioned dark circles.

I just tried it with my eyes (sigh) and it works fine, the result is similar.

ages ago(permalink)

You should help us a little more about this plugin, Elsamuko.

It is so slow and memory slurping that I gave up trying it. The two script-fu provided with it are worse: they look like an advertisement for the use of coffee machines and a preview of what eternal life will be.

I have just done a new Windows compilation from the latest sources, but, despite it is lighter than the one in the Gimp repository (I added -s and -mwindows), it does not seem to be faster.

Originally posted ages ago. (permalink)

Franois Collard (a group admin) edited this topic ages ago.

I've tried the resynth tool a few times (getting rid of a copper pipe in the background of a photo, e.g.) and it hasn't done that well for me. Some of the script-fu scripts also don't run to completion :-P

The healing tool is ok but the clever thing about the Photoshop Patch Tool seems to be that it seems to adjust the color gradient of the patch to match what was there (more so than the healing brush does). Google it to see examples of usage. Some people even use it instead of the healing brush.

ages ago(permalink)

Yes. I have just given it some tries under Lnux, and it works OK and fast enough to remove properly an unwanted object. The plugin used alone works better than the "smart remove selection" script and provides more options. But the "samrt-enlarge" script-fu is time and memory consuming, and I always killed the process before it ended.

But Resynthesizer simply does not work under Windows. For instance I tried to remove a bucket on a beach and the selection was filled with the color of the sky. It's the same with the 0.13b Windows binary provided on the official site, the 0.16 binary compiled by Michael Schumacher, and the one I have just compiled. It seems that there is a calculation error of the reference area under Windows.

Originally posted ages ago. (permalink)

Franois Collard (a group admin) edited this topic ages ago.

Sometimes when compiling plugins for Windows, we get weird errors like that.

With the last version of gimp-lqr plugin (0.6.1), we always got a harmless but strange error: the plugin worked, but the "next step" figure was the largest displayable integer. At last Carlo Baldassi was able to install a brand new MinGW on his Linux Windows emulator and compile it, an we got rid of this bug without understanding how.

MinGW is not yet a coherent system, and sometimes one wrong header can cause strange behaviors. As the compilation of some older plugins (even written in 2007) requires old headers, it's very hard to keep a coherent Windows compilation system.

Originally posted ages ago. (permalink)

Franois Collard (a group admin) edited this topic ages ago.

By default, the Move Tool in GIMP is set to Pick a Layer or Guide. With this option set, it is a bit more like Inkscape or Illustrator because you also move things that are not on the current layer (like the background). If you are a long time Photoshop user, this is very strange.

To make it function like Photoshop, you want to set the default to Move the Active Layer.

Once you have the color profiles on your disk, you need to let GIMP know where they are. From the main menu in GIMP, go to Edit => Preferences => Color Management. Make sure Mode of Operation is set to Color Managed Display, and select your RGB and CMYK ICC files in the drop down menus below.

I get your point of switching from photoshop to gimp, but still I feel photoshop is much user friendly thank Gimp. I am very comfortable of using photoshop for all of my editing tasks and designing the creative banner.

Thank you for these infos, would be nice to read more about your working with Gimp and how to overcome limitations. BTW, maybe many readers did not notice that LIGHTZONE is back! Now as a free and open source software! This is a really strong contender to LR, go and take a look:

Regarding Gimp-Inkscape-Scribus vs. Adobe Cloud CS, they are both very useful in their own ways. Adobe has worked hard to make efficient all-digital work flows over the past decade. Since Adobe have revenue from licensing, they can make a much more complete effort to research and implement digital work flows. That being said, I find it fascinating to watch how the OSS teams are tackling the same issues with their much more limited resources. For a volunteer effort, Gimp-Inkscape-Scribus stack has become very capable in recent years. If you are only producing for digital consumption, it can be completely sufficient for many work flows. I still recommend Cloud CS, though, if someone is targeting physical media.

I'm using Spine trial version right now and thinking to purchase it.

I use Clip Studio Paint as my art tool and I just knew that there is no json script plugin for it to export to Spine.

So I have to use one of these products to export to Spine: Adope Products or one of the two free software Gimp or Inkscape.

I tried Gimp and installed "Export to Spine" menu,I conveyed Clip Studio Paint's layers to Gimp, I tried to export but it didn't work, It keeps giving this message

"An error occurred running python-fu-spine-export

TypeError: object of type 'NoneType' has no len()"

Now I will try the same process with InkScape. If it doesn't work either, Adope Products aren't an option to me :doh: and pay monthly fee just to export to Spine or give up on CSP and use Photoshop.

I'm happy with CSP ? . If only the developer team make export script plugin for CSP, It would be wonderful combination to me.

We are in contact with CSP about getting Spine export there. Until then, if CSP can save as GIMP or Photoshop files, that would be good. Can you post or email the GIMP file that doesn't work? con...@esotericsoftware.com Can CSP save as a PSD? The PhotoshopToSpine script is currently the most advanced. You could use Photoshop CS2 to export, available directly from Adobe:

-suite/kb/cs2-product-downloads.html?promoid=19SCDRQK

Thank you for your response Nate. That's a good news to hear that will be a Clip Studio Paint extension plugin to export to Spine :rofl:

And yes, CSP can save as photoshop formate and open it with Gimp.

After two days trying to find the problem, I finally did. The problem was the file should be only layers and no extra stuff with it.

I cleaned up the file and exporting from Gimp to Spine worked!

I will try the link you sent me about CS2, thank you ?

I followed these instructions -scripts/tree/master/gimp

I'm having a problem " export to spine " shows up but i get this error " RuntimeError: Could not open '\tmp\filename.png' for writing: No such file or directory

"

and

GIMP Message

Calling error for procedure 'file-png-save':

Could not open '\tmp\filename.png' for writing: No such file or directory

Over six months ago, I stopped using Adobe Photoshop and switched to the open source alternative, GIMP, for all my personal photography projects. This wasn't the impossible task that most people believe it is.

But times have changed. Photoshop isn't the killer app that it used to be. I spend about 90% of my time in Lightroom and only 10% in Photoshop. This is the same for many other professionals. We've all switched to the RAW format, so we use RAW photo editors most of the time. Photoshop is often just used for final touch ups.

For the reduced role that Photoshop now plays in many photographers' workflows, GIMP is surprisingly capable. However, transitioning to GIMP can be frustrating because the keyboard shortcuts, tools, and interface are different from Photoshop's. Hopefully these setup tips can help make Photoshop users feel much more at home in GIMP.

In this tutorial, we'll be tweaking some configuration files in the GIMP's settings folder. This is in a different place on every system. So, mark down where this folder is, and keep it in mind for future steps:

By simply replacing one configuration file, you can have Photoshop's keyboard shortcuts enabled in GIMP. This, by far, is the most helpful thing I did to make my transition to GIMP easier. In fact, I am almost useless in GIMP without it.

Note: After installing the configuration file, you may have a few shortcuts that conflict with one another, so I recommend going to Edit > Keyboard shortcuts and making sure everything is in line with this chart. I also recommend binding "[" to Decrease Brush Size More, and "]" to Increase Brush Size More to speed up brush size changes.

In Photoshop, CTRL+J can be used for more than just duplicating the current layer, it can make a new layer from the current selection. This is a really handy tool that I use very often in Photoshop. You can add the same function to GIMP's Layer menu with a plugin called Layer via Copy/Cut.

Combining the "Layer via Copy" feature with layer masks is a great way to create composite images in GIMP. The two can also be a capable (but less efficient) replacement to the patch tool in Photoshop.

3a8082e126