Batch Process - Project Saves
Batch Process - Project Saves
Is it possible to batch save all processed file projects or must I save them individually? I cannot find an option to save all batched files projects.
Re: Batch Process - Project Saves
There is currently no option for that, but it can be implemented, I'll add it to the to-do list.
You can use the command line mode with a script, saving a project is possible from the command line.
You can also run your batch and manually save the results as projects one by one.
You can use the command line mode with a script, saving a project is possible from the command line.
You can also run your batch and manually save the results as projects one by one.
-
clausgiloi
- Posts: 34
- Joined: 12.09.2024 16:27
Re: Batch Process - Project Saves
Pardon my jumping in here with a related comment - Some time ago I brought up adding an option to embed the input files into the save file rather than having external file references. I would still love to see this feature.
Re: Batch Process - Project Saves
Do you mean copying the source files to the project folder? There is no singe project file, there's a file + a folder with a bunch more files inside.
Currently, the source files will be bundled with the project (copied to the folder) if they are in a temporary location. i. e. if it was exported from Lightroom/Capture One/some other software that places exported files in a temporary folder and later deletes them. We could extend this behavior to all source images, sure, but generally it's not needed. We could add an option for that.
If you have a project that doesn't open because the source images were moved, you can open the .hproj file with a text editor and edit the paths to where they are now.
Also, whenever possible, the project stores relative paths to the sources. This means, for example, that if you saved the project to a sub-folder in the source image folder, and then moved the whole parent folder, the project will still load (and it doesn't have to be specifically a sub-folder).
Currently, the source files will be bundled with the project (copied to the folder) if they are in a temporary location. i. e. if it was exported from Lightroom/Capture One/some other software that places exported files in a temporary folder and later deletes them. We could extend this behavior to all source images, sure, but generally it's not needed. We could add an option for that.
If you have a project that doesn't open because the source images were moved, you can open the .hproj file with a text editor and edit the paths to where they are now.
Also, whenever possible, the project stores relative paths to the sources. This means, for example, that if you saved the project to a sub-folder in the source image folder, and then moved the whole parent folder, the project will still load (and it doesn't have to be specifically a sub-folder).
-
clausgiloi
- Posts: 34
- Joined: 12.09.2024 16:27
Re: Batch Process - Project Saves
Naively, the way that I would like it to work is that when you "save project", it prompts for a destination, then bundles all needed input images (and needed outputs!!) into a .zip file at the destination. Load project would reverse this.
Typically, my input files are still on the memory card, I would want to save only my "keeper" stacks from the batch to secondary storage.
Unless the restrictions on saving projects with retouching from other outputs is lifted, the whole mechanism is of limited value to me since that applies to virtually all of my outputs. I can see how this becomes tricky on loading, since the input list for the retouching source output could be different, so the set union of input files for multiple outputs would have to be saved.
Thank you for your consideration!
Claus
Typically, my input files are still on the memory card, I would want to save only my "keeper" stacks from the batch to secondary storage.
Unless the restrictions on saving projects with retouching from other outputs is lifted, the whole mechanism is of limited value to me since that applies to virtually all of my outputs. I can see how this becomes tricky on loading, since the input list for the retouching source output could be different, so the set union of input files for multiple outputs would have to be saved.
Thank you for your consideration!
Claus