メインコンテンツへスキップ

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

Very bad performance with Full Sync of XMP data enabled

コメント

4件のコメント

  • RobiWan
    Hi,

    full sync or read XMP data enabling in C1 is very bad idea. This may really work with small sessions but not with catalogue.
    Phase One know this but I think there have no idea how to fix it.
    0
  • SFA
    [quote="deirh" wrote:
    In my catalogue of around 30000 photos (imported from Lightroom), whenever I enable Auto Sync sidecar XMP to Full Sync, I encounter terrible hiccups and basically entire Capture One becomes unusable until I turn it off. Seems complexity of this option scales with number of photos. With 30K, Capture One eats up all my 4 CPU cores constantly and GUI grinds to a halt with frequent Not Responding states. It does not go away even after few hours.

    Any possible future fix to this? Would really like to ditch Lightroom for catalog management but XMP sync is really important to me (can be synced to Google Drive).

    Thanks.


    Do you have 30000 photos that constantly need full XMP sync?

    If not, turn it off until you need it.
    0
  • Benjamin Liddle
    Additionally, you can manually sync via the Metadata tool's dropdown menu (... at the top right) and selecting Sync Metadata.
    0
  • fotojenic777
    [quote="deirh" wrote:
    In my catalogue of around 30000 photos (imported from Lightroom), whenever I enable Auto Sync sidecar XMP to Full Sync, I encounter terrible hiccups and basically entire Capture One becomes unusable until I turn it off. Seems complexity of this option scales with number of photos. With 30K, Capture One eats up all my 4 CPU cores constantly and GUI grinds to a halt with frequent Not Responding states. It does not go away even after few hours.

    Any possible future fix to this? Would really like to ditch Lightroom for catalog management but XMP sync is really important to me (can be synced to Google Drive).

    Thanks.


    Admittedly my cat is only 11,000 images but I've had full sync set on from the very beginning and I do not see any performance degradation or improvement if turned off. It would be interesting to understand what is monitoring the xmp files to determine if an external app has altered any data and therefore COPro needs to sync. If I edit a xmp file in one window with COPro open in another the metadata in COPro refreshes as soon as I click "save" in text editor so something is "watching". Clearly changes made in COPro metadata e.g. keywords know when to sync to the xmp and so there should be no additional overhead syncing in that direction. Perhaps someone from PhaseOne could enlighten us?
    0

投稿コメントは受け付けていません。