Batch Processing annoyances
Posted: 14.12.2018 10:32
Hi,
my standard process is always like taking tons of pictures during the day and processing images over night so the batch processing is of great help, but there are a couple of issues:
1) Stackdefinition when selecting thousands of pictures with lot of stacks:
1.1 why do I have to wait for exif info to be parsed just to answer a question which is obvious ? ( yes break up and proceed ) why not ask first - or add a checkbox "start automatically after splitting" ? ( this takes quite a while for 10000 pictures...)
1.2 no further information about stack content ( image numbers) is displayed to identify single stacks in the batch main window
1.3 stack content ( range of images processed ) is not stored in exif of generated tif ( nor elsewhere to support inputfiles <-> ouputfile correlation later on)
1.4 re-setup after out of discspace stop ( because of topic 2) is cumbersome (as 1.2, 1.3) you have to count available output images to delete splitted stacks ( after again 1.1) to be able to continue...
2) temporary files are only deleted on shutdown of application! (Not when a stack is finished!) I have 256 GB SSD dedicated to Helicon only which is not enough to process all stacks over night ( scenario is every day like 1.x)
3) Optionally it would be nice to have an option to also save the project files of a batch run automatically
what do you think ?
kr
Jim
my standard process is always like taking tons of pictures during the day and processing images over night so the batch processing is of great help, but there are a couple of issues:
1) Stackdefinition when selecting thousands of pictures with lot of stacks:
1.1 why do I have to wait for exif info to be parsed just to answer a question which is obvious ? ( yes break up and proceed ) why not ask first - or add a checkbox "start automatically after splitting" ? ( this takes quite a while for 10000 pictures...)
1.2 no further information about stack content ( image numbers) is displayed to identify single stacks in the batch main window
1.3 stack content ( range of images processed ) is not stored in exif of generated tif ( nor elsewhere to support inputfiles <-> ouputfile correlation later on)
1.4 re-setup after out of discspace stop ( because of topic 2) is cumbersome (as 1.2, 1.3) you have to count available output images to delete splitted stacks ( after again 1.1) to be able to continue...
2) temporary files are only deleted on shutdown of application! (Not when a stack is finished!) I have 256 GB SSD dedicated to Helicon only which is not enough to process all stacks over night ( scenario is every day like 1.x)
3) Optionally it would be nice to have an option to also save the project files of a batch run automatically
what do you think ?
kr
Jim