GIMP

The developer of the Frequency Separation plugin Chuck Henrich has updated it for GIMP 3.0

It's simple and slick and works really well.

It's great to see development activity for 3.0 plugins and of course a big thanks to the developer 🥰

I would have sworn I read that the developer had an agreement with the GIMP team to just put it into GIMP 3 natively.

Was I imagining things?

If you've never heard of it, it's a plugin that adds "Heal Selection" to GIMP that behaves a lot like the same feature in Photoshop. It's a killer feature! It can also "Heal Transparency", and the plug-in itself can be run manually with many more options. It works really well.

Here's the discussion I found about getting it to work in GIMP 3 under Windows: https://discuss.pixls.us/t/need-help-installing-resynthesizer-plug-in-for-gimp-3-0-in-windows-10/49019/2

In short, the files go into your app settings GIMP folder. The exe goes into "plug-ins" inside a sub-folder named the same as the exe (minus the .exe part), so; plug-ins/resynthesize/resynthesize.exe, and the scm files go loose inside scripts. The scripts will appear in GIMP under Filters/Resynthesize.

[ascii is hard]

I guess I might be the only person on the face of the planet dependent on PhotoGIMP so this might be useful for no-one but just on the offchance...

After updating Gimp to 3 and updating photogimp too, it was for me totally and utterly broken. I don't know enough to say why, but it was. It loaded the new splash screen but when fully loaded the whole interface was the standard Gimp one and all interface tools, layouts etc were also (as far as I could tell) standard Gimp. I searched for answers but couldn't find any. Maybe this is a 'me' issue or maybe the updates are too new or maybe photogimp doesn't have enough of a userbase to notice.

So, I've ended up rolling back to gimp 2.10 and the 2020.1 version of photogimp. However, this is not a straightforward process. Here's what I had to do (assuming flatpak).

Remove all photogimp bits and pieces from $HOME/.var, $HOME/.local and most especially $HOME/.config

DO NOT uninstall Gimp itself.

Then revert gimp 3.02 to 2.10 like so:

First you need the commit id of previous versions of Gimp.

flatpak remote-info --log flathub org.gimp.GIMP

For 2.10 its 83b335255cc239e223ada842f99107d1d6ce51b511a8ae2a278005c2e2809242

So this is technically an update even though we're reverting not upgrading, so Gimp itself still needs to be installed. Might need to sudo the next command.

flatpak update --commit=83b335255cc239e223ada842f99107d1d6ce51b511a8ae2a278005c2e2809242 org.gimp.GIMP

Let it do its thing. When its ready, you can (optionally but I did) tell flatpak to ignore updates like so:

flatpak mask org.gimp.GIMP

When that's all done, open and run gimp and you should now have 2.10

Close Gimp.

Now download photogimp 2022.1 from the releases page, then extract the relevant files into $HOME/.var and $HOME/.local respectively.

Double check $HOME/.config/GIMP is definitely gone.

Open Gimp again and you should have photogimp back to its pre-gimp3 self.

Wasn't my fault after all. GIMP has a quick update to fix the issue for Windows users.

I tried both the "Hello, World" one, and the Goat one.

I saved the "Hello, World" one as C:\Users\Me\AppData\Roaming\GIMP\3.0\plug-ins\py3-hello-world\py3-hello-world.py as instructed. I did the same for the goat one, but named it "goat-exercise-py3". I double-checked the plug-ins folder path in Preferences, and that's one of the two.

Incidentally, the code in the two files are different in regards to initializing the plugins. The Goat one includes ".py" in the call to init, but the "Hello, World" one does not:

GimpUi.init("goat-exercise-py3.py")

plug_in_binary = "py3-hello-world"
GimpUi.init(plug_in_binary)

I tried using the nominal shebang line included, and also tried changing it to an actual path to Python on my system. I can see GIMP attempt to load py3-hello-world.py during startup, but when I create a new file and look for it anywhere in GIMP, including the Procedure Browser, I don't see it.

I've made a few python plugins for GIMP 2 using python fu, and have had no trouble with them, but I can't get either of these demo ones to load. I don't even know where the "Hello, World" one is supposed to show with a menu path like this: "<Image>/Hell_o Worlds", so I changed it to "<Image>/File/Hell_o Worlds" like I've done for custom export scripts I've made for GIMP 2.

Any ideas?

This is a patch for GIMP that makes UI look similar to Adobe Photoshop.

Draft Release Notes: https://testing.gimp.org/release-notes/gimp-3.0.html

Will soon be published to Flathub

I recently started !fakealbumcovers@lemm.ee, and though my previous posts were made with PS, I've committed to using GIMP moving forward!

We'd love to have your image manipulation skills over there, so come check us out.

Just saw on Masto that Resynthesizer will be compatible with GIMP 3.0

I think this is great news. Apart from all the upgrades we'll get in 3.0, it will be an opportunity to create a buzz around GIMP. The more functional it is, the better that buzz will be :)

#GIMP #FOSS #Resynthesizer

I'm often using the Select by Color or Fuzzy Select tool. ¿Is there a quick way to increment the threshold with a keyboard shortcut, the mouse wheel, or similar?

Take the following example:

Given the image of the GIMP mascot, I want to select only certain portions, for instance the outer white part.

To do this I activate the Select by Color or the Fuzzy Select tool. Set the threshold to a starting value (let's say 15), then click on a white part at the edges of the image. But I'm not quite satisfied with the resulting selection: it selects most of the area I want but not enough of the greyish shadow below the chin. So I adjust the threshold to 50 and click again. Still not enough, set to 90 and lick again. A bit too much, set to 80 and click another. Almost there, set to 85 and click. Set to 83 and finally voilá.

That involved a lot of clicking and typing though. ¿Is there a quicker way to do this? Ideally I would like to see a live update of the selection as I change the threshold, so that I can simply drag the slider or scroll the mouse wheel until it's perfect.

Maybe I'm simply using the wrong tool and there's are completely different inroads to achieve this. I'd like to know about those as well.