Saving image settings outside of the catalog
I would like to be able to export image settings from given images in a catalog, in order to save a copy of these settings in case the database gets corrupted.
When exporting images using "Export Original Files", there is indeed a checkbox entitled "Include Adjustments".
But I could not find a way to export adjustments ONLY (i.e., the "Capture One" folder which is created when exporting original files with settings), NOT the image files themselves.
Is there a way to do that? That would be very useful.
-
This is actually one of my favorite feature requests, a two way synchronization between catalog adjustments and adjustments on the file system (CaptureOne/Settingsx.y.z sub folder, .cos and .comask files).
Not possible today. Please create a feature request too.
0 -
The Capture One folder that you mention is a feature of Sessions rather than Catalogs - one of the big differences between how Sessions and Catalogs work is that in a Session, edit data is stored alongside the image files in subfolders of that Capture One folder, whereas in a Catalog it is stored inside the database.
As you have discovered, using Export Originals and Pack as EIP in the Export feature effectively does what you want, but at the price of duplicating the image files, and also with the risk that the versions in the catalog and the other versions get out of sync if other edits re made.
I tend to agree with Andy Gawthrope and SFA that regular catalog backups are the way to go. In fact you can quite easily get a fair bit of useful redundancy into your backup routine. As using Capture One's facility to back up the catalog on exit, you have (presumably) system backups using Time Machine or similar. And the Capture One catalog backups needn't take up a lot of space - there is no need to keep very many previous backups as long as nothing has gone wrong with the catalog, especially as you could restore them from Time Machine anyway.
The other thing you could do is to use the Export Collection as a Catalog feature on the File menu and create a separate catalog of the images you are most concerned about. But again you get duplication and the risk of edits getting out of sync.
Ian
0 -
Thank you all for your considerate replies.
Finally, I tend to be convinced by the idea that the best way to proceed is to make regular backups: there is in practice no advantage in size of the "Capture One" folder generated when saving original files with the adjustments, over a catalog backup. In addition there is no need to keep many older backups.
Bernard
0 -
Given the current possibilities of C1, catalog backups are the easy way to go. But it is not the same as having all edits in sidecar files because you can only go back to the latest backup (in case your catalog is broken even after verify/repair). If sidecar files would be written automatically (in additon to the catalog) then you could restore from the sidecar files into a new catalog and have your most current state (not an older backup).
The opensource raw developer darktable has both a catalog AND sidecar files. So, it is possbile.
I like to use sessions for every new shoot and only need a catalog for searches across sessions. Even for long term storage sessions are great, sessions are small self-contained packages which can be moved as needed.
As I also re-edit images across sessions even spanning several years (maybe some of the images were only auto-adjusted, or I need specific editing for a certain printer/paper etc.) I would like to keep the edits in the catalog and in the session in sync.It should not be too difficult to implement and would give us the best of both worlds, sessions and catalogs.
0 -
The opensource raw developer darktable has both a catalog AND sidecar files. So, it is possible.
Actually, I understand that Lightroom can do it too - not by default, but there is an option to enable sidecar XMP files, and if that is activated the edits are stored both in the catalog and in the sidecar file.
As far as going back to older sessions goes, though, another option is to start with a session, as you do, but once the session (or the keepers from the session) have been added to the catalog, only do subsequent edits in the catalog, and not in the session.
Ian
0 -
Hi Ian, yes I know you do it that way.
But then the catalog is not obsolete. I want each image to have a sidecar file (or two) holding all edits so that each folder is an independant container of images including their edits. I could through away the catalog if wanted and import the images into a new one. Sessions (or folders containing original images and the Settings sub folder) are a good concept.
In a recent re-organization effort I exported all folders (images) in my catalog as originals including adjustments to some temporary location, then copied the CaptureOne folder which holds the exported settings into the original image folder so that I can edit them with a (any) session.
The plan is to search for images I want to edit in the catalog and put / gather them in a catalog album. Then drag&drop them from the album browser to a session album (C1 session running), edit them in the session so that the edits are stored in the .cos and .comask files, then remove them from the catalog (I remembered them in the catalog album for this purpose) and then import (synchronize) them into the catalog again from the images parent folder. A somewhat complicated workaround workflow, only because C1 cannot sync the catalog with the CaptureOne/Settings folder.
Cheers,
BeO0 -
If LR can do it, then maybe C1 will follow, they even removed the "Processing" tools in favor of a simple Export dialog, because it is so Lightroomish... :-)
0
投稿コメントは受け付けていません。
コメント
7件のコメント