Guys:
I'm with you re concerns and frustration. I love Aperture when it works and I love the integration, but this is a very bad release. To your point TreenM, I would recommend waiting 'til this settles down to upgrade if I were considering it now, rather than having already taken the plunge; wait until a patch comes out. Also, as Jim noted, the Aperture team is obviously aware and working it. As I indicated earlier in this thread, they took the initiative (obviously were monitoring this discussion) and contacted me yesterday. I've sent them my System Profile and they are overnighting a hard drive for me to load my library & overnight it back so they can try try to duplicate, analyze, and fix the issue. I've very impressed with their being proactive, but disappointed that the 3.3 release has such major issues. I want to stay the course with Aperture, but even though I've finally recovered, I will withhold my judgement until I see the response and feel confident in the path forward
Ted
PS - One more possibly useful data point. I was able to recover everything (images with both embedded and referenced masters). I did have to do a restore from the Vault & Aperture had to do another full (successful this time) upgrade. I then imported a few more images into Aperture and kicked off a Vault backup to see how that would work. The Vault had to be reprocessed in some way by 3.3 and after 6 or 7 hours is still chugging. We'll see where it is in the morning of Day 3.
