Aperture managed vs referenced files

8 things you need to know about managed vs referenced files in Aperture

Aperture used to be like iPhoto – all the pictures you added were stored in its internal library, a single file which ring-fenced your shots from the outside world and enabled you to move your library around as a single object. You can still do that with the current version. It’s simple and secure, but as library sizes grow, increasingly impractical.

So Apple soon added the ability to reference external files. This separates the Aperture library from your original images, so it’s messier and more prone to user error, but perhaps the only long-term solution to ever-growing image collections.

Aperture managed vs referenced files

This is my setup. My Aperture library is in my Pictures folder, but my original files (‘Masters’) are on an external WD drive.

So that’s what you have to weigh up: managed vs referenced files in Aperture. It’s really important to know how both systems work, which one is best for you and, if you’ve not been paying attention, which system you’re actually using! Because until you know this, you won’t know where Aperture has put your photos…

5 thoughts on “8 things you need to know about managed vs referenced files in Aperture

  1. Hi Rod:

    Thanks for an enjoyable site. Generally a very good article discussing managed vs. referenced files. Having taught Aperture, I know how conceptually difficult this topic can be for many users. I know I am being somewhat pedantic and that too much info can be a problem, but hear goes with a couple of comments/suggestions. I hope you are not offended.

    Aperture no longer uses the term “masters”, replacing it with the term “originals”. Use of the old term may confuse students.

    You state, “Referenced files stay in their original location, which may even be on a separate drive”. This is may confuse some users, because for most image file imports the original location is a card in a card reader. This is one of the most dangerous aspects of dealing with referenced files. In paragraph 03, you specifically recommend using the “In their current location” setting. I have personally had to tell many people they have lost their original files, because they inadvertently selected this setting, where the original location is a card. They see their images import into Aperture. They might even back up their hard drive first, because they are cautious, but in short order they reformat their card, in-camera, which was the “original” location. Oops! If you must use referenced files, I feel a better methodology is to always use the “Choose” setting, as it reinforces that you are copying the originals to a new location. I realize there may be times where the files already exist in their final resting place and the “In current location” setting is appropriate, but users must be extra vigilant to avoid mistakes when using this setting.

    In paragraph 07, the implication is this is the way you would use an external editor. Certainly you could do it this way and if you use multiple external editors, it is required, unless you want to change preference pains regularly, as Aperture currently supports only one external editor at a time. However, if you predominately use one external editor and/or plugins, you can set your preferences to use this external editor. Once this editor is set, it will appear as an editing option, in the Photos menu and in the control click/right click contextual menu. The advantage to this approach is that Aperture manages the export/import round trip. Less work and fewer opportunities for a mistake.

    I feel the topic reviewed in 08 should include discussion of a third choice, multiple managed libraries. This allows the user to address internal storage space issues without going the referenced route. There are many ways to manage this approach, e.g., a current year, plus portfolio level images library on your internal drive and an archive library on the external drive. Someone who manages a very large database of images might take a yearly library approach. A professional photographer might have a library for each customer/project. Like all approaches, there are pros and cons. I feel the biggest pro to this approach is the reduction in human error possibilities managing referenced image import and the created files in the finder. I feel the biggest con is that Aperture can only search within the open library, so a multiple library user needs to have a good system for defining libraries, or they will struggle to determine in which library an image resides.

    I hope this commentary is useful. Thanks again for a useful site.

    Regards,

    Scott

    1. Thanks for those comprehensive observations, Scott. I think the one about not referencing file on a memory card is a particularly good one, and I wish I’d though of that!

      I also take the point about the swap from ‘masters’ to ‘originals’. I’ve been using Aperture a long time, but I hadn’t noticed that.

      I’ll update the post with those points in mind.

      Point 7 is not about using external editors and I can’t honestly see where I implied it. It’s about situations where you might want to extract a file from a managed Aperture library for use externally, for whatever reason – I think the DxO conversions I mentioned are a particularly good example. Aperture is not always the best RAW converter, and you have to resort to means like these to use another, or to send your originals to other people, for example.

      I think it would be better to cover external editors in a separate post.

      I have tried multiple managed libraries, but they don’t work at all well for me. Others may feel differently, though, so thanks for the suggestion.

  2. Thanks for the kind comments back my way Rod! I apologize for misinterpreting Point 7. I took it to be inclusive of all external editing, not specifically for RAW and/or batch processing. I have not found the need to do this type of work personally. You and your readers, who use Aperture and have this need, may want to explore the Catapult plugin. It is an Aperture plugin that facilitates round-tripping RAW files to DxO Optics Pro, ACR and Nikon Capture. It does not cover every base, but may be helpful to some. Below is a link to their site and a review:

    http://brushedpixel.com/

    http://www.apertureexpert.com/tips/2013/8/28/guest-post-catapult-and-aperture-3.html

    Regards,

    Scott

  3. Hi Rod,

    I really enjoyed reading your thoughts on referenced vs. managed libraries. I’ve been spending entirely too much time deciding which approach to use as I move all my images from PC to Mac. I’m a bit of a control freak when it comes to the handling of my files, so the managed approach goes against my nature. However, I’m just a JPEG-only rank amateur snapper, so I’ve decided to use iPhoto in managed mode for it’s sheer convenience. FYI, iPhoto can import photos with a managed, referenced or combo approach. Also, iPhoto can open an Aperture library, and vice versa, so I may graduate to Aperture at a later date.

    I’ve also decided to do a couple things to my images before importing them into iPhoto. I use the Automator to give them a more descriptive filename with the image date and time, and I use Picasa to add geotags and keywords. That way, my iPhoto masters will have that info in them should I ever decide to break out of the Apple camp.

    Steve makes excellent points about the danger of using a referenced library unless you are really clear on where your images will reside. Another thing for folks using an external referenced library: If you back up your Mac with an app like Time Machine, your external drive holding your photos must be connected during the backup if you want your photos backed up, too.

    Thanks again for your excellent and timely article!

    Rod T.

  4. Very informative Rod, and also Scott, your comments were very helpful. Being in a position of starting from scratch with Aperture and a Macbook Pro (moved from Windows), I was looking for “best practice” suggestions.

    Scott B.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.