Allow Option to Overwrite/Skip Files when Exporting Originals
What problem do you see this solving?
The Export Originals function does not give the option to Overwrite or Skip Existing Files. It defaults to adding a suffix to the name of existing files. The option to Overwrite/Skip was added to the other Export options in C1 v21, it would be very helpful to have it available when exporting originals.
When was the last time you were affected by this lack of functionality, or specific tool?
My workflow requires me to output RAW files along with XMP sidecars during shoots, so I need to be exporting originals frequently and want to just overwrite files from previous exports.
Are you using any workarounds or other solutions to achieve your goals in Capture One?
Yes, I have to remember to delete the files from the export destination folder which is error prone.
Are you happy to be contacted further about this suggestion or request?
Yes please.
-
+1
If the original image raw file is skipped, do you want to xmp file to be skipped too or update the xmp file with the current metadata?
As far as adjustments (cos and comask) files are concerned I want them to be updated (and xmp too)
0 -
If I select Skip, I would expect it to behave the same way it does with a normal Export. When I select Skip there, the exported file is not updated even if I have made further edits, so I'd expect the same with Export Original (I.e. don't update sidecar/COS files).
One other/unrelated request - adding an option to generate XMP files when doing Export Originals would be great. Currently I only get XMPs if I've already generated them in the source folder (e.g. have Image - Sync Metadata). Would be great to basically have the option to do the metadata sync with the original export.
0 -
+1 - really need this as my company's workflow includes making multiple revisions and overwriting conflicting assets
0 -
Hi SFA,
"Overwriting" originals is, in the context of this thread, meant as an option or workaround to update write, or overwrite new or changed xmp files (or cos files in the respective subfolder). It is mentioned in the replies and can alternatively be implemented by a xmp and cos/comask file sync.
EDIT: My remark about the xmp and cos/comask file sync is nonsense, it was driven by my deep desire to have that.
If you have an original image in your original location then an overwrite with newer a new .cos file can simulate a cos file sync, though I would not want to really overwrite the original file in its original location. For a backup or second location though it could make sense but an xmp/cos file sync would not be appropriate. It is late already...0 -
Was it ever any different through the ages?
I don't know, please ask the AI.
:-)
0 -
That's the issue with AI, the result often appears to be convincing though it might be totally wrong (ChatGPT etc.). AI for masking and denoise maybe an exception.
0 -
If you don't have cost, time, energy and risk of failure, where is the delight when you succeed? If I just want to have an impressive image on my wall I can just buy a print from a better than me photographer (who hopefully did not use AI). :-)
0
Post is closed for comments.
Comments
7 comments