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

Aperture library import failed: "Invalid hex quad"

Chris-H
Hi all.

I've just purchased and installed C1 and tried to import my Aperture 3.6 library (332GB) from my OS-X (10.10.3) pictures folder. After half a few seconds C1 gave me the following message:

"Katalog Import fehlgeschlagen, invalid hex quad" which translates
"Catalog import failed, invalid hex quad"

Anyone familiar with the issue and can help me get on board?
Thanks, Chris
0

Kommentare

8 Kommentare

Datum Stimmen
  • Henrik Lorenzen
    try to repair you permission on your Aperture libary
    that might help
    Henrik
    0
  • Chris-H
    Thanks Henrik - done that but it did not do the trick. However you've triggered another idea: I've only just restored my Aperture library from Time Capsule and while the library looks good and fully functional in the application, I noticed that it's still processing pictures in the background. As I have some 20.000 in this library, this might still take a while. I did have Aperture closed while I attempted to import it to Capture One - however maybe I just let Aperture complete its processing job first, then close it down when it's done and finally try the C1 import again... Will report how that goes...

    Of course if someone has another hint, please shout!
    Thanks, Chris
    0
  • Eric Nepean
    Hi Chris
    I have just finished importing about 17000 referenced images (130GB) from Aperture to CaptureOnePro. So not quite quite as big as your collection but sizable nevertheless.
    Here is the process I used, maybe it will be of help to you.
    1) Starting with my Aperture Library - Preparation
    - COP will not recognize not import version names. I changed all my File names to match the Aperture version names. (optional Using an Applescript, I put the original filename into the IPTC "source" Field, and the Aperture import date into the IPTC "JobID" field)
    - COP does not recognize the Keyword hierarchy in Aperture Library. Changed all the keywords in Aperture so that COP will recognize the hierarchy upon import "TopLevel | NextLevel | ... | BottomLevel"
    - Extracted the Keyword list from Aperture and copied it into the COP plist file, so that it becomes the master list of keywords present in all COP Catalogs and folders
    - COP does not recognize smart folders, copied the images from each smart folder into an album of the same name
    - COP does not recognize stacks, copied all the images in each stack into an album, indicated the stack pick with a color code, all the nonpicked images with a different color
    - COP does not recognize many Aperture adjustments - using a smart folder at the library level, selected all images with each kind of adjustment, added a keyword indicating what adjustment type was applied.
    - Divided the Aperture Library into chunks of 4000 to 6000 images, separated as top level folders, plus two folders of about 50 images for the purpose of testing
    - Exported each of these top level folders as a new Aperture Library - so these new libraries are clean, no trash, no processing required
    2) COP - Testing
    - Set COP to "Prefer Sidecar XMP over embedded Metadata"
    - Make a test catalog, import the Aperture Test Libraries. After each import select the "all Images" folder to force syncing the Metadata and create previews.
    - Check carefully after each import to make sure that all images and Metadata make it across correctly.
    - If not, go back and fix what needs to be fixed in the Aperture master Library, re- export the Test Libraries, repeat steps above until hapy witht he results
    3) COP - First Main Import
    - Re-export your first for real Aperture library chunk
    - The Import process appears to be limited and slowed down by available RAM, so I make a number of choices here which seem unusual, but the purpose is to free up as much RAM as possible, and requires COP to use as little RAM as possible.These choices are indicated by "**"
    - ** Start by setting COP to "Prefer Sidecar XMP over embedded Metadata" and "AutoSyncSidecarXMP" to "No"
    - Create a COP catlog which will become your Main Catalog, in the place where you want it to be permanently.
    - I would not set it up so that COP treats the managed images in your Aperture catalog as referenced images, I think it is better to have a common pool of images which are referenced by both tools, or to move the entire set of images into an COP Catalog file. Personal and complex choice - YMMV
    - ** Create Group called "Dummy" in the COP catalog
    - ** Turn off all optional SW in your MAC - emails, browsers, antivirus, dropbox, other users
    - Import the First Aperture Library into the COP catalog - ** as soon as the import starts, select the "Dummy" group with your mouse.
    - The import proceeds by importing all the image files and counting them as it imports - when COP has finished counting image files it seems to hang, but it is continuing to write to disk and process. On my machine that takes another 40 minutes to complete, and uses a very large amount of RAM. Best leave it undisturbed. If the import fails due to lack of application memory, this last part is where it fails. On my machine, and import of 9300 images fails for this reason.
    - One the COP Activity menu disappears, and COP once more reacts to the mouse, set COP "AutoSyncSidecarXMP" to "Full", now select the COP "all Images" folder. This will cause COP to sync all the Matadata and generate previews for all the imports. This probably takes another hour or so.
    - Check carefully after the import to make sure that all images make it across correctly. Count to make sure the number of images in the catalog match the number of images in the library.
    4) Remaining Imports
    - Make any other changes needed in the main Aperture library and re-export all the remaining top folders
    - Import each Aperture library into your main Catlog, one by one, following the procedure above. Especially as the size of the main catalog grows, be sure to turn off "AutoSyncSidecarXMP" during import, and to select a something that causes no images to be shown during import, to get the highest speed and lowest memory usage.

    FWIW my iMac has a 1 TB magnetic drive, 16GB of RAM and a quad core i5 processor. Machines with 32GB or RAM and SSDs will probably execute this much faster, for those with smaller RAM you might have to cut down the size of the import.
    0
  • Chris-H
    Oh wow - thanks Eric! I must say I'm blown away...

    Shouldn't we copy/paste your process into a new post under a more appropriate headline, so that more people will find it to take advantage?? I mean this should really not be buried in my crazy "invalid hex quad" post... What do you think?

    For myself I'll go paste your process into my Omnifocus system as a number of new subprojects to my C1 migration project and work out what I need to do under each step.

    Damn - I was so looking forward to pressing the button and just go import everything... Can't wait to finally work with C1. But looks like it's absolutely worth taking a step back and do some proper preparation work upfront...

    Thanks again from Hamburg to the other side of the world!
    Chris
    0
  • Chris-H
    Hi all
    (It's been a while I know, life got in the way...)
    The import attempt still delivers the same C1 error message (import failed, invalid hex quad) even after I freshly rebuilt my Aperture library.
    I'm clueless what to do i.o. to make the Aperture-to-C1 library import work... Anyone come across this error message before / got a hint what to do?
    Thanks all, Chris
    0
  • Paul Steunebrink
    Hi Chris,

    Have you already contacted support on this issue?
    0
  • Chris-H
    No not yet, thought it might be something totally simple. Will do.
    However - all ideas welcome. Thanks.
    0
  • Eric Nepean
    I have done a number of Aperture imports into COP, with images from a wide variety of cameras (my own and 8 friends) but I have never seen this issue.

    Since it happens very early in the import process I would guess it is a problem with the Aperture Library structure, not the images.

    I would try exporting about 100 referenced images to a new Aperture library and see if you can import that. If they are managed images (i.e. inside an Aperture Library), then move them with Aperture to a folder so they become referenced images before exporting to a new library.

    If that works, try exporting all your images to a new Aperture Library and see if the import error still occurs.

    How many images do you have, BTW?
    0

Post ist für Kommentare geschlossen.