Import Catalog from Aperture: Persistent Compatibility Issue
I've been trying to import my entire Aperture catalog since 10.0 (just tried again with 10.1.2). Each time, upon completion of my import session, I get an error that several hundred files were incompatible and not imported.
The error doesn't give specifics of which files were identified as incompatible, so I'm mostly left guessing which files out of tens of thousands were left behind, which isn't good. Does anyone have experience or can shed light on the issue?
I've contacted Phase One about the issue and their response wasn't very helpful... they just sent me a link to a list of compatible file types (all of the photos in my library match those types).
Getting very desperate, since Aperture can no longer support my needs. Any help is super appreciated!
The error doesn't give specifics of which files were identified as incompatible, so I'm mostly left guessing which files out of tens of thousands were left behind, which isn't good. Does anyone have experience or can shed light on the issue?
I've contacted Phase One about the issue and their response wasn't very helpful... they just sent me a link to a list of compatible file types (all of the photos in my library match those types).
Getting very desperate, since Aperture can no longer support my needs. Any help is super appreciated!
0
-
I just finished my trial with CP1 and after fully reviewing it and LR I've actually decided to stay with Aperture and just not upgrade my camera 😂 (The implementation of brushes in CP1 was a deal breaker for me, Aperture is still so much better / faster and more intelligent workflow)
I did migrate one library of about 6K images from Aperture into CP1 and all images worked, perhaps its brush tools or other adjustments are not compatible and hindering the transfer. Keep us updated.0 -
Ha! I wish I'd thought of that! I switched cameras and my new one isn't Aperture compatible, so I've effectively painted myself into a corner 😄
Does anyone have any experiences with "incompatible images"? I've searched all over to find examples but none that I've found so far apply (and Phase One support wasn't the least bit helpful).
Really appreciate it!0 -
I managed it this way. I realised that I had to find the type of incompatible image. Once I understood that, then I could eliminate or convert the images in the Aperture Library, and redo the import.
I found that .psd, .png, some .tiff and some video caused problems.
In my expereience, Capture One handles virtually any JPEG, except that those with any dimension less than 512 pixels become uneditable (but they are not incompatible). There have also been certain types of RAW images which Capture One can't be handle - it takes a while to get support for newest formats, and there may be some old formats which will never be supported.
For the purposes of migration, I made a base or reference Aperture library, and then working versions. I then imported the latest working library into a temporary Capture One catalog, where I would verify and assess. Then I would discard the temporary catalog, and go back and improve the working version of the library.
This works well with referenced files, I would not try this with managed files.
In retrospspect, a really fast way to determine this question quickly would be to make a temporary Aperture library with each image type in its own project or album. Separate according to image type, according to the type and origin of RAW and any other differences you can think of. Count the images in each project (each type). Now import into Capture One. Projects which become completely empty identify your completely incompatible types.. Count the images in the remaining projects and compare with the Aperture temporary library to see if there are other issues. Go back to the temporary library and delete all the unsupported image types, import again. Repeat until there are no incompatible images on import.
Now go back to your refernce library, and from it make a working version, and there take care of the unsupported image types. Delete, convert, resize as needed. Try the import again and check if it's clean.
I made a sreies of 5 working libraries as I dealt with TIFF issues, dealt with hierarchical keyword issues and dealt with version and file names. Once or twice I realised that I had done something wrong, or proceeded in an inconvenient direction, and then I restarted from the previous working version.0 -
Update
I've isolated at least part of the problem. About 2/3rds of the "incompatible" files are PNGs.
But I can't for the life of me figure out what makes these PNGs different from the hundreds of other PNGs that imported just fine. No edits were made, no differing EXIF data, no differences in file size (larger and smaller files both imported fine), not from different sources, etc.
Did anyone else have issues with PNGs when importing from an Aperture library? If so and you can share any insights in issues you encountered, it'd be HUGELY helpful.
Thank you!!!0 -
[quote="NNN636161386430431591" wrote:
Update
I've isolated at least part of the problem. About 2/3rds of the "incompatible" files are PNGs.
But I can't for the life of me figure out what makes these PNGs different from the hundreds of other PNGs that imported just fine. No edits were made, no differing EXIF data, no differences in file size (larger and smaller files both imported fine), not from different sources, etc.
Did anyone else have issues with PNGs when importing from an Aperture library? If so and you can share any insights in issues you encountered, it'd be HUGELY helpful.
Thank you!!!
This is a good topic to discuss with PhaseOne support - why these PNGs and not those? Very specific, so they will find it difficult avoid answering the question, as they sometimes do.
I've searched in vain for a list of file types that are supported for import into Capture One - another question for PhaseOne. I cannot even find online help for the CaptureOne Import feature in version 10. There is a COP version 8 description, and a lot of broken links.
I only had a couple of PNG files in my Aperture Library, which both caused problems, so I converted them to TIFF.
I've done that with some other files as well, used Aperture to export as TIF, then import the TIF into Aperture library and copy the Metadata over. Knowing that Aperture is getting progressively unreliable, and that NIK SW is also dying if not dead, I've purchased Affinity Photo for $50 to serve as a complement and external editor for COP. Affinity doesn't have the DAM features of COP, but it does some key things that COP doesn't do, such as HDR, tone mapping and working with (and resizing up) images less than 512 pixels on one side. Affinity 8 bit TIFFs are compressed and seem to import well into Capture One Pro.
I have noticed that the COP Aperture Library Import functions differently than the COP Image import function - some things (like smaller images) that cannot be imported in the COP Image Import are still imported (or import is attempted) in COP Aperture Library Import.
It might be worth selecting some of both kinds of PNG file, and seeing how COP Image Import handles them.0 -
[quote="NNN636161386430431591" wrote:
Ha! I wish I'd thought of that! I switched cameras and my new one isn't Aperture compatible, so I've effectively painted myself into a corner 😄
Does anyone have any experiences with "incompatible images"? I've searched all over to find examples but none that I've found so far apply (and Phase One support wasn't the least bit helpful).
Really appreciate it!
I've just done what is probably my last ever Aperture Import.
In this import, I noticed that TIFF files with more than one image (like main image + thumbnail) are also treated as incompatible.
You can sse the two images if you open with Preview.
I handled this by opening the image in Affinity Photo, and then exporting it with layers suppressed, then Capture One could import it.0
Post is closed for comments.
Comments
7 comments