Zum Hauptinhalt gehen

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

Synchronize adjustments between catalog and sidecar subfolders

BeO
  • Bearbeitet
Top Commenter

A catalog with referenced images in my own system folder hierarchy, I want to create and synchronize manually (or keep fully synchronized) the adjustment files (.cos, .comask) in the sidecar folders CaptureOne/Settings.

Then I can use a (any dummy) session or the catalog to make changes to the image edits or metadata and keep the adjustments in sync.

No request to copy or move of the image files, just a plain synchronization of the adjustments in both ways. 

Thanks.

5

Kommentare

6 Kommentare

Datum Stimmen
  • BeO
    Top Commenter

    Maybe similar to the Load Metadata and Sync Metadata (XMP files).

    I am coming from sessions, either keeping the the session folder structure or moving the images with subfolders to my final image directory structure and then add the images folder to a catalog. I want to search in the catalog make changes and synchronize to the CaptureOne/Settings files.

    Or vice versa, edit in a session and sync to the catalog adjustments. 

    Benefits:

    - I have adjustments and metadata redundancy (in the catalog and as individual files per image), being a very good backup

    - I can through away my catalog (even if it is corrupted) and reimport all my images including adjustments with no loss since the last synchronization because all data is in the cos and comask files. Only need to recreate the catalog previews.

    - I can move or just remove parts of my directory structure e.g. to a long-term archive (similar as with sessions, the folder are self-contained) and have the full information travel in form of .cos and comask files alongside each image

    - C1 catalog and session based workflows are much better integrated than today

     

     

     

    0
  • BF
    Conversation Starter

    I would find this useful as well.

    0
  • BeO
    • Bearbeitet
    Top Commenter

    Thanks BF.

    Interestingly, the opnsource raw developer "darktable" actually can store the edits in its catalog as well as in its sidecar files simultaneously.

    0
  • Thomas Kyhn Rovsing Hjørnet
    Top Commenter

    This would be very useful. It would also allow for a workaround for issues with unresponsiveness when using larger catalogues, as you could then work with small ad hoc/temporary catalogues and sync all edits back to your main catalogue afterwards.

    1
  • BeO
    Top Commenter

    Thanks Thomas for another use case.

     

    0
  • ernst.w

    For me the idea of a workaround like Thomas Kyhn wrote sounds very interesting!

    0

Post ist für Kommentare geschlossen.