Session-cosession confusion
I took a set of product photos last week. I created a new session an imported the photos. Let's say I called it "Candles".
This week I went to Okinawa. When I got home I created a new Session called "Okinawa" and imported the photos.
Today when I go to open/recent, there are 2 cosessiondb files in the recent files list, "candles.cosession.db" and "okinawa.cosession.db"
If I open, Okinawa.cosession.db, it contain all of the photos from both candles and Okinawa. If I open, candles.cosession.db, I get the same all photos from both candles and Okinawa.
What gives? Shouldn't the contents of the sessions be separate? Isn't that the point of sessions?
This week I went to Okinawa. When I got home I created a new Session called "Okinawa" and imported the photos.
Today when I go to open/recent, there are 2 cosessiondb files in the recent files list, "candles.cosession.db" and "okinawa.cosession.db"
If I open, Okinawa.cosession.db, it contain all of the photos from both candles and Okinawa. If I open, candles.cosession.db, I get the same all photos from both candles and Okinawa.
What gives? Shouldn't the contents of the sessions be separate? Isn't that the point of sessions?
0
-
To where in your computer's folder structure did you import each of the sets of images?
Were you importing from a card, multiple cards or, given that you mention a product shoot, a mix of a tethered shoot and a subsequent card based set of images?
Assuming you have not created any other sessions since the Okinawa import, open the import process window and work out where the source and identified destination folders are pointing to. Then see how that fits with the location of the files within your system.
Let's start there and see where it takes us.
Grant0 -
Just importing from 1 card on 1 camera. It's a Fujifilm X-T2 so no tethering.
It looks like they are all going to a folder called Capture One Session.
Do I have to manually create a new folder each time I do a new session?
I guess I assumed that naming the Job would make a session named with the job name. ( I tried naming subfolder but couldn't make sense of the subfolder tokens.)
What is the function of the job name then? I tried looking at the help but it provided no useful information.
Is there a way to simply create a new session, give it a name and have the files import in to a folder with the session name?0 -
[quote="PhaseoneUser82303" wrote:
Is there a way to simply create a new session, give it a name and have the files import in to a folder with the session name?
Yes. Open Capture One, go to the Library tab, click the + to get the option of a new session or a new catalog - choose session. You'll be asked for a name for the session. If you choose, say, January, then Capture One will set up a new folder called January in your Pictures folder, it will create a session file called January.cosessiondb, and subfolders for Capture, Selects, Output and Trash.
If you wanted it to be located somewhere other than your Pictures folder, you can specify the location in the dialog box when you create it.
Ian0 -
I went to library tab, added new session and have it a path on a different hard drive from the previous sessions. I opened it and it was a new empty session as expected. Then I imported 1 image from an SD card (the card contains 197 images.
The browser on the right imported the image... then it continued to populate with an additional 495 images . (basically everything I've imported since setting up my new computer last week).
Is there a way to get the browser to show only the photos in the new session?0 -
Where are the other 400+ images on your system?
Are they in a folder that you have accessed using your new session?
If so C1 will have found those images because you chose the folder in which they reside.
The folder will appear in the list somewhere in the library window.
Unless you have somehow managed to "import" all of those images to the new session they will simply be referenced at their external (to your separate drive) location so you can ignore them or break the link by removing it (the link, not by deleting the images.)
If you have not done anything like that (as far as you know) then you have something unusual going on.
HTH.
Grant0 -
The other images are on the local hard drive. The new session used an external hard drive. 0 -
This is very frustrating. I have been too busy to sort this out since you replied last. I've been using the workaround of creating a new import folder every time so I can get my work done but the problem remains the same.
If I follow your instructions (I'm pointing it to the Pictures folder in this case) and create a new named session then import 1 file from an SD card. When I open that session the browser on the right displays that image along with 500+ other images.
It looks like the new folder is created where it should be but the file from the SD card is not there. There is a cosession.db file there. If I open it it shows the 500+ files along with the one I intended to import.0 -
Is it possible that all those "unwanted" files are still on the camera's card? C1 is bad about importing already imported images. 0 -
[quote="PhaseoneUser82303" wrote:
I took a set of product photos last week. I created a new session an imported the photos. Let's say I called it "Candles".
This week I went to Okinawa. When I got home I created a new Session called "Okinawa" and imported the photos.
Today when I go to open/recent, there are 2 cosessiondb files in the recent files list, "candles.cosession.db" and "okinawa.cosession.db"
If I open, Okinawa.cosession.db, it contain all of the photos from both candles and Okinawa. If I open, candles.cosession.db, I get the same all photos from both candles and Okinawa.
What gives? Shouldn't the contents of the sessions be separate? Isn't that the point of sessions?
For me this is an error that occasionally occurs (very rare though). I would start with cleaning up Capture One by deleting the preferences.0 -
Images aren't unique or within sessions. When an image is "imported" into a session, it's basically copied to somewhere on the system. One session can browse and edit another session's images. Think of sessions more as folder-browsers- if there's images that Capture One can read, it will show you a preview. Also, as the adjustments and settings are stored in sidecar files, any session will be able to edit any images, regardless of which session imported them.
Likely what's happened is that you've specific the import path for Okinawa.cosessiondb's images to be within the folder structure of candles.cosessiondb. Reinstalling "fixes" this because it returns the import settings to the default, but that's using a hammer for a headache.0 -
I have recently seen something similar to the original reported problem.
If I have a session open (V9, Windows 7 in my case) and then create a NEW SESSION and attempt to import to that it appears that the Import screen seems to think it is still associated with the originally open session so the "Capture Folder" destination is not the expected capture folder.
This information does appear next to the "Sample Path" but it's not something one always feels the need to read (until now ...)
I have not yet investigated why it is defaulting to a previous "Capture Folder" when accessed through the new Session. Fortunately it can be corrected without too much effort but is still slightly annoying when the unexpected occurs.
Grant0 -
Good point Grant, not something I had considered. 0 -
I love the way capture one processes RAW files but the file management still leaves a lot to be desired. "Extremely quirky" is the kindest description I can think of for it's current state.
The latest twist in this saga for me is that now when I open Capture On and insert an SD card, 5 cessions automatically open and 5 instances of the import dialog automatically open. If this behavior is "by design", this is, from a user perspective, very bad design.0 -
I think that if you had 5 sessions open together when you closed C1, those 5 will open again when you open C1. You could open just the one if you start C1 by double-clicking the session file for that session only. Also there is a setting in preferences to open sessions in a new window. If you have that option selected, then creating a new session, or choosing an existing session to open when you are working in another one, results in two sessions open at once. If the option is not selected, then when you start a new session, or open a previous session from within C1, the app closes the current session, so that you only have one session open at a time. (I find the latter the most convenient way to work.)
Ian0
Post is closed for comments.
Comments
14 comments