Testing the latest Gimp 2.10.15 AppImage for Linux. It's based on the upcoming Gimp 2.10.16 and the bumpmap is now fixed, yay!
https://github.com/aferrero2707/gimp-appimage/releases

As you can see, some of the tools are abbreviated into groups. It also has some new button options in the layers window and the opacity slider is narrower. I like the update.

Sometimes worth going to https://github.com/GNOME/gimp/commits to see what is going on.

Missed the date already https://github.com/GNOME/gimp/commit/8b ... a0b8feef50 but will not be far away

Thanks racer, I will be using this appimage. I clicked on 'Assets' and found a long list with the latest ones somewhere in the middle.
This one seems the best on version number, date and plugins:
GIMP_AppImage-git-2.10.15-20200130-withplugins-x86_64.AppImage

No, the latest version with plugins is: GIMP_AppImage-git-2.10.15-20200213-withplugins-x86_64.AppImage.

I actually run the one without plugins and install the latest G'mic using this link: https://github.com/aferrero2707/gimp-pl ... continuous

Thanks for the tip racer. This version works nicely. I find appimages are better than flatpacks which I no longer use. I'll be giving this a good testing.

Latest date for Gimp 2.10.16 is....tomorrow

https://github.com/GNOME/gimp/commit/41 ... a008cbd041

although they say tomorrow never comes.

However, it has come today
18-Feb-2020 20:21

Could anyone tell me if Optimize for Gif has been fixed.
I think it was a reported bug.
Here is a example of the problem.
http://gimpchat.com/viewtopic.php?f=8&t=17795

I downloaded you xcf file, here it is "optimized for gif".

Gimp 2.10.16 isn't out yet, unless you want to compile yourself. The AppImages are updated every two weeks or so, I imagine a 2.10.16 version will be out in a couple of weeks or so. The current 2.10.15 AppImarge it already based on the 2.10.16 code, so in essence you're already there.

Thanks racer, it looks like it's fixed.

I notice there is a Gimp 20.10.19 version made yesterday on the appimage release page.

It asks to integrate to your system when running for the first time. I say yes and it's good to go.
I like it but I find its slower than an integrated Gimp version supplied by the OS. I test with large files of over 1000 layers. G'MIC will crash when doing a job of that size. There must be extra overheads or resources used by an appimage but that would be expected.

The latest release 2.10.19 has the 2.10.20 fix and works great. Essentially it's Gimp 2.10.20 for all intents and purposes.

AppImages use a little more resources because it runs in a virtual drive that contains all needed dependencies. I like Appimages and run quite a few myself. They are very easy to manage, just delete them when you want to uninstall or upgrade. I never allow it to setup in the menu, I do it manually same with all other Appimages I use. I don't have any issues with large files yet.

I am still using Gimp 2.10.14 95% of the time, I do have a portable (sort of ) Gimp 2.8 that comes out occasionally and I do like to try out the development appimage as well. The new compact toolbox is a great improvement.

For those of us who are inveterate dabblers

If usage was the other way around, using the appimage all the time, then I am not happy with unpacking 9000 files (500 MB) into /tmp folder every time I run it.

I might consider this. These appimages can be unpacked into a local folder, basically a permanent installation run from that folder. Might save a bit of wear and tear on your computer SSD drive but these are quite robust these days. Up to you. I might unpack that appimage on my storage partition like this, in a folder gimp-app (can be any name)



Gimp is then run from the folder squashfs-root/ ./AppRun There are still writes to /tmp but only 500 small symbolic links (90 kB)
The appimage still uses the Gimp appimage profile for your personal resources (can be changed but do not advise mixing an older Gimp with Gimp 2.10.16/18/20...)

There it is in action with an old Gimp 2.8 script:



Any snags with that version?
Same as any Gimp 2.10 The nuFraw plugin interferes with loading a SVG (unsupported file format) Disable plug-ins/NUFraw/plug-ins/nufraw-gimp until required.
Liquid-Rescale, totally broken. So far I do not know a fix. G'mic has a seam-carving filter that can be used.
Not at all sure that the bump-map plugin is completely backward compatible. Keep an old plugin handy

Thanks for the post rich2005.
Never knew you could 'install' an appimage

Maybe I'm an 'inveterate dabbler' because I just figured how to get MathMap working in a Gimp 2.10 appimage under linux.
Cheers from down under.

liquid-rescale problem.

This for CtrlAltDel who wanted a replacement liquid-rescale.

This compiled with a fix. Linux, 64 bit, unpack (check permissions) put in the Gimp-appimage user plugins folder.

Thank you rich2005 for the tip on extracting the AppImage, I didn't know you could do that. It works perfectly and is now faster taking less than 3 seconds to load Gimp. I may even try this on other AppImages like Blender.

FYI: The bump-map has been fixed since 2.10.16. I also use the smaller AppImage without plugins and then add just the plugins I want, like G'mic via this link: https://github.com/aferrero2707/gimp-pl ... continuous

Yes, I'm running Gimp 2.10.19 from an installed appimage with MathMap as a plugin currently rendering 720 frames.
This is a very cool outcome IMHO because you can easily go to a later or an earlier Gimp version.
Thanks racer and rich for putting this out there.

BTW rich I use the clearalpha script you wrote often.
I also use offnuts export all PNG's script although don't know how to make shorter filenames like frame001, frame002, etc.
A lot of video editors don't like long filenames.

It's explained in the readme.
For example typing this: layername{numDown1:03d}.png in the layer name field would yield 3 numbered consecutive png images named layername001.png, layername002png and so on.

@Tas_mania

For batch renaming (any files) I use gprename simple enough, even for me. It is in the 'buntu repo.

A script I sometimes use for exporting multiple layers, I have it down as Saul Goode but is with Lauchlin Wilkinson so not on the SG site. Best thing about a script, keep it in ofnuts resource manager for when required. zipped, attached.