Inside Aperture

Digital Media | Spotlight: Photography | Inside Aperture | Blogs

Color Management and Aperture


The other day, I was helping a person figure out a weird problem in Shake. Given it took two of us to figure out what turned out to be a color space problem, I figured it would worth spending some time discussing color management and Aperture.

Color management is important because, as you may know, no device, screen or printer, can reproduce every possible color, and each device reproduces a different set of colors. The set of available colors for a given device is called a color space. A color profile is just some math that specifies how to interpret pixel values in terms of a particular color space so that when we talk about a specific color, we're clearly and consistently defining the color. If each device we're working with has the proper color profile available (and our tools are setup to use them), then we can say our workflow is calibrated because as we move from file on disk to screen to other screen to printer, the colors stay consistent.

The first profile that matters is the profile in our image file. This profile tells Aperture (or another application, like Photoshop) how the colors in your file are defined. Some profiles, like Adobe 98, specify a large number of possible colors, while other profiles, like sRGB look pretty good even if you're not looking at that file on a properly calibrated monitor. In fact, typically, higher-end cameras create image files using Adobe 98 whereas consumer cameras (where the images often are displayed on uncalibrated monitors) use sRGB.

Once the file and its color information are read in, a color management engine (such as ColorSync) moves the pixels in the file into a flexible working color space, which in tools like Aperture and Photoshop is where we can make adjustments. Adobe Camera RAW for example uses ProPhoto internally as its working space (I believe). To the best of my knowledge, there is no way to specify Aperture's working space. The main reason this matters is that different adjustments can cause different results in different color spaces. Certain colors in your image might not exist in smaller gamut color spaces, for example. Another example of why your adjustments will differ is that some spaces are perceptually linear while others are energy linear. Say you double the exposure in your image. In a perceptually linear space, that means that your image will now appear twice as bright. In an energy linear space, you image might not be twice as bright, even though you've doubled the amount of energy in the pixels. Perhaps an option to set the working space will be available in the future, but I'm guessing there are bigger fish to fry first.

The next profile to deal with, which is one you can control, isn't actually in Aperture: it's under System Preferences > Displays > Color. Here is where you set the system-wide profile that controls how a given color from an application is transformed when it's sent to the screen so that it gets displayed as the expected color. Usually, you use a device like a Spyder 3 to measure your monitor, creating this color profile for your specific display. Just be warned that since your perception varies some under different lighting conditions, it's a good idea to calibrate your monitor in a lighting condition you can recreate, such as a dark room. Make sure to watch your monitor's brightness setting, too and to not change it after calibrating!

Back in Aperture, one great and overlooked color-related feature is Onscreen Proofing. As I mentioned earlier, not every device displays color the same way, and if you're adjusting your image for a specific target (e.g. to make a print), it's nice to be able to see how your image will look when transformed to the printer's color space and printed without wasting any paper. Under View > Proofing Profile, you are able to pick what output profile you want to use (e.g. your printer and paper combination), and then select View > Onscreen Proofing to see how your image will look when transformed to that color space. Sometimes, if the devices reproduce colors similarly, it's tough to see if this command is actually doing anything. To clearly see that yes, something is happening, pick one of the default black & white or sepia profiles.

Lastly, under your image presets, you're able to specify what color profile will be embedded into your exported images. I find that this is incredibly useful for my web and email presets. I've set both to always convert my exported image to sRGB so that even if the person looking at my image has never calibrated his monitor, it will still look reasonable. Another example of when this is really handy is if you're sending your images off to be printed elsewhere, even at Costco! Most labs provide color profiles for their printers online for free. If you make a new preset (i.e. one called "Costco") and set it to use the lab's profile, then Aperture will convert your file to the printer's colorspace. Then, when having your image file printed, make sure to select "no color adjustment," and your print will look like how you expect it to look.

Hopefully this brief overview has cleared up any misunderstandings about color management in Aperture that you might have had! If you're really curious, google around for discussions about Adobe 98 vs. ProPhoto vs. sRGB color spaces, and see how they compare to different monitor and printer spaces.





AddThis Social Bookmark Button
Comments (5)

5 Comments

Tym said:

One thing that users may want to keep in mind is that not all browsers display sRGB (or lack of a) colour profile. For example Firefox and other mozilla based browsers on the Mac do not show sRGB correctly. Because of this it took me months to figure out why sRGB looked so different on Firefox on the mac compared to Safari/Aperture. For this reason for months I didn't believe that sRGB was the correct choice for outputting images on the web. Only after reading this most excellent article on colour profiles, I finally understood what was going on. This article saved me many sleepless nights trying to get my images to look correctly. Read page 3 especially to understand what happens on different browsers and platforms:

http://regex.info/blog/photo-tech/color-spaces-page1/

Oleg said:

Can somebody please shed some light on a weird behavior I experience while exporting RAW images taken with my Nikon D70s camera from Aperture: in default export presets I use "sRGB IEC61966-2.1" (also experimented with "Adobe RGB (1998)" and "Use source profile" settings) to output images for Email, web posting, Picasa Web Albums and other non-critical uses.

I then compare the very same image opened side-by-side in color-managed (Preview.app), non-color-managed (Xee.app) viewers and notice clear difference between them, not to mention what I see in Firefox after uploading to Picasa's website. Whereas in Preview the image stays close to what I have in Aperture, other browsers show low-contrasty pictures with washed-out colors.

To counteract this, I developed an Automator workflow that treats selected Aperture versions to a custom export setting (100% size with "Use source profile") and then applies the very same "sRGB IEC61966-2.1" profile using "Apply ColorSync Profile to Images"-action. The result looks virtually the same in Preview/Xee/web-browsers and even uploaded to Facebook/Picasa/Flickr.

What's the difference between Aperture's own profile embedding process and the one I try to simulate in Automator?

My take: Opening an arbitrary image in ColorSync.app I can see three distinct options: "Apply profile", "Assign profile" and "Match to profile" - could it be that Aperture is in fact "assigning", not "applying" the profile (or vice versa)?

Josh Anon said:

Tym, thanks for the article pointer! For anyone interested in color management, I completely agree that it's an excellent read!

Oleg, you might want to check out the article Tym mentioned, as you'll find examples that show how browsers like Firefox aren't color managed at all, which is why the images appear washed out. I'm guessing what your Automator action is doing is actually burning the color transformation into the image so that if something opens it up without being color-calibrated, the pixels have already been adjusted to be sRGBish. In some ways this is bad, because you're changing the data, but with the current state of the unmanaged browser world, it's acceptable.

Guy said:

Great article.

I have Aperture set to color proofing sRGB and same for export, my images look washed out on both Safari and Firefox, I have tried over profiles and always the same. Can't figure it out.

My set up:
- Monitor calibrated with Huey Pro
- Aperture, onscreen proofing sRGB
- export sRGB

Result washed out images in Firefox and Safari.

Sebastian said:

Awesome article, cleared up my confusion.

Recommended for You

Tag Cloud

Stay Connected