Capture One Pro 12-Slow loading metadata

Comments

4 comments

  • Ian Wilson
    Capture One catalogs do generate their own previews, even when you import the images from a session which will already have previews. Of course, the previews in the catalog are stored inside the catalog, whereas the previews for the session are stored in subfolders of the image folders. But I too have wondered why it can't just copy the previews from the session folders. However, despite that, I would not expect 23 minutes. What is your setup? What computer, what version of MacOS, where are the images stored (inside the catalog, or outside and if so on an internal or external drive)?

    Ian
    0
    Comment actions Permalink
  • Marco Hyman
    The documentation warns about setting the Auto Sync Sidecar XMP to Load or Full Sync as it will slow down image import. That is an understatment. It brings image import to a crawl.

    I haven't tested if the combined time of first importing then selecting all images and Load metadata is any faster than doing it all at once. I hope it is.
    0
    Comment actions Permalink
  • Ian Jukes
    Thanks for the replies! I just turned off Auto Sync Sidecar XMP. My session was once again happy, all the labels and star ratings set in Photo Mechanic 6 were correct, as is the metadata.

    I just did a test. I added GPS data via Geotag Photos Pro 2 and then hit Image > Load Metadata. Once again, very slow, 6 minutes for 190 images. Capture One Pro 12 also decided to create new previews. Why? all that changed was GPS data!
    0
    Comment actions Permalink
  • SFA
    [quote="Manalishi" wrote:
    Thanks for the replies! I just turned off Auto Sync Sidecar XMP. My session was once again happy, all the labels and star ratings set in Photo Mechanic 6 were correct, as is the metadata.

    I just did a test. I added GPS data via Geotag Photos Pro 2 and then hit Image > Load Metadata. Once again, very slow, 6 minutes for 190 images. Capture One Pro 12 also decided to create new previews. Why? all that changed was GPS data!


    I would guess that the amended source file will be recognised as "changed" (i.e. not the same file as was previously known) with no easy way to assess what has changed - could be a completely different file - so the regeneration occurs.

    DId is actually regenerate or did it just update the working records in memory cache?


    Grant
    0
    Comment actions Permalink

Please sign in to leave a comment.