New to C1 - Archiving Edits
Still VERY new to raw editing, and was surprised there doesn't seem to be any way to store adjustments in sidecar files. How do you "archive" your work? Currently I'm using Catalogs as I'm using the Express version for Sony. But, if I can come up with a sustainable workflow for how I operate, I'll likely upgrade to Pro.
Catalogs seem restrictive and dangerous. I already had a catalog freak out on me. I ended up with duplicates upon import that I don't know how I got in the catalog. Anyway, that's probably operator error, and I'm not fundamentally worried about that at the moment. But as my library gets larger, the catalog will get huge. I'm guessing I need to use sessions (which are not available in the Express version.)
My question is, for all the pros that have project based work, how do you handle all your material?
I'd like to:
1) Import all my RAWs
2) Perform all the adjustments and edits
3) Export the JPGs
4) Somehow export all the adjustments. (I thought into sidecar files for each RAW.)
5) Archive the RAWs and Sidecar adjustments
6) Remove everything from C1.
This way, if I needed to go back, even 5 years from now, I can copy the images from the archive with the sidecars, import the images (and the associated adjustments), and continue where I left off.
How is something like this accomplished in C1? I really would like the archive to contain the original, straight from camera RAW file... I saw something about EIP.. But that also contains a copy of the RAW data? It's proprietary to C1? The raws are 24MB each. Presumably the EIP is also 24MB. I just need the adjustments....
How do I accomplish this?
- Mike
Catalogs seem restrictive and dangerous. I already had a catalog freak out on me. I ended up with duplicates upon import that I don't know how I got in the catalog. Anyway, that's probably operator error, and I'm not fundamentally worried about that at the moment. But as my library gets larger, the catalog will get huge. I'm guessing I need to use sessions (which are not available in the Express version.)
My question is, for all the pros that have project based work, how do you handle all your material?
I'd like to:
1) Import all my RAWs
2) Perform all the adjustments and edits
3) Export the JPGs
4) Somehow export all the adjustments. (I thought into sidecar files for each RAW.)
5) Archive the RAWs and Sidecar adjustments
6) Remove everything from C1.
This way, if I needed to go back, even 5 years from now, I can copy the images from the archive with the sidecars, import the images (and the associated adjustments), and continue where I left off.
How is something like this accomplished in C1? I really would like the archive to contain the original, straight from camera RAW file... I saw something about EIP.. But that also contains a copy of the RAW data? It's proprietary to C1? The raws are 24MB each. Presumably the EIP is also 24MB. I just need the adjustments....
How do I accomplish this?
- Mike
0
-
Sessions I believe is the better solution for project based work. Back up the entire session and all of the settings go with it.
When using sessions there is a CaptureOne folder that generates inside your image source folder which contains all of the preview and adjustment files. If you backup this folder along with your RAW files then in the future you will be able to access your adjustments from the backup so long as the CaptureOne folder remains in the RAW source folder. It is easiest to backup the entire session, leave out the output folder if you have no need to backup the jpgs.
Another alternative is process everything out as EIP files. This is a stand alone file that contains the RAW image as well as the adjustment settings so you can open it in Capture One and all settings will remain intact. It however can only be opened in Capture One as far as I know.0 -
Ok. It sounds good.
Basically, I keep the C1 folder in the ARW folder and archive it with the ARW files. I don't need to create EIP files.
I can delete the previews/cache from the C1 folder (to save space) when I archive...
Then, if I need to reprocess or make additional edits, I just import the session, and all the edits are already in place?
And presumably future versions of C1 will read older versions of the session files?
Is that about right?0 -
Yes, that sounds correct.
Newer versions on C1 will open older version sessions, it will ask if you want to update the session and once you update it you can no longer open the session in the older version of C1 that it was originally created in.
Sometimes the way C1 applies its adjustments are redesigned so from time to time opening an older photograph in a newer version of C1 will give you a different looking edit. I have not experienced this myself but if I remember correctly some people experienced this moving from 10 to 11, I think it was something about the order that the adjustments are applied were changed so the end result changed as well, maybe it was with the downloaded style packs(?), I don't recall exactly.0 -
Older sessions will need to be updated to the latest session format if opened in a later version of the app. But individual older images still have the processing engine that they first used unless they were updated. So you can update any given image to the latest processing engine, and that does sometimes change the rendering - for example I am still sometimes opening old sessions that have images in them that used the version 6 engine. Updating may make quite a difference depending on the adjustments used - for instance the highlight and shadow recovery sliders have a markedly different effect. If I want to try improving an older image I often create a new variant and use the new processing engine on that so that I can compare with the old result and go back to it if I prefer it.
Ian0 -
Ian3 wrote:
Older sessions will need to be updated to the latest session format if opened in a later version of the app. But individual older images still have the processing engine that they first used unless they were updated. So you can update any given image to the latest processing engine, and that does sometimes change the rendering - for example I am still sometimes opening old sessions that have images in them that used the version 6 engine. Updating may make quite a difference depending on the adjustments used - for instance the highlight and shadow recovery sliders have a markedly different effect. If I want to try improving an older image I often create a new variant and use the new processing engine on that so that I can compare with the old result and go back to it if I prefer it.
Ian
sounds good. thanks to you both. I'll probably "Zip" up the Capture One directory during my own archive process and keep it on the side. If I want to reprocess, I'll hang onto the original zip..
This sounds like it will work for me.0 -
I think you may be over-complicating this. You can reprocess an old image in a session that has been updated to the newest version. You can even reprocess it using the old processing engine if it hasn’t been updated for that image (or even temporarily change the processing engine back to an old version). Most of the time you will get a better result reprocessing with the new engine, thought as it provides features the older engines didn’t have.
Ian0 -
Ok. Got it.. Thanks. 0
Post ist für Kommentare geschlossen.
Kommentare
7 Kommentare