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. ⚠️

Capture One 11.1 crashing when importing photographs

Kommentare

3 Kommentare

  • Ian Wilson
    Moderator
    Top Commenter
    I wonder whether it is to do with this catalog, or your system? What happens if you create a new test catalog and try to import a few images?

    Ian
    0
  • Harold Mancusi-Ungaro
    I had a similar problem. It turns out that is just takes a lot of time, hours, to import a large library. During the process, it would halt when it did not find a file. In the beginning I would quit, delete the new catalog, open Aperture and relink the photos and go again. In the end, I told it to skin files not found. Once the new C1 catalog was built, there were some duplicate albums not in projects. Now my problem is if I try to move them C1 crashes. When I reopen the album has been moved successfully.
    0
  • Eric Valk
    When I last imported my Aperture library of 16000 images, it took Capture One 10 about an hour to complete the import process. Sometimes I would just let it run overnight.

    I made an album with no contents, and immediately when the import started I would select this album - in this way Capture One has to generate no previews and show no images during the import. Even so, Capture One would be non-responsive during much of the import. Once the import was finished, I would select "All Images", and then Capture One would spend another hour generating previews.

    Prior to the final import, I made a quite a number of trial imports to fine tune the process.
    • Removed or converted images of unsupported image type
    • Found files with missing images and linked them back into the Aperture Library
    • Renamed Files according to Aperture Version Names
    • Fixed up the hierarchical keywords so they imported properly
    • Converted Aperture Stacks and Smart Albums to Albums

    I found it useful to make a small test library of a few thousand images to do the initial testing.

    Note that some CaptureOne operations slow down as catalog size increases, this becomes more noticeable as the catalog size gets larger than 10,000 images.

    One particular sticking point is the Filter tool - if its active (meaning visible, or being used for a filter) then it can take a very long time to refresh. Depends on the metadata - if a large image collection has some metadata field which has a unique value for every image, then the refresh time really builds up. I put the original file name and import time into IPTC Metadata fields, and it took me a long time to track this down as the source of the perfrmance issues. One fix is to remove the Filters Tool from the Library tab, so the tool is typically not active.

    The work flow of images in CaptureOne is a little different than in Aperture.

    In Aperture, the paradigm is to put every single image - good, fair, bad, burst, bracket - into the Library. CaptureOne paradigm has unculled images coming into a Session, and then the selected and culled images may then be imported into a Catalog. Unfortunately, there is not straight forward way to move images from an Aperture Library into a Capture One Session.

    What I think I will end up doing is, having imported my main Aperture Library into a Main COP Catalog, exporting the images that should be in sessions, importing them into a Session, and then deleting them from the Catalog.
    0

Post ist für Kommentare geschlossen.