Clarification on .COF/.COT & Session Files

NFGphoto

• 18. Januar 2015 09:55

I've had another instance of edits lost because one computer used a different session file than the other, and a third of a thousand edited files reset themselves. I managed to find the appropriate session file and the edits were restored (which is a better outcome than last time when they were gone forever). This seems to be related to C1 not closing down properly: while the app is visibly shut down, there's a CaptureOne.exe process still running and it seems to cause me some grief when I move to the other machine and resume editing.

Anyway, I've been through the process with C1 support and it was confusing. Their advice was to copy the session file from one machine to another when editing, and this strikes me as sub-optimal, an extra step and important do-not-forget hassle when I change machines.

Which brings me to my question:

I've had to use a dozen different session files in the past because of crashes and locks, until I found the problem and it isn't happening anymore... But how can I tell if any images in the archives have edits relying on these no longer used session files? I haven't been backing up my session files because I thought all my edits were in these other files.

What are these six related files for every NEF image for if they're not storing the edits I've made?

0

• 

  Drew Altdo

  • 19. Januar 2015 11:33

  [quote="NFG" wrote:
  Their advice was to copy the session file from one machine to another when editing, and this strikes me as sub-optimal..

  
  
  I believe our advice was to use the SAME session file. Copying it to one computer to be opened and used when editing your files, then copying it back to the other machine when opening and editing images on it. This ensures you do not come across the rather obscure and odd workflow conflict you have initially reported.
  
  Further, as we suggested in the support case, should you open a Session and believe you do not see your edits to a file, try to create a New Session and access the same images. This will tell you where the root of the display conflict originates.
  
  Sessions DO NOT hold adjustments. These are saved in sidecar files to the RAW files. As such, you can delete old sessions without fear of deleting adjustments.

  0
• 

  NFGphoto

  • 19. Januar 2015 20:05

  Thanks Drew. This details of this issue were different from last time (ie: the edits still existed on one machine) so I didn't think to go back to the old advice. Rather, I was trying desperately to preserve the edits before they evaporated on me.
  
  Yes, copying the session file was the advice, but it's a hassle. I was hoping to avoid having to do it, so I've been extra careful about closing C1 on one machine before opening it on another, but still using different session files.
  
  I was hoping that if I avoid the caching issue by not copying session files, the sidecar files would carry me through. There are two problems here though:
  
  1. Capture One doesn't always close cleanly, leaving an invisible process (captureone.exe) that, I'm guessing, is still using the session file/caching stuff/queuing writes to the sidecar files (maybe?).
  
  2. One machine was using 8.0 and not 8.1 (oops). The 8.0 machine had ~400 edits the 8.1 machine simply couldn't see. When I updated the older machine to 8.1, all the edits were lost again, so I had to re-install the old version, restore the backed up session file, and get back to it.

  0

Post ist für Kommentare geschlossen.