This problem appeared on the Aperture discussion pages almost as soon as Snow Leopard was released and seems to afflict a considerable number of users. I followed the advice to give Apple some feedback on this, as many others have done. To date there has been NO RESPONSE from Apple, not even an acknowledgement that it is a known issue, much less any serious attempt to fix it. I payed good money for both Aperture and Snow Leopard, and to have a new release of an OS break a core Apple product is beyond belief. Many folks are seriously considering switching to Adobe Lightroom, but again that costs more money, so we really are stuck until Apple stops behaving like Microsoft (releasing bruised versions of their OS) and fixes this.
anybody figure this one out?
applecare wouldn't help me because my care i over, but i was at the genius bar yesterday and the guy tried to...he suggested checking consistency and rebuilding my database, which i did. didn't help.
here's what's happening w/me:
With the green screen situation, each time I do an edit and try to work with a single shot, it suddenly gets a colored layer over it of weird flourescent (sp) colors (mainly greens, but also magenta, yellow, sometimes a mix I think. Looks like noise--and looks corrupted.) Usually that image stays that way until I drag the image onto my desktop and then the image is fine and I can use it.
also getting the spinning beachball. do you think they're related?
ps I have Ap 2.1.4 and I'm on an iMac with SL 10.6.2. Could be SL related, but I hope not.
Do as the above poster said (terence devlin) and submit a bug report to Apple. You can do it from within the program via the Aperture or File menu (forgot which at the moment).
The short answer to your assumption is that yes SL does break the use of Aperture for some. (I am one of them). It is not necessarily the Aperture program update (2.1.4) itself as I have reinstalled Aperture on Leopard with all updates (10.5.8 and 2.1.4) and have had no issues.
As far as I can tell, the problem lies in the card drivers, Snow Leopard Code and Aperture programming code regarding OpenGL and/or CoreGraphics.
To answer your anticipated question about my trouble shooting:
I have done (in no particular order) the font, plist, permissions, new user account, new library, rebuild library, vacuum library, visual inspection of the motherboard (internal) capacitors, voltage/current checks on power supply, new ram, new HD...it became a quest as you can see.... I changed system settings, tried hidden parameter settings, ran developer toolkit utilities to search for error messages and odd behavior. I ran console and watched each line by line message as I performed each Aperture adjustment/task (or at least tried to...)
Finally I reinstalled both Operating Systems (Leopard and Snow Leopard) separately on new drives AND installed Aperture 2.1.4 with a 150GB 30,000 image library on each drive separately. No peripherals, clean systems. No haxies (I do not use them) Nothing but the OS and Aperture and the same library. Aperture performed flawlessly on an external bootable drive in Leopard but not in Snow Leopard..in fact it performed worse and I had the corruption duly noted above and elsewhere.
In my opinion, Apple should be shamed for being so tight lipped about this. It is a serious flaw that should be acknowledged to users. But to admit this without a patch or software solution in the works is an unspoken implication to have customers purchase new computers for a fix.
Anyone notice the released updates for Logic Pro (2 since the release of SL) and Mainstage (also 2 since the release of SL) and Remote Desktop (also 2 since release of SL).....you get the idea? Aperture? Zilch.
I am having the same problem. Just realised it can only be a Snow leopard OS Bug. A 2.14 started to show this occasionally after 10.6 upgrade. Aperture 3.0 does it pretty much full time, and makes the use of Brushes impossible.
Reported Bug, but suspect that Apple no longer has the skills on board to fix a problem with an ATI Radeon X1600 driver (especially as it cannot support CoreCL)
Not too happy with the fact that my amazing Mac has been obsoleted as fast as a Windows PC.
Sadder and Wiser
Are you sure that it is definitely a graphics card problem? I don't want to go out and buy a new mac just because Apple can't support it's own (not so old) hardware, but as it stands Aperture 3 is a right mess while this artifact keeps intruding on my workflow.
I have reported the fault to Apple, but given previous experience with the same bug report for Aperture 2 (or Snow Leopard as the case may be) I don't hold out any hope of a response.
This must be the worst bug fiasco I have encountered since I used to deal heavily with Microsoft products. I just expected Apple to rise above such mediocre customer service.
'Nuff said, ******** makes me feel better, but doesn't solve the problem.
I had the same problems. Green blocks after nearly every adjustment. The 301 update did nothing to fix that. So I dug a little further (in Google, that is ) Seems to have gone away after putting Aperture in 32 bit mode. Which - on a 2.15 GHz iMac with 2 GB ram seems not an unreasonable option.
It seems to be running a little faster than A2 but now I've got it fixed I can do more testing (and actually start enjoying A3 I hope...) and see if it stays away.
Use to get this type problem, but instead the pics would turn white. So I would close the program, shut down the machine, and step out for awhile. Come back, turn the machine back on, start Aperture and it would start working properly.
Sometimes the program crashes but doesnt shut off. A hard or soft reboot is in order when this happens.
Glad I found this thread, though I'm not too happy to see that there doesn't seem to be a solution - yet.
Aperture 3 was running just fine - and then I upgraded to Snow Leopard...in happiness because Aperture recently decided to support my camera's RAW...only to find these weird artifacts going on. As with others it is not all the time. Thankfully, it has not hurt the actual photograph.
I'm not quite sure what one earlier poster meant about changing the BIts for Aperture but will look into this.
It's too bad and here's hoping for a definitive update.
One more voice to add. For me the problem started with an upgrade to SL while using 2.14. Now running 3.01 under SL 10.6.2 and the problem is worse. Seems that any adjustment that affects the tonal range of the photo will trigger the bug. As others have noted, use of brushes is especially effective at making things blow up.
Have many screen shots that I could post for comparison.