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

I wish I hadn't imported Aperture library

Kommentare

3 Kommentare

  • Helmut Kaufmann
    I had a similar iussue with Aperture. Here's what actually helped:
    - Checked if actually all images that were on disk were actually loaded in Aperture (surprisingly, quite a few were not and of course then there is not import into CO)
    - Did a complete rebuild of the Aperture database.
    - Imported into CO1 using the Aperture import.
    - Ran a script that straightened out the directory file names during the Aperture import (in the CO catalog it always started with /Macintosh HD/Users here a manually import would have resulted in the directory being only Users)
    - Synced the imported tree again manually, this imported files that I still had missed when checking as described above.
    - Checked for missing files, see .
    - Most of the missing files were not imported as the meta data could not be read by CO. Used exiftool to fix it.
    After this, everything as more or less fine. CO is currently building the previews (16 hours for roughly 45k images), which makes it really slow to use in the meantime.
    0
  • EnderWiggins
    I think the C1-Aperture-Importer regularly has trouble with bigger Aperture libraries (that was my experience with just 27.000 images), so I would advise to split up the work into smaller import jobs. That may have lead to your troubles with missing images. Maybe throw the C1 catalog in the trash and start again using my approach (seperate your library into smaller ones and import them one by one).

    After your import you simply have to wait until C1 has built all the previews. This is actually similar to starting a new library in Aperture. Back in the days then people also complained about Apertures' performance because they were not patient enough to wait for the preview database to be built completely before actually starting to work with it.
    0
  • Neonsquare
    @MikeA
    Does opening this big catalog take that long for you too? I have converted a bigger Aperture library (have to look how many images) and it take minutes to open it - even if the catalog is on a SSD.
    0

Post ist für Kommentare geschlossen.