Aperture 3.2 upgrade (from 3.1.3) crash continuously

😕 Sorry, but not sure I understand the intent of your question. Are you wondering whether the sufferers of Apple ineptitude on here are wilful causers of their own misery by ignoring warnings that Apple gave us that 3.2 wouldn't work properly or are you asking whether Apple released any warnings?

If it's the former, I'd love to see those warnings! If it's the latter, there certainly weren't any when I used System Update to update Aperture.

I guess I was quite unclear about the intention of my question. Yes, I wanted to know if Apple had released any warnings about this upgrade - 3.2 - would cause the problems many of us now are experiencing. I did not notice any warnings from Apple that this problem would occur on certain machines. If they did not release such warnings, users have a very good case and Apple need to handle this mess promptly.

I certainly do not intend to update versions till it is resolved.

Anyone know if it is possible to 'switch off' the inclusion of Aperture in Software Updates? I've looked in Prefs and cant see anything.

Helen A wrote:

Anyone know if it is possible to 'switch off' the inclusion of Aperture in Software Updates? I've looked in Prefs and cant see anything.

Yes, after Software Update has completed checking for new software click on "Show Details" and you will see a check box next to each proposed upgrade item that can be unchecked before you click on the "Install Items" button.

Automatic software updating must of course be OFF.

Personally I never upgrade anything immediately. Waiting for new updates to prove fully stable in one's setup configuration just makes sense.

HTH

-Allen

This up-grade has caused me to return to using Adobe Lightroom. My dual-core iMac simply crashes Aperture upon openning, it doesn't take any import and is not dependent on RAW or file format it just crashes. What an ill conceived release, no warnings, did they bother to test it or just jump on the big release day bandwagon?

If Apple can not fix this quickly then I'm back to Lightroom and it's quriks for good.

You can also highlight an item in the update detail list and delete it with the delete key. It will ask you if you're sure you want to do that etc.

I for one, will probably never update anything from Apple without first checking mulitple forums ever again. I'm still a little upset about the 10.5.? OS X update that disabled USB speakers. Flippin' monkeys!

Reminder:

Image originals should be backed up in multiple locations prior to import into Aperture or any other images management application.

Yes there are printed workflows that fail to note that critical step. Such manuals, tutorials, etc. are incompetent in that regard.

-Allen

I've yet to get Time Machine to backup an external HDD, so will have to try to remember to do it manually...

I for one, will probably never update anything from Apple without first checking mulitple forums ever again. I'm still a little upset about the 10.5.? OS X update that disabled USB speakers. Flippin' monkeys!

Not monkeys and not just Apple, just the nature of complex graphics software, operating systems and hardware. Those of us who grew with Photoshop expect anomalies with application and OS updates.

Waiting for new updates to prove fully stable in one's setup configuration just makes sense. Expecting vendors to get it instantly perfect has never been feasible in the heavy-graphics world.

-Allen

Well, that's apples and oranges -Allen. Perfect is one issue. Another, wich is the case here, is this software is PERFECTLY unusable or worse yet, disabeling or seriously hamper ones business!

Helen A wrote:

I've yet to get Time Machine to backup an external HDD, so will have to try to remember to do it manually...

Helen-

Masters need only be backed up once (but to multiple backup locations) and that backup should happen immediately after copying to the hard drive from the camera card, before involving Aperture or any other images management app. And before erasing the camera card.

Time Machine is an ongoing regular-routine backup process. Image originals instead need irregularly timed backup, once.

Note also that automatic backup will also back up what is broken. With images I recommend manuals backups of files that have been checked to not be broken.

-Allen

Sorry, 'flippin' monkeys!' is a personal euphemism for 'clucking bells!', which in turn of course is a less personal euphemism for 'fu...' Oh, you get the idea!🙂

However, the reality distortion field has taken a real battering with this one. If any software company ever said, "Wow, there's 30 million lines of code in this baby, and there's bound to be some errors, so please let us know if you find any, and we'll keep working on it until, together, we've got the best darned bit of software out there!" we would happily forgive them.

But they don't say that do they? They say, "Transform your workflow! Work Smarter! Think Different!" and we suck it all up and then the 30 million lines of code fall over. Who's to blame? Us for being suckered, or them for not writing it correctly in the first place?

FWIW, I've been using photoshop since version 2, and it's never locked me out of images before. Nor has it been so unstable it's unusable. In fact, in my experience, Photoshop is a benchmark standard by which all other apps should be tested. Well, the artistic filters menu aside, anyway. 🙂

coverpix wrote:

Well, that's apples and oranges -Allen. Perfect is one issue. Another, wich is the case here, is this software is PERFECTLY unusable or worse yet, disabeling or seriously hamper ones business!

Sorry, we disagree. IMO no one should rush to risk his/her enterprise with brand new software changes because said changes could be "disabeling or seriously hamper ones business!"

Windows XP at 11 years old remained the OS in most usage worldwide because the IT folks running enterprises knew better than to risk their enterprises on new OSs. I am still on 10.6.8 with my developer copy of 10.7 ready to install for months, but I have not done it.

It will happen. With MS scheduled to cease XP support, IT is now shifting from XP to Win7; but do not expect them to go from Win7 to Win8. Similarly I will install 10.7.2 at some point, probably this week or next. I may or may not install Aperture 3.2.

Vendors do a pretty good job but cannot fully pretest. As users it is almost always best for us to wait a bit on new upgrades. And I agree that the vendors should be more cautionary in the language appended to new releases.

-Allen

I'm in agreement with all of that Allen. If nothing else, I've learnt from this debacle to never blindly update anything ever again, without checking the forums first.

Dan Thurgood wrote: ...FWIW, I've been using photoshop since version 2, and it's never locked me out of images before. Nor has it been so unstable it's unusable. In fact, in my experience, Photoshop is a benchmark standard by which all other apps should be tested. Well, the artistic filters menu aside, anyway. 🙂

Dan-

Agreed PS standing alone never locked us out of image files (artistic filters menu aside 😀). However PS never stood alone, we had to maintain color managed workflow and we had to print. And properly color-managed printing broke with about every new PS version (at least in my cloudy unmanaged memory).

And we scanned (my most hated work activity, except for that one crazy co-worker...). Scanners cost more than Macs and the drivers could take years to be updated, if ever. Scanner drivers often broke with PS upgrades, so folks would dedicate a Mac to scanning just to avoid updating OS/PS.

And we had plug-ins for PS that broke with every new PS version, OS version, tide change, etc.

My guess is that Apple today is like PS was with all the various drivers and plug-ins; trying to make it all work is hugely complex undertaking. And today (and I literally mean today) Apple is trying to hook everything together in almost real time via iCloud. Some of the hooks are bound to be broken, and IMO we will see the breaks most easily in heavy apps like Aperture and in communications links like iMessage. The good news is that Apple does control almost all the hooks so at some point soon I expect it all to stabilize.

I am sure Apple would have liked to NOT release iOS5, OS 10.7.2, 10.6 security update, iCloud (huge!), iCloud for Win, iTunes 10.5.1, Aperture 3.2, iPhone 4s and Siri (huge) all in the same week; however Apple did so because they all inter-relate. A very good time to wait a while for things to get the kinks worked out and stabilize.

Unfortunately above when I posted "always wait to upgrade" I knew when I posted it that right now for some of us it is not really possible to wait too long. For anyone who needs the functionality of any of those upgrades (e.g. iPhone 4s buyers like me) we sort of need to upgrade them all. Scary!

-Allen