Session vs Catalogs
It remains a but unclear to me what are the criteria which one to choice.
But on the internet, I just found this:
This organizational method puts all your edits in a sidecar file next to your original image, rather than centralizing everything in a single database file.
is this true? Maybe you have seen my post about a corrupt main catalog which I cannot repair. If i start using sessions, I have a feeling, I never loose my edits… (As i did now)
But on the internet, I just found this:
This organizational method puts all your edits in a sidecar file next to your original image, rather than centralizing everything in a single database file.
is this true? Maybe you have seen my post about a corrupt main catalog which I cannot repair. If i start using sessions, I have a feeling, I never loose my edits… (As i did now)
-
That’s one of the fundamental differences between catalogs and sessions. In a session, Capture One creates a Capture One subfolder in the image folder, and within that further subfolders for Settings and Cache. The Settings one includes .cos files with the adjustments, and .comask files too for images with masked layers.
Ian
Please sign in to leave a comment.
Comments
1 comment