You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

How I reverted 3.2 library back to 3.1.3

Constant crashes and the need to get my clients work finished called for a little creativity and it really is a simple fix. At least on my old macbook!

Step 1 dug out old version of Aperture and put copy on desk top.

Step 2 tried to open Aperture 3.1.3, no luck! Said library was updated. Grrrrr!!!

Step 3 held down option and apple keys while double clicking AP3.1.3... now we are getting somewhere!

Step 4 Fixed premissions! IT worked !!!! All was good in AP land until I closed and restarted...

Step 5 fix permissions! Grrr.....

Step 6 export sample library and see if it opens nicely in 3.1.3.... Success!!!!!

Step 7 couldnt get back to original library.... had to delete sample library so no others could be found, fixed permissions again and am currently exporting the entire 179 gigs work of work into a new library!

So it is possible to revert!

Open 3.1.3 holding down option and apple

fix permissions

export as new library!

This worked for me and hope it helps others!

now i think I will go back to bed until the new old library is created.......

MacBook, Mac OS X (10.4.11)

Posted on Oct 14, 2011 8:23 AM

18 replies

Ldub42

Level 1

0 points

Oct 24, 2011 5:27 PM in response to uccio2

I normally don't post anything but I will say I also followed Mr. Gandalf53's post and it worked! Thanks!!!

I have Core Duo and this was just what I needed after the 3.2 upgrade. I couldn't access RAW files. Now things are back to normal.

Dec 4, 2013 11:34 AM in response to StephenOrsillo

You are the Man. I had 'upgraded' to Mavericks, had loads of issues and decided to go back to SnowLeopard but I had unfortunately upgraded all of my apple applications for Mavericks which meant that my Aperture libraries were only good for the 3.5. I followed your recipe and I'm back in working order and happy as a baby with a fresh diaper.

Cheers,

Sohio

Level 1

4 points

Apr 14, 2014 11:59 PM in response to StephenOrsillo

This is an excellent post, and I thank you very much for it!

Having experienced some serious issues with Mavericks, I have had to revert to ML. Because the problems didn't start until after about 3-4 months of use, I had updated the Aperture library to the 3.5.1 format. Your fix enabled me to use the lib, even though I am "back" at 3.4.5.

Although this is not the place for it, I feel that I must voice my concerns about Mavericks running on older macs. I have 3 different machines: a mid 2011 MBP and a 2010 MacMini that both work fine with Mavericks. My MacPro, 2009, was fine for a while, really fast and lovely, but then, all of a sudden, I started experiencing constant red memory pressure, even with next to no apps running, and frequently I would get the "apps out of memory" message. Having trawled the net for fixes, unsuccesfully, I clean installed a ML, and feel much better again. Getting the various apps to behave has been greatly helped by this post, which, I am sure, will be a technique that works with other apps too.

Elton

How I reverted 3.2 library back to 3.1.3