A lot of Aperture’s functionality comes not from Aperture itself, but from Core Image, lower level operating system features that Aperture can tap into. For example, the Mac OS has built-in routines for opening and displaying various file types such as JPEGs, TIFFs, GIFs, PNGs, and Photoshop documents. While this helps integrate Aperture with other OS features, it also means that, as Aperture users, we’re sometimes subject to the bugs and errors of other OS functions.
Consider this image, which I shot in London.
Because I wanted to perform a separate set of edits on the sky, I used Photoshop to create an alpha channel mask so that I could manipulate the sky and the building separately. I used a number of normal Photoshop masking operations to create this alpha channel.
When I import this Photoshop document into Aperture, though, I see this in the thumbnail:
and this in the Viewer pane:
The problem is that OS 10.4.8 has a bug in its Photoshop routines that causes some Photoshop documents that have alpha channels to render improperly (this bug does not affect Photoshop itself, as it uses its own routines for interpreting files). If you open this same image in iPhoto or Preview or any other app that relies on the OS-level Photoshop renderer, you’ll see the same results. (This bug has been around for a few OS revs now. If you’re using Aperture 1.5, you must be running 10.4.8.)
To get around this, use Photoshop to save a separate version of your document, delete any alpha channels from this document, and import the new version into Aperture. I like to keep the old version in Aperture also, just in case I want to perform additional Photoshop edits that depend on my mask. It’s easy enough to keep them both stacked together, giving me quick access to the Aperture-friendly version, and the complete, masked version.
Note that layer masks attached to a Photoshop layer do NOT cause this problem. Only stand-alone alpha channels.