State:
Gimp: 2.10.32
OS: Win7 x32-Bit
Processing of tool scripts is unnecessarily slowed down:
Currently it is the case that when batch processing is performed by Gimp via external batch script (tested here especially under Windows), it is noticeable that gimp.exe starts in a new process instance each time, which unnecessarily slows down the repetition of scripts or execution of further commands, since Gimp first uploads all its modules each time - or even worse for each command line in the script. An unnecessary nonsense.
So it would be much more superior and faster, if there would be a parameter here to let gimp.exe load once into RAM and stay there until it is not explicitly removed from there something by (gimp-quit 0).
Under "gimp-2.10.exe --help" however no further parameters are listed at present, which force the execution of the Gimp console in already running instance.
And concretely on the example: A following processing under Windows leads currently per gimp.exe command line a delay of around 5 s, so with next following both command line per gimp.exe thus at least (2* 5 =) ~ 10 s are wasted:
(In addition there is the closing of Gimp, which is also somewhat delayed).
Suggestions for improvement?
Gimp: 2.10.32
OS: Win7 x32-Bit
Processing of tool scripts is unnecessarily slowed down:
Currently it is the case that when batch processing is performed by Gimp via external batch script (tested here especially under Windows), it is noticeable that gimp.exe starts in a new process instance each time, which unnecessarily slows down the repetition of scripts or execution of further commands, since Gimp first uploads all its modules each time - or even worse for each command line in the script. An unnecessary nonsense.
So it would be much more superior and faster, if there would be a parameter here to let gimp.exe load once into RAM and stay there until it is not explicitly removed from there something by (gimp-quit 0).
Under "gimp-2.10.exe --help" however no further parameters are listed at present, which force the execution of the Gimp console in already running instance.
And concretely on the example: A following processing under Windows leads currently per gimp.exe command line a delay of around 5 s, so with next following both command line per gimp.exe thus at least (2* 5 =) ~ 10 s are wasted:
Code:
PushD %~dp0
set "gimp=%ProgramFiles%\GIMP 2\bin\gimp-2.10.exe"
set "FileExtens=PNG"
"%gimp%" -i -b "(batch-crop-to-content \"*.%FileExtens%\")"
"%gimp%" -i -b "(scale \"*.%FileExtens%\")"
"%gimp%" -i -b "(rotate \"*.%FileExtens%\")"(In addition there is the closing of Gimp, which is also somewhat delayed).
Suggestions for improvement?