checkbox in process recipe / overwrite files
Implemented
checkbox in process recipe - to select overwrite files in output if photo is processed again
-
How would you guard against over-writing a file by mistake?
(This suggestion often comes up, but I have to say - just as a fellow user - that I prefer the existing system. I can always delete an older version if I want to, but I'd hate to have over-written one that I wished I'd kept.)
Ian
0 -
That would be great!
2 -
@Ian Wilson
1. Overwriting output files should be an "opt-in" choice. If you don't choose the behaviour, you'll be safe.
2. C1 already supports many optional warnings, i.e., one can choose whether one wants to see certain warnings or not via the preferences. There should be a respective warning preference for overwriting output files. So even if you have opted in by mistake, you'd still be warned before any file is deleted. The overwriting feature would be less useful if one always had to confirm the overwriting, so such warnings should be optional.
In my view, output files are dispensable anyhow. If I don't keep a variant around that can create exactly the same output file again, I consider the output file as obsolete. In other words, if a particular output file is precious for some reason, one really should keep a variant in a catalogue or session that can be used to generate the output file again.
Regarding your point of always being able to delete an older version: It is very inefficient to be required to do that time and again if one keeps generating new versions of output files for some reason. One has to context-switch to an explorer/finder, select the files -- potentially in multiple output directories(!) -- and then delete them. After that one has to context switch back to C1. This is too cumbersome and tedious for files that really shouldn't have any value at all due to being derivatives.2 -
Hi,
Thank you for your post and comments.
The basic principle of Capture One is its non-destructive approach which means that no changes would be applied to the original image files.
-2 -
Hi Lily,
this request is not about original image files.
Of course C1 uses a non-destructive approach and should never change original image files.
The request is regarding exported renderings of original images. The idea is to be able to generate, say a JPEG file from an image within C1 and later be able to overwrite the generated JPEG file.
All renderings that C1 writes to output folders are in principle dispensable because they can always be generated again by repeating the export/process operation from within C1 that generated it.
The only time when they are not dispensable is when someone
1. generates the output file.
2. changes the adjustments to the original image (in a session or catalogue),
3. deletes the output because they think it has served its purpose, and
4. then wishes they could generate the output from step 1 again, but cannot because they cannot undo the latest adjustments anymore (e.g., because they closed the catalogue in between).
However, this should be a rare scenario. Most of the time people generate the output, use it for something and then either leave it, erase it, or write over it. Generated output shouldn't be really used for archival purposes (as the original will always deliver the best quality for future usages).
That rare scenario above aside, output should be easily removable (to save space) and, most importantly, overwriteable so that one can efficiently create new versions after having discovered some mistakes in the output (e.g., watermark on the wrong side, etc.).
Does the request make sense now?1 -
@Lily
I mean overwrite output files !!! not original source images !
@Class A - great detailed explanation
0 -
@Ian Wilson
If you don't want to overwrite output - simply don't mark checkbox ... - I mean - if checkbox is not marked - > C1 works as now - if it is marked then overwrite without any warnings already existing output file (remember that for variants you can use "Variant Position" meta in Naming format so for each variant you can receive separate result)
1 -
Hi,
Thanks for providing more details and clarifications on the matter as that is quite important in feature requests.
I will submit your suggestion regarding the option to overwrite previously processed files from the Process Recipe tool.
2 -
Thanks, Lily!
0 -
+1 on the request
3 -
As far as I can see this issue was first brought on this forum 9 years ago. It has been raised several time since then. It strikes me that having a check box to overwrite duplicate output files would be pretty simple to implement. It would still be a far cry from something like Lightroom's "publish" functionality. So let's get on with it. It will save me a lot of trouble!
4 -
+1000 to this request. I need to be able to overwrite old versions jpegs with updated edited versions. Having to export them to a separate folder and then move them manually from the finder is an extra, ridiculous and unnecessary step. If there is a concern that people won't remember their overwrite settings, simply include a pop-up warning before the actual processing begins.
3 -
This is 100% needed, I'm writing an FTP script right now and having program the system to delete the old files otherwise I can't reimport the filenames accurately.
I can name my recipe with overwrite or you could add an icon that shows that this recipe will overwrite exported files if you're worried about the user not realising, but this is a vital option, you're essentially saying the user is to stupid to know what they're doing by not having the option, well in my opinion anyway.
1 -
I would also love this option.
To avoid datalos you could (maybe as option Overwrite.No overwrite/Safe) create a 'save directory' and move the old file to it. Often you not want to reprocess all files, so now you have to fin the specific file, delete it and process.
1 -
@Kees Buth
A "save directory" is a great idea. One could clear it whenever it suits; the most important aspect is to be able to have updated files with the original names.There really is no good excuse left to not implement this request.
0 -
+1
Particularly needed since there is no capability to export to "maximum file size" (needed even more than this one). Until that feature is available, I often need to export a large batch of files (destined for a website), then see how many exceed the file size limit. At that point, I need to go back through and re-export until I hit the file size limit. Please don't point me to the File Size estimate under Process Summary - I find that to be highly inaccurate.
0
Post is closed for comments.
Comments
16 comments