Capture One 8, corrupt session files
I use sessions. Recently, I created five sessions after an overseas trip. I've been working on all of them sporadically over the last couple of weeks. My computer froze once earlier this week. Today, I tried to open two of the sessions, but they would not open. The others are OK. Oddly, the affected sessions were not what I was working on when the comptuer locked up, but I may have been in them earlier that day.
When I try to open the affected sessions, there is a short interval where the "Loading" message with orange progress bar shows in the center part of Capture One. This quickly disappears, and the Capture One "brower" says "No images in collection." I never see "Loading" in the browser area. If I try to Verify the session, the verify fails. When I try to Repair the session, it claims that the verify is OK, but the same problem persists--the session won't load, and a subsequent Verify on the new session file (and the backup(s)) also fail.
1. Why is this happening, and what can I do about it? Can I fix it? Or can I re-import the files and keep the previous edits (the sidecar files in the session's Capture One\Session82 folder appear intact)?
2. I have a sense that switching between different sessions can cause Capture One to become unstable. Is this true, and there anything I can do about that?
I'm running Windows 7 on a Dell Optiplex 980, 8 Gigs memory. Capture One 8.3.2 64-bit. I will upgrade to the latest, but I still need to regain access to my sessions.
Thanks for any help!
--Peter
When I try to open the affected sessions, there is a short interval where the "Loading" message with orange progress bar shows in the center part of Capture One. This quickly disappears, and the Capture One "brower" says "No images in collection." I never see "Loading" in the browser area. If I try to Verify the session, the verify fails. When I try to Repair the session, it claims that the verify is OK, but the same problem persists--the session won't load, and a subsequent Verify on the new session file (and the backup(s)) also fail.
1. Why is this happening, and what can I do about it? Can I fix it? Or can I re-import the files and keep the previous edits (the sidecar files in the session's Capture One\Session82 folder appear intact)?
2. I have a sense that switching between different sessions can cause Capture One to become unstable. Is this true, and there anything I can do about that?
I'm running Windows 7 on a Dell Optiplex 980, 8 Gigs memory. Capture One 8.3.2 64-bit. I will upgrade to the latest, but I still need to regain access to my sessions.
Thanks for any help!
--Peter
0
-
As long as the subfolders of the main folder which holds your image files weren't moved, deleted or similar I'd say all your edits are still there.
It seems to me though that your specific "session" file lost track somehow to the right location of the files.
I'd suggest to open C1. Then you should see in the centre on top of the screen the name of the active session.
If it isn't the right session then go to the Library icon in the top left section of the screen and click it.
Under "Library" the first item should be "Session X" with X being the name of the active session. There you can switch to another session or add one.
If the active session or the changed (or added new) session still doesn't point to your image files go down to the "System Folder" section and browse there until you find the folder which holds your images (similary as you would in Windows Explorer) and click it. This should open your files - with the already performed edits applied.
When finally closing C1 the information regarding location of the files should be saved by C1 so the next time you open C1 it should "remember" the last used session as well as the location of the files. However whenever C1 may have lost track all what's needed is to re-direct it to the right spot as described.0 -
Michael, your diagnosis and solution were both spot-on. Problem appears solved. Thank you!
I realize now that the problem folders may be folders that I renamed to match my usual naming convention after initially misnaming them. Someone else on this forum said that if renamed or moved a session folder in Windows Explorer, keeping with all of its subfolders and files intact, C1 would figure this out when I next opened it, and adjust its internal pointers accordingly. For a while that appeared to be the case, but at some point it lost track. This is distressing, because I am going to probably have to move my image files to a second hard drive soon. I would hate to have this issue with every session I've ever created.
--Peter0 -
[quote="Peter306" wrote:
Michael, your diagnosis and solution were both spot-on. Problem appears solved. Thank you!
I realize now that the problem folders may be folders that I renamed to match my usual naming convention after initially misnaming them. Someone else on this forum said that if renamed or moved a session folder in Windows Explorer, keeping with all of its subfolders and files intact, C1 would figure this out when I next opened it, and adjust its internal pointers accordingly. For a while that appeared to be the case, but at some point it lost track. This is distressing, because I am going to probably have to move my image files to a second hard drive soon. I would hate to have this issue with every session I've ever created.
--Peter
Using sessions the chances are that your source images are almost all of the disk usage for that session - unless you also have a lot of output files.
Either way a session, if set up on a per shoot sort of basis, is likely to be self contained. If not you may have missed out on one of the great benefits of sessions.
If it is self contained you can simply move the entire session to another disk. It's what I do when I I have finished with a shoot so far as I know. If I then need to access it again and undertake further edits I can just open it from the external drive and work on it there or, if there is a lot of work to do or it would be more convenient to work on a local disk, I just copy it back to local and carry on there.
If you have a less structured sessions in which you have opened folders from all around your filing system and not bothered with a complete self contained session folder structure then you need a different approach. However a folder full of images edited with C1 should have a capture One folder present as well. That will contain a folder with your edit adjustment files. So long as you keep that folder in place when copying your main images to an external drive you should have no problems re-opening the images in their own session or another session one you have selected the folder.
I found that the key to getting sessions to work for me was to stand back, after my initial dive into the deep and of the C1 pool, gain an understanding of the way sessions are intended to function, work out how that best fitted my requirements and then let C1 handle things rather than attempt to swim against the tide with a few of my previous preconceptions. In fact, once I had done that, I discovered that C1 was enabling me to do just what I had wanted to do all along.
One thing that your description of you problem prompts me to point out.
A session database is basically a link to some file locations and some general settings information. It can only know about changes if you make them through the application.
If you open a folder you can edit the images and the edits will, if allowed to, remain with the images wherever that folder goes. Unless the folder is also added to the session database as a "favourite" it simply becomes a folder which contains some images and a set of edit files and previews, etc.
If you add it to the session as a favourite the session will record where it is and moving the folder(s) will break that link if the move takes place outside the session. In that event the folder will need to be "rediscovered" to reinstate the link within that session although the lost link in itself does not make the edits disappear - they will still be with the original files in that folder UNLESS you have done something to separate them.
It is not impossible, in my experience, for a session database file, just like any other computer file, to become damaged in some way. I have seen this once in several years of using C1. In fact the session file was not itself damaged but pointed to an edit file that had somehow become invisibly "bad". Once the edit file problem had been spotted and the edit file deleted everything worked perfectly once again.
Apart from that one incidence the session functionality has, for me, always worked very well - including the 2 or 3 session I keep for "generic" editing without being too concerned about managing a shoot. For example I tend to have a "testing" session with which I associate random activities with some folder as Favourites - usually because I have imported the images - and others just accessed without making them favourites when I want to quickly check something.
It all seems to work whichever way one approaches it providing one has thought through what one requires.
HTH.
Grant0 -
In my years of working with C1 and always working with sessions (only) perhaps I've misunderstood something concerning the fundamental idea of "sessions". Because I'm working with one only session and I don't see the point in having more.
As far as I understand, the session file holds my definitions concerning for example ratio ascpects for cropping as well as the definitions for my output receipts (I have 3: Full, MidJPG and SmallJPG each with specific settings concerning size, compression rate, colour space, watermark and so on). For what reason I'd need more than that?
So when I want to point my work to another set of images I simply browse to the folder which holds the reffered images.
OK, if it is a folder which holds several hundret images it takes some time to have all images read. But I don't think that there's a way to accelerate this process.
To OP: Shortly after starting to work with C1 (sessions) back in 2007/08 I discovered that it's very help and useful to define a meaningful organization structure for the image files. This is not only because the number of shots in the digital era rises easily into the hundrets of thousands in some years, and even if equipment changes, the default camera file naming stays the same (especially when staying with one brand over the time; and the naming is the same even over different camera models of the same brand). So cronology and camera model are two criteria I'm using in my organizing structure. And a "backup" means the creation of a copy of the entire structure to external drives.0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare