re aquiring a session
I've been using C1 for a few years now and on occasion want to revisit older Sessions. Inside that Session folder is usually a cosessiondb file. If I click on that file it opens C1 and that operational folder, and it's great as a one click tool. But the only way that I can SEE that cosessiondb file is inside Adobe Bridge (or Explorer). I can't see it when I try to use the C1 file tree. There doesn't seem to be a "see all files" choice within C1's preferences.
So is there a better way to open old Sessions? Is there a way to see that cosessiondb file within C1? What am I missing?
-
There are two ways. (1) go to the session in question in File Explorer and double click it as you have done, or (2) in Capture One go to File>Open... then navigate to the .cosessiondb file.
Ian
0 -
Using Windows you can simply search for cosessiondb files. There is a search option as part of the File>Open option - at least there is in Win 7, provided by Windows.
If not that then much depends on how you have structured and managed and named the folders you have used as the parent folder for the session.
In the library tool there is a drop down list of "recently" accessed sessions and catalogues.
I think the default drop down length for "recents" in Windows is 10 rows but a bit of judicious editing of the the appropriate value in the Windows registry can extend that if it would help.
0 -
The File>Open in C1 seems to have solved the problem. I kind of wish that there was a dedicated folder created in Sessions so I'd know where it was, and to leave that subfolder alone. I think maybe I'[ll start creating one.
It's still weird at what you can't see when the Capture One file tree is used. Why is C1's file tree so dumb? You can't see the cosessiondb files, nor can you see subfolders created by C1 in custom Process Recipes.
0 -
If you really want to see all of that you might consider moving to a catalog based approach.
I would not want to see the output folders. I am pleased they are ignored by default since otherwise all of the output files would be identified by C1 as editable files and have subfolders, previews and thumbnails created for them when such things are not required. Indeed, in my opinion, not welcome for the most part.
I actually think it is quite smart to avoid that problem.
0 -
My professional workflow means that using a file tree system makes a lot more sense than a catalog, so I'm both stuck and prefer that method. I'd still like to see sub-folders but I take your point.
0
Post ist für Kommentare geschlossen.
Kommentare
5 Kommentare