Life after Aperture

[purplehaze]

Great reference, Mike; thanks.

[Manfred M]

I think I remember reading that unless you elect to write a separate sidecar for each file, AE selects one at random for each set.

No. There can only be one sidecar file per raw file. The file name has to be identical, other than the extension.

Based on the screen shot 333.NEF will use the 333.XMP file. 333(1).NEF has no sidecar file associated with it. Even though the contents of 333.NEF and 333(1).NEF are identical. My guess is someone copied the same raw file into the directory and the operating system renamed the copy.

[Mike Buckley]

No. There can only be one sidecar file per raw file.

Janis noted that there is only one sidecar file pertaining to a raw file and two tiff files that are versions of that raw file. She doesn't seem to be suggesting that there can be multiple sidecar files pertaining only to the raw file.

[Manfred M]

If you read the quote of hers that I am using, she doesn't say that at all. She clearly suggests that if there are two identically named sidecar files, the editing program will randomly select one of them when a file is opened for editing. In computer systems, it is impossible for two identically named files to be in the same directory, so the situation she suggests cannot occur.

Sidecar files and raw files need to be situated in the same directory for the editing program to access them.

[purplehaze]

No, sorry if I was unclear, Manfred, Mike read me correctly. We are talking about an exporter (Aperture Exporter or AE), not an editor. What I gather from the AE documentation is that AE's default is to write one XMP file for the imported RAW and all associated versions, but you can optionally choose to have it write a sidecar for every imported image file. The default does not allow you to choose which image file's XMP data gets carried over, the exporter chooses randomly among them. It strikes me as less desirable for drive space reasons to have one XMP file created for every version of a given image, which is why I would put the XMP data I want to preserve (name of editing program) in the file name prior to export.

[billtils]

Mike

They are in the same album namely 2014-15 in the screen shot.

[billtils]

Eagle-eyed Janis The "(1)" designation is because I duplicated that particular file.

This thread and the comments from everyone who has contributed has been outstanding re my personal migration (or non-migration) strategy and success, and led to a major shift in approach.

I am now a very happy Capture One user (unlike my feelings when I tried it out in April). This is mainly because of how Aperture Exporter worked for me ("for me" because the optimum solution will differ for different people), coupled with some help from a friend who uses C1 and was able to demystify the difference between C1's "Catalog" and "Sessions" but I now have a cleaned up library with the same hierarchies as were in Aperture.

[purplehaze]

It is great to hear you have had a positive experience, Bill. It gives me confidence to move forward. ;-)

[Mike Buckley]

I now have a cleaned up library with the same hierarchies as were in Aperture.

Way to go, Bill! As the title of the thread indicates, there really can be life after Aperture.