Aperture 3.2 upgrade (from 3.1.3) crash continuously

The main problem is in the CPU. I have a Core Duo from 2006 and it crashes ONLY WITH RAW FILES, same as many from here.

The solution is simple; Use TIME MACHINE, not the Vault function, wich is almost useless in Leopard and Snow Leopard, to downgrade your library, and then uninstall Aperture 3 with Appcleaner or similar. Then, reinstall Aperture 3.1.3 Update. It worked for me...but I hope that Apple will solve this soon.

I agree and that's what I did. Interestingly the app store is still saying I should update to 3.2 which you think would have stopped for our configuration (they do with Lion).

I'm hoping there will be a bug fix soon.... I did Not do a Time Machine back up... I have Aperture 3 on a disk... I guess I updated to the 3.1.3... not sure, I thought that updates were for software on your machine so I always updated when updates were available on my machines window...

As I stated before I am not a computer tech, so I am not comfortable moving or changing things around... I have had so called experts move things and everything went haywire because something wasn't backed up correctly, I lost information and I got was, sorry...

I have been shooting with digital for about 5 years, I wanted to start sell my prints at Art festivals, 5 years of images with adjustment to print, maybe lost or are definitely at risk or I will have to pay a tech money I do not have to fix this problem with no guarantee...

Apple want to charge me for a 30 day apple care after I told them the problem No mention about a bug fix.. Did NOT ask the price... long story short, I may be out of business, starting over when money is really tight for me! almost everyone I know is using LightRoom.. Apple is leaving me out in the cold and they really don't seem to care.. I am still trying to be optimistic about a bug fix update from apple ... I guess they don' want to admit to anything so not to be liable.. My hands are tired, it has been 3 days that I have not been able to work on images

http://www.billygphotography.net Here's the start of my site where lots more of my work was going to be featured.. Thanks for listening to my Rant..

Just to add something to the mix - my updated Aperture 3.2 crashes instantly on opening a RAW file and I'm running it on... wait for it... an iMac Core 2 Duo. So it may well be that it's not just Core Duo machines that can't run it. It is of course perfectly possible that it's a totally pants update that urgently needs fixing. Apple, over to you. Hope you're enjoyiing reading all those bug reports - you've had 7 off me alone. [yawn]

(reposting this as it got lost at the end of page 3)

This might be helpful if anyone like me didn't have a time machine backup

How to access 3.2 library in 3.1.3 (maybe other version also)

hold down ALT & COMMAND launch Aperture

the 'Aperture Library First Aid' dialog box will appear

Then hit the Cancel button

Aperture will now load the library.

I have noticed a few odd things like some brush adjestments miss alignment but for the most part it works fine

Just a thought for other sufferers - I'm fortunate in having a time Machine back up of both app and library, but as an added bonus, right from the start, I never trusted the 'all photos in the Library model of working, so 99% of the hundreds of gigs of photos that I have are in folders and aperture has catalogued them from their locations, not stuffing them in the library. I'm very glad I did that now, and when you get all your systems back up and running again, (which, I'm sure you will; the help on this forum is always brilliant) you may want to consider using that model when importing photos. I now use the finder to get RAW pics off the cards straight into a client named folder and then import them left in their current locations into Aperture. It certainly speeds up the import process too!

well! that is most definitely the soundest bit of advice I have heard thus far. I have lost quite a serious amount of faith of how Apple's apparent lack of "care" resounds amongst this community - ie photographers only trying to get their work out - we are not predominately geeks! I thought that was why we paid for their software........

For those whose libraries are crashed, it may be worth pointing out that although the library appears in the Finder as a single object, it is in fact a package. That is to say, 'behind' its iconic facade, is a whole bunch of dated folders, with every single image in there, safe and sound. Now, I haven't tried this, so don't blame me if it doesn't work, but if all else has failed, you possibly could open the package, (simple right click and 'Show Package Contents' does this) and COPY (i.e. DO NOT MOVE THE FILES OUT OF THE LIBRARY!) the files into a new location. Then, you can import tham back into Aperture, and this bit is important (in my opinion) , from their current location and NOT into the library.

Now, I know this will not have all the adjustments etc that have been made to them, BUT, if like me, you're a pro photographer with recent must-have-for-current-client images, then this MAY be a way you can get around the problem of an updated/corrupted library. If, of course, you've managed to get Aperture up and running at all yet. I'm still in process on that one!

This is just surmise and NOT a tried and tested theory. But if you leave the files where they are in the damaged library, then you should be fine, as the library is probably fixable in the future.

If anyone knows that this SHOULDN'T be done, please feel free to correct me. It's just that I know its unlikely that anyone really has lost decades of images. They're on your disk, safe and sound, just not accesible through Aperture at this stage. Try the 'Show Package Contents' trick on the Aperture Library and see.

Dan,

Your advice should be fine. Using the 'Show Package Contents' command (by right-clicking or control-clicking on Aperture library icon) to get inside the Aperture library package is a valid option to retrieve images in an emergency.

Once inside the package, users should see a number of folders inside.

The two folders of interest are:

1 - Masters - this folder has all the originally imported files (it is organized by import date (year folder > month date folder > unique folder for images).

2 - Previews - this folder has any generated previews which will be JPEG files with any adjustments applied when the preview was generated (organized the same as the Masters folder).

Both folders can be safely copied out if needed.

Once the folders are copied out (and the Aperture library package is closed), users can dig down into the folders to locate the images, but as I listed above - the process could take a while because of the way Aperture created the folders to prevent unique lowest level folders. This is required for the database so it knows where each image is.

Hope this helps. 😉

This is an issue with ANY plugin software, i have spent the weekend bouncing around various departmens at Apple and Apple's Express lane has forwarded this issue to Aperture support, let's hope they can fix this promptly!

Running a quad core, and adobe plugins like photoshop, all NIK software as plugins as well!

Me too - having the same problem. Aperture 3.2 crashes consistently when I am attempting to open CR2 files. I have no clue what Apple think they're doing. Now I cannot even get to my images. I am a photographer not a computer geek. Come on Apple. Get this fixed or I will have to start all over again in Adobe something. Seriously!

I allowed Sys.Update to install 3.2 and opened a library. Aperture bombed out after updating the library, then I tried importing some more files and though the folder names were there, no photos were in them.

I resorted to replacing 3.2 with 3.1.3 but have found that the library that was updated couldnt be read, so what do you think I'm doing as I'm typing this? Importing the whole library again!!! 😟

I am NOT impressed!

Helen.

Imploring apple to help me out of this hole. I have a dualcore mac with aperture 3.2 that hangs immediately due to accessing raw CR2 files. I used Time Machine to go back to Aperture 3.1.3 but forgot that my library is not backed up by Time Machine but is instead on Drive 1 of a mirrored raid pair that writes to two drives simultaneously. I thought that was the best way to protect against a drive failure. So now I'm in deep do do running Aperture 3.1.3 with a 3.2 library. Thank you Apple! ;-(

I know there's a lot to read through, but the answers and solutions are on this thread. There's a couple of ways around the problem; sadly it appears that one of them is not yet Aperture 3.2.1 😟

I was wondering if anyone have read any warnings from Apple that this problem would occur on certain machines if you upgraded Aperture from 3.1.3 to 3.2?

Anyone?