Page 1 of 1

feature request for batch processing: suspend batch processing, edit transformations, and resume batch processing

Posted: December 5th, 2022, 1:18 pm
by pierrelabreche
Would it be possible to add a control feature whereby batch processing could be suspended and resumed ?
When batch processing is suspended, editing the image browser transformations would be permitted.
Thus, another transform could be added, or the order of transformations could be modified.
Batch processing could be restarted with the image input transformation at the top.

Re: feature request for batch processing: suspend batch processing, edit transformations, and resume batch processing

Posted: December 5th, 2022, 4:19 pm
by jsachs
There is no easy way to implement this. Once you start a batch process it either has to run to completion or be canceled.

Re: feature request for batch processing: suspend batch processing, edit transformations, and resume batch processing

Posted: December 5th, 2022, 9:27 pm
by pierrelabreche
I normally perform batch processing with breakpoints for cropping, adjusting gray levels, etc.
Would it be possible to accept this in breakpoints ?

An alternative would be a control feature to terminate a batch and remove all fully processed input files from the input file list, reopening the input transformation.

Re: feature request for batch processing: suspend batch processing, edit transformations, and resume batch processing

Posted: December 6th, 2022, 5:50 am
by jsachs
Allowing arbitrary editing of the image tree in the middle of a batch process has the potential to crash the program.

This is further complicated by the fact that there can be multiple File Opens being processed in parallel.

I believe the way it works now is that when you terminate a batch process, the red dot indicating the current image should be on the first unprocessed image. If you click on it and then shift click on the first image in the list you should be able to select and then remove all the processed images. In addition, the red dot marking the current image is left on the last image processed. If you terminate and then restart the batch process it therefore starts at the file you were processing when you terminated the batch. I did make a change for the next release so that when a batch process runs to completion, the current file is set to the first file in the list.