Aperture 3.2 upgrade (from 3.1.3) crash continuously

I only use time machine for the job I am working on ( I keep a separate library for each job). After that I move it to two external hard drives. I must admit I did not realise time machine recopies the whole folder if there is any change. I just leave it clicking away . Perhaps I need to relook at my work-flow . .

I've been told by that there is a fix out coming. I've been trying for 14 days to get my TIFF images to load. They won't. So I have kept my ear on the tracks through this subject thread to try to understand and find a solution to the 3.2 crash issue. My library is copied to 3.2. I can't load 3.1 and revert. I didn't back up into Time Machine. Now that I've heard that Time Machine re-copies the entire library because of one modified file, should I be glad I didn't use Time Machine? Read these threads. There are so many varied issues pertaining to the 3.2 upgrade issue, that at this point in only seems reasonable to stop chasing ones tail, perhaps creating more issues in the process. I'm at the mercy of a fix out, and that's the reality of it, so I've accepted it.

Pathology:

Upgraded to 3.2 from 3.1, crashing Tiffs files upon opening. It loads and sticks, then quits.

Jpegs will load and will allow editing. All thumbnails are up and visible. Can't click on a Tiff or it will quit.

Cannot import any file, Jpeg or Tiff.

I've been frustrated by all this, and have expressed that on this forum, and I'm sorry about that.

I've spoken to techs, they remind me that there is a fix out in the works for Aperture 3.2.

I await the fix because I like Aperture, and the way it works, while it worked.

Many of my Tiffs are on Cd, so theres my backup. A couple of those Cds are old and won't load anymore, but that is beside the 3.2 crash issue. I'll just get the Cds redone.

The 'issue' of Time Machine backing up entire libraries every time is a new one to me. I've been using it for over a year and once it's done its first back up, it works like all other back up systems ever have - it just records the changes. I regularly upload around 12gigs of photos to my system and TM has never given me the impression that it's backing up the whole library all over again.

And let's face it, even if it took 3 hours or whatever to backup every time you gave it a few photos, I think this thread alone has shown the dangers of no backup at all. Even nightmarishly slow backup is better than no backup at all.

I've just checked the size of my photography folder and it's 637GB, so if TM was backing that up in its entirety every time, I think I'd know about it 😁

To be honest, let's face it, Aperture has never been very stable anyway! I'm back to 3.1.3 and it's back to the old game of it locking up at random in full screen mode, such that you have to force restart the machine to get control back again. At least the 3.2 disaster upgrade solved that problem for me - when Aperture 3.2 crashed after 30 seconds, every time, it always threw itself right out of the system, leaving everything else intact. Maybe that's an improvement?😕

I saw a blog today that mentioned that 3.2 was meant for Lion users to improve performance. I wonder whether that is also an issue? How many of us who couldn't get it to work were on Lion? I'm not... maybe it shouldn't have been released as a general update - for Lion users only?

I'm not a Lion user. Again Savyer people than me having issues with this. Optimism hopefully will prevail and provide us with a efficient 3.2, or Aperture 4 program that will save the day. I shouldn't read tea leaves as to what's happening with the sofware engineers, but it seems likley that as they strive to find a solution to the 3.2 issue, that they wiil clear up other so called, "inherent" issues that plagued Aperture as they go along. In other words, I would think passing out a band aid on this is not their intent. I'm looking forward to a clean and efficient Photographic edting program that was the original intention of Aperture, or at least hat was the way it was billed.

I'm done with going around in circles. I wait patiently for a fix.

Thank you so much frej. I have been struggling with this problem on my iMac since a routine software upgrade. Now that you have provided this information I can stop looking for an answer and pray for a code update. I will try and restore to the day before the update from my Time Machine backup.

Best regards.

GOOD NEWS - the 3.2.1 fix released today works!

I am running an Intel Core Duo and my Aperture has been impossible to use since the release of 3.2.

This fix seems to have sorted everything rout, and no more problems with Nik plug-ins or RAW files.

Thanks to everyone who worked on fixing this.

through software update...

... if i download the dmg from the downloadpage...

what is going on here? I know my machines. But obviously not well enough. Any help would be greatly appreciated.

I get the same "can't be installed error" when trying to take my iphone or ipads up to iOS5 through iTunes.

help- sleepless in nova scotia.

So you can't update anything? One was the last time you were able to update your software? Any software? Sounds like an OS issue as opposed to an Aperture one.

Just did today's update... Aperture appears to be working YAY! I was able to open, go to a gallery and export.. so far so good... When I open the library again who knows. I'm so glad to have my images back..

@ Pete Mitchell I might try downloading again as well.

YES! YES! YES! Thank you to all that fixed this. The nightmare is over for now. I know I got carried away a couple of times. But hey! Just loaded Aperture 3.2.1, and it works. It fixed the issues that I had and it seems I can move on and get back to a process of producing pictures. The Tiff issue I've spoken of is fixed, they load, 3 or 4 seconds, and stays. I've already edited one, and it all seems good. I like that after closing Aperture, then reopening, it reopens where I left off. Good stuff. Apple, Good job.

Anyone know what it did to all the vertical crops that we had to do "backwards" at a "horizontal" aspect ratio? It didn't switch them to actually being horizontal did they?

Some of my jpegs are swithched from vertical to horizontal. They were originally horizontal. Some stayed.

I just timed with a stop watch, a Tiff load. Its 7 seconds when first located. Intantly if revisited. Thats faster than before the 3.2 update.

Well, that is good news. At least we know that Apple does care. I'm still going to wait a bit before updating this time - I've shot four weddings this week and can't risk anything going wrong again. Really glad to hear that folks are back up and running again though!🙂

Did the 3.2.1 update with out issue!

I'm happy to be working again, but I will be traiding up from a 2006 to a 2007-2010 machine reguardless. The traidup is cheep and I'd like more memory.

Good luck everybody,

Brian in Atascadero, CA