Hi there! I developed a batch image processing plug-in for GIMP 3.

Main features:
* Convert image files to any file format provided by GIMP and third-party plug-ins
* Export images opened in GIMP
* Batch-edit images opened in GIMP and/or save them to the native XCF format
* Export layers as separate images from an opened image
* Batch-edit layers in an opened image
* Apply any filter or plug-in during batch processing (rename, scale, ...)
* Process only images/layers matching your criteria (ending with a suffix, visible layers, ...)

More information and download: https://kamilburda.github.io/batcher/

In my opinion this plugin is much better than BIMP (and Bimp is not available for GIMP-3.0.0).
And a request right away, if possible:
a slightly larger (x3?) start preview:



I know I can stretch the window, but it's a bit of a waste of time.

If it helps, you can save settings (Ctrl+S or Settings -> Save Settings), which will remember the dialog size and the positions of the separators. If you make use of "Save Settings to File..." to switch between multiple configurations, loading settings should by default keep the dialog size and the positions intact, unless you check "Load size-related settings".

I realize the preview may be a tad too small for some users, it's just that I find it difficult to strike a good balance between the input list height (some users may work with more than a few layers/images) and the preview height. I suppose I could increase the overall dialog height and the preview a bit, though.

Thank you, Kamil!

Thank you for your valuable advice.

However, maybe a small compromise - a larger preview and a scroll bar for the file list(Input)?

If this requires a lot of changes to the code, forget about my request.

edit:
I'm not used to the fact that in Gimp 3 the scroll bar is visible only after hovering the cursor.

This plugin should be in GIMP automatically.
The option to preview the effect while specifying individual parameter values is amazing.
Processing and combining PDB (including filters GEGL and G'MIC) has never been easier.



What is worth emphasizing is that the saved additional procedures (preset.json) will create a new filter that can be easily shared with other users. If you master BATCHER, you do not need any programming knowledge to create your own 'plugins' (something much better than Action [*.atn] in PS).

Problem with G'MIC filters:
1. Add 2 arbitrary/different Gmic procedures to Edit Layer.





2. Check if they work without error.
3. When OK save settings to file.



4. Reset settings.
5. Load settings from file - it loads only 1 procedure.




Also, if you add more than 2 G'MIC procedures after saving - it loads only 1 last one on the list.
No error message.

Such a problem does not occur in Export Layer for Gimp-2.10.xx
Ver.4.1 https://github.com/kamilburda/gimp-export-layers
By the way: is there a chance to add GEGL support to this version?
Gimp 2.10.xx will not have NDE and this plugin can replace it perfectly.

And one more opinion of mine:
The option when Edit layers and their exports are in one window is much more functional (in Batcher, they are separate windows and the settings saved for them are not compatible among themselves).
-------------------------------------------------------------------------------------

The more I test, the more annoying it becomes when I see in "Edit Layers" saved with a success message - Procedures performed correctly, (not just from GMIC), but then it doesn't load json them.

Unfortunately I can't find a rule why it performs additional procedures correctly, writes the json file but cannot always read it.

Reported here:
https://github.com/kamilburda/batcher/issues

Unfortunately, it cannot be ruled out that the save/open problem lies in the GIMP-3.0.0-1 Win10 64bit itself (users report problems with opening saved graphic files).

First off - thank you both for the kind words. ☺️

As for the bug with disappearing procedures, thanks for finding this, I'll fix this in the next release.

As I said, I'll consider increasing the preview size, at least for Edit Layers, where the user may be much more reliant on how the resulting image looks like after applying a set of filters. Conversely, for the export procedures, I expect users to care more about file format settings and some less "invasive" changes to the images like renaming and resizing, where the preview does not have to be that large. Or maybe my assumptions are all wrong.

Due to my time constraints and other commitments, I'm afraid I won't be able to dedicate my time to maintain Export Layers anymore.

As for exporting and editing of layers in a single dialog, can you elaborate on your workflow (i.e. how you tinker with layer editing and then perform layer export)? In Batcher, I made the decision to split exporting and editing into separate dialogs so that Edit Layers is more discoverable (it was hidden previously under Settings). I could perhaps create a more visible switch between edit and export mode, but I'm afraid it would clutter the GUI and add some confusion. For example, the Resize to layer size procedure is applicable only for Export Layers and it would have to be disabled for Edit Layers (it would otherwise keep resizing the image canvas as it goes through each layer until the image canvas is resized to the dimensions of the last layer).

You can always have both Export Layers and Edit Layers opened at once. They do not share settings, so you don't have to worry about settings being overridden if you save them (with ctrl+S or to a JSON file). If you renamed/added/removed layers in GIMP and you switched back to the Export or Edit Layers dialogs, the list of layers will be automatically refreshed.

Thank you very much for your answer.
I decided to spend more time with Gimp 3, mainly because of BATCHER and support for GEGL operations.
I will wait patiently for the possible addition of this functionality to EksportLayers in Gimp-2.10.38.
I am testing quite extensive procedures in Edit Layer - could this be the reason that the json file is saved but sometimes cannot be loaded? Or is it just me?
I have downloaded Gimp 3.0.2-1 and if the problem occurs again, I will post the "faulty" json files.

Can Batcher be used with third party GEGL plugins and GEGL syntax from "GEGL Graph" filter?

awesome, I confirmed it detects my plugins and here is an example of batcher calling my plugin "custom bevel" and dropshadow

Batcher rules, I can save everything as a json file and reload it for later user. This is like PS actions!

Much better than actions in PS!
Why?
- because you can easily modify the json file by changing parameter values, changing the order of procedures (dragging) and all this with a current preview of the effect.
However, I will refrain from publishing json files until the next version of BATCHER is released.
The creators of Gimp did not consider the possibility of placing GEGL operations in the browser, but Kamil Burda managed it brilliantly.

New edition

Thanks for the update info MareroQ!

It was hard to diagnose my problems in Edit Layers, because they were two separate problems. Reported here https://github.com/kamilburda/batcher/issues - and very quickly fixed.



I will now open a new thread for sharing settings (Save Settings to File...) between users - ACTIONS BATCHER EDIT LAYERS

Is there a way to save procedures in a more simple text file than .json?

Bimp saves procedures in .bimp files which contain something like this:


Which is way easier to read and modify with a bash script than .json files...

Batcher has a different (better) approach than BIMP.
You edit *.json files in a window with the current preview (without guessing how editing the *.bimp file will affect the result).

Regarding sharing JSON files - that's definitely a great idea! I have plans to improve support for this by allowing to load the saved settings in any plug-in procedure (e.g. saving in Edit Layers and loading the settings in Batch Convert).

There's one thing one should be careful about at the moment - the JSON files may contain file paths (especially when saving settings in Batch Convert), which reveal the user's OS account name and also may hint at the contents of the files, both of which may be perceived as violating privacy. I'll add an option to only save procedures and constraints without the sensitive data and warn the user when attempting to save all settings.

@helixarch Since I plan to provide a lightweight version of the saved settings, I'll see whether I can make the format simpler (e.g. it would be sufficient to just store the parameter names and values instead of all possible attributes). I'd still probably keep it as JSON, though, as implementing a custom format would take quite a while. Out of curiosity, what are your use cases? E.g. whether you are trying to programmatically add new procedures, modify existing parameter values, ...