Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Lost Edits on Session

Comments

6 comments

  • SFA
    If you are using a Session the folder structure and file names provide the links between the image and the edits.

    So, basically, wherever you files are that folder requires a subfolder named "CaptureOne" and in that folder 2 more subfolders named "Cache" and "Settings<something>"

    Cache is for Previews and Thumbnails. Not important if you can recreate them using the edit files.

    Settings<Something> will be where the edit files are to be found. <Something> will be the version number of C1 that has been used to create the edit files. So Settings120 will be V12.

    In the settings folder you should find the .cos files that contain the image edits and .comask files if you have created masks using layers and, perhaps, a few other file types for other edit related activities if you have used them.

    If your .cos, .cosmask , etc., files have become detached from the folder containing the original files you will have a problem. Likewise if you attempts at renaming (outside C1?) have renamed the original files they will have no matching edit files due to name differences. I.E. if you do not have a folder with the original images that also contains a CaptureOne folder or if you DO have A CaptureOne folder but no Settings folder (or an empty settings folder) that would certainly be a problem.

    I would suggest you first check what you have in those areas and lets take things from there.

    HTH.

    Grant
    0
  • CHRIS PRINCE
    Thanks for the reply.

    It's weird in that the raw images are still in the original location. The "CaptureOne - Settings120" folder with all the .COS and .Mask and .ICM files are all located in the original location. The files are all there (and taking up about 1.5gb). The images that were NOT exported are fine. The images there WERE exported have reverted back to as shot. It's like CP1 pushed the .COS files to the dropbox folder where the exported JPGs went and forgot the original.COS files are still located in the original file structure. Goofy... I'm wondering if THOSE .cos files have now been written over and instead of having my edit instructions, the instructions are now basically null. But I have no idea...

    Thank you so much for any insights!
    0
  • SFA
    [quote="NNN635732201373084680" wrote:
    Thanks for the reply.

    It's weird in that the raw images are still in the original location. The "CaptureOne - Settings120" folder with all the .COS and .Mask and .ICM files are all located in the original location. The files are all there (and taking up about 1.5gb). The images that were NOT exported are fine. The images there WERE exported have reverted back to as shot. It's like CP1 pushed the .COS files to the dropbox folder where the exported JPGs went and forgot the original.COS files are still located in the original file structure. Goofy... I'm wondering if THOSE .cos files have now been written over and instead of having my edit instructions, the instructions are now basically null. But I have no idea...

    Thank you so much for any insights!


    How, exactly, did you make the "Exports"?

    At what point did PhotoMechanic come into the process? (Before or after your C1 editing activity?


    Grant
    0
  • CHRIS PRINCE
    Hi Grant,

    The exports were standard "Process" images that were exported to a dropbox folder. PM was used after tethering and before editing by locating the RAWs in finder for PM and making my selections. Then sync metadata and CP1 pulls in that info and updates the session with any tags from PM.

    I've used PM at the stage before with no issues and that doesn't seem to be the problem here. The PM flags (which were basically to add a Red color tag to my selects) are still present. The Star ratings that I created in CP1 are gone as well as the edits on the files. The .COS files are still in their original location and do not appear to be syncing back up to the RAWs.

    I'm stumped.
    0
  • SFA
    Right.

    So everything is performed in the local machine up to the point of processing (using a Process Recipe?) to the Dropbox folder?

    You have RAW files in C1 and exported jpgs.

    Export or Process to output would not create a settings folder containing .cos files. Finding one in Dropbox is odd. So far as I can think it through the simple act of deleting and the reinstating it would seem to be unlikely to have any bearing on the edit work performed on your RAW files that are not on Dropbox.

    The .cos files that may come to exist (if,for example, you were to open the output folder and view the images in a session) but relate to the jpgs would not have the RAW file edits included. The jpgs would have been exported with the edits embedded permanently. EXIF data would be embedded according to what you had allowed as part of the output process.

    Back on your processing machine are there any other locations that might contain the original RAW settings (.cos etc.) files but with names that no longer match the RAW file names? Or were the renaming activities entirely related to the Exported (Output) files?

    The .COS files that you can see at their original location need to be in the correct folder location relative to the RAW files and the names must match exactly. What happened to the original RAW files that were NOT part of your selection and therefore (presumably) were not sent for output?

    As for missing star values after Sync - the sync process setting need to be carefully understood.

    I don't have need of them so I am now expert but I do know form posts by others that the potential for confusion is significant. That is a common problem of cross-application and cross-machine(s) synchronisation. However I'm not sure how that possible warning applies in this case.


    Grant
    0
  • OddS.
    [quote="NNN635732201373084680" wrote:
    ...
    12) I had a baby and am now totally sleep deprived trying to figure out wth I did and how to fix.


    Congratulations! I hope all is well and that you don't allow Capture One to keep you sleepless.

    [quote="NNN635732201373084680" wrote:
    ...
    I'm afraid at this point that it's overwriting the edits with the "new" instructions which are basically "as shot."


    That may well be, your list indicates that you may have confused C1 beyond recovery. Restore from backup comes to mind..., but re-edit may be your only option.

    [quote="NNN635732201373084680" wrote:

    I can't find a way to resync the edits back into the RAW files


    Simple explanation: There is no such thing, C1 does not write to existing image files.

    I will not try to analyze the issue with those mysterious C1 folders/files in your Dropbox, but I hope you can find time for a little experiment that hopefully clarifies things.

    You will need a new C1 session according to C1's default template, no fancy folder redirection, no Dropbox, no external disk, do everything using the computer's local harddisk. You will need two image files (different, not two copies of one image nor two very similar images, you must be able to see the difference). You will also need a new empty folder outside the folder structure of the new session. Don't worry, you will delete the session, the image copies and the temporary folder at the end.

    Pay attention to the session name you pick for the new session and the folder where the new session is is located on disk. I want you to be able navigate to the session folder and operate on it using a file tool like Finder or similar. The experiment takes a whopping 15 steps, but they are really simple and quick. But pay attention to what you observe.

    1) Start C1 and create a new session. Just for the experiment

    2) Close C1.

    3) Peek around in the session folder and observe its empty sub folders (Capture, Selects, Output and Trash) in Finder and observe the session's database file (<session name>.cosessiondb). That is where C1 keeps some of the secret sauce. This is as basic and bare bones as a session gets.

    4) Copy one of said image files into the newly created test session's Capture folder. Finder should only show one image file in that folder, no sub folders

    5) Start C1. You should be able to see the thumbnail image in the Capture folder (Library->Session Folders->Capture). Do not open the image the viewer if you can avoid it, you should just see the single thumbnail image appear in the film strip.

    6) Close C1

    7) Peek around in the session folder again and observe the sub folders (Capture, Selected, Output and Trash) in Finder once more. Observe the changed Capture folder content.

    8.) Create an empty folder somewhere on your disk, but avoid the session folder structure. You only need a temporary folder. You can delete it later.

    9) Copy the second file image into the temporary folder. Use Finder and observe that the copied image file is the only content in that folder.

    10) Start C1 and navigate to and select the temporary folder (Library->System Folders->.../temporary folder). Do not open the image in the C1 viewer if you can avoid it, you should just see the single thumbnail for the second image appear in the film strip.

    11) Close C1

    12) Navigate to the temporary folder using Finder and observe how the content of the temporary folder located outside your session folder structure looks similar to the session's Capture folder.

    13) Start C1 and open a different (older) session, and make sure you see the thumbnails etc. (This is just to keep C1 from nagging you next start because it can not find the most recent session, you are going to delete it using Finder.)

    14) Close C1

    15) Delete the session folder and the temporary folders created as part of this little experiment. When you see "stray" C1 folders/files where you did not expect them to be, you may now have an idea of how they got there.

    C1 in session mode does nothing to cover its tracks. Why would you use a C1 session for browsing images outside the session's folder structure? I don't know any tool better than PM for that. The fact that C1 needs additional folders and files to do its housekeeping when you point C1 to image files outside a session structure, has confused a few users. I have seen users ditching C1 as their raw image tool because they hate those housekeeping folders/files so much.

    I'll leave commenting on the metadata and sync part of your post for another day 😄
    0

Post is closed for comments.