Two drives for "To be edited" and "Edited"
Hi I'm going to be using two external disks for my work with Capture One 23 for better performance.
One SSD for editing ("To be edited") my images and the other HDD for storage after editing ("Edited"). From here to backup.
The Capture One catalogue is naturally linked to the images being edited on the SSD. When I move those images to the HDD to the "Edited" folder, the images on the SSD go "offline". Later if I want to re-edit and stop the edits I made previously, I just connect those files offline, but this time to the HDD in the "Edited" folder and I get back the edits I made in the past? Does changing images between disks physically erase the information of the edits made and stored on the Capture One catalogue?
System: Mac mini M1/macOS Ventura (updated)/SDD & HDD-APFS files system/Capture One 23 (updated)
Thanks a lot
-
Additionally...
Would it make sense or have any advantage to import the images to edit on the SSD, actually copying them instead of using "Add to Catalog"? Once edited in C1 and exported to tif and jpg, when I copied the folder with everything to the "Edited" HDD, would Capture One keep up with this transition since it wouldn't go "offline"? When reopening them from the HDD, would C1 recognise them? Could I then delete the original, unedited folder from which they were first imported?
Thank you0 -
That sounds a little strange to me. If you are working with a catalog (and not with sessions) then I suggest not to copy or move images with the Finder or other external tool, instead consider using the library tool in C1 (drag&drop images from browser to a folder in the library tool). Or, do it outside and use the Locate folder function in C1.
The edits/adjustments are all stored in a catalog regardles where your images are stored (In catalog, or outside catalog from the "Add to catalog" import, SSD or HDD). The point is you want to maintain the links in that catalog to the images (so that they don't appear as offline), otherwise a catalog is of rather limited use.
You can use a ToBeEdited-Catalog (or a session) to edit your images on the SSD and after that you could export originals including adjustments, and then import them in your final HDD_Edited-Catalog. Clean up the ToBeEdited-Catalog. Something around this.
Whatever workflow you consider, try it out with a number of test images, this will probably give you better answers than anybody here could give you and might reveal unexpected side-effects you may or may not like.
0 -
Thank you for your help. This seems to be a good solution:
"You can use a ToBeEdited-Catalog (or a session) to edit your images on the SSD and after that you could export originals including adjustments, and then import them in your final HDD_Edited-Catalog. Clean up the ToBeEdited-Catalog. Something around this."
0
Please sign in to leave a comment.
Comments
3 comments