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

Level 1

7 points

Aperture 3 hanging... and hanging... and chewing...

was totally stoked about upgrading today. now i'm kicking myself in the pants for doing it so quickly.

when i came home for lunch, i installed A3, typed in my purchased Upgrade serial, and then allowed A3 to upgrade my old A2 library. obviously, this was gonna take awhile, so i left it running whilst i went back to the office. when i returned home, i discovered my MBP had actually frozen. ok, that was weird. i had to do a hard shut down (hold down power button) and then reboot. everything comes back fine, i reopen A3, and its just processing "files." i let that go for about 15 minutes, come back, and the MBP has just sloooooowed to a crawl. i mean awful. it was like being at a concert: beach balls of death EVERYWHERE.

i didn't want to, but i had to force quit A3 to do anything else. so i did that, did a normal Restart, and then reopened A3. still processing, same chain of events. i mean, it was terrible.

so finally, FINALLY, i get down to the last 12 "files" or "items" or whatever, and A3 seems to be really stuck on these last 12. it'll just sit there and churn away whilst eating up all system resources and giving my BBODs whenever i move the cursor around.

so... what's going on here? i've tried repairing the database as outlined in the recently update Aperture manual (to no real end; didn't fix anything), and my next step, i suppose, is rebuilding the database. is anyone else having a problem like this? i've seen lots of folks having fairly terrible times with the move, but nothing quite like this. i've a fairly large library (not really giant by any means).

so: help!

2.26gHz Intel MacBook Pro, Mac OS X (10.6.2)

Posted on Feb 9, 2010 8:56 PM

441 replies

Feb 10, 2010 9:05 PM in response to lukelucas

I am upgrading my 370GB A2 library to A3.

The progress bar has been stuck on "4% updating master metadata" for 6 hours now. No change.

The iMac is responsive and the iStat process monitor says A3 is using 190% of resources.

I'm wondering how long I should wait if the progress bar does not move at all?

Feb 10, 2010 9:16 PM in response to travelboy

Travelboy - I had a similar issue - check here:
http://discussions.apple.com/thread.jspa?threadID=2332345&tstart=0

Feb 10, 2010 9:47 PM in response to demoneyes

I would point out that the installation instructions (along with various knowledge base articles like the following) are very clear that the library upgrade can take quite a long time, especially with large libraries. Don't say they didn't warn ya!

With that said, happily I can report that my library upgrade is progressing well on my 27" iMac. So far, anyway.

My library (which contains some managed images, but mostly referenced) is 75GB in size.

Aperture has been running for a bit over 2 hours, and is half done.

Worthy of note: I have 8 GB of ram, but even as Aperture is upgrading the library, I have 2.5 GB free - and often this jumps to 3 GB free. And I have Firefox, MS Excel, iTunes, Mail, and several other apps running. In fact, *Aperture is only taking 450 MB of "real memory", and generally around 500 MB of virtual memory.*

Based on this limited experience, I cannot understand why others think the upgrade is so very ram-hungry.

http://support.apple.com/kb/HT3945

Enjoy!

Jim

Feb 10, 2010 9:56 PM in response to lukelucas

Sorry, I believe you are mistaken.

There are two different potential upgrades - one is optional, the other is not.

Aperture 3 uses a different library structure than Aperture 2, so you MUST upgrade your Aperture 2 library if you wish to use it with Aperture 3. (Note that this process creates a new library, and seems to leave the Aperture 2 library untouched, and appends "_original" to the file name.)

The optional step of upgrading images (as opposed to library structure) is only necessary if you want to use the new tools such as brushes and curves. You can do it along with the library update, or do it later.

Please take a look here for more information:

http://support.apple.com/kb/HT3945

Enjoy!

Jim

Feb 10, 2010 10:12 PM in response to MagicMacMan717

The library upgrade process uses considerable disk space because it leaves your Aperture 2 library intact, and creates a new copy which it upgrades.

Seems to me that this is a good move, for safety.

lukelucas Author

Level 1

7 points

Feb 10, 2010 10:20 PM in response to Jim Warthman

even then, though, Aperture 3 (so far as I can tell) won't automagically reprocess RAW files that weren't initially imported using "the latest RAW processing" that Apple offers. so if I want to go back and edit, say... our pictures from Seattle this past summer with the new fancy brushes and curves, I have to go in and tell Aperture that I want to Reprocess Masters. I know this, 'cause I just checked outta' curiosity. 😉

my final bit for the night was to rebuild the 2.1.4 library in Aperture 2.1.4. then I went through, weeded out some weird, straggling projects, repaired permissions via Disk Utility, and rebooted. after that, I fired up A3 and had it import my 2.1.4 library (with the "upgrade blah blah blah" box checkede ON). as of now, as i'm in bed, it's working on generating a little over 120 thumbnails. after that, I've no idea what'll happen next. hopefully when the baby gets up, I'll be ale to sneak a peek and see if all went according to plan OR my MBP is in meltdown mode.

Feb 10, 2010 10:23 PM in response to Matthew Bergsma

Matthew Bergsma wrote:

Also, for those who haven't upgraded yet, I recommend relocating your masters outside of the library first, and "updating" by using File->import library... This will keep your version 2 library intact, and give you a clean aperture 3 library.

Matthew, good advice to relocate the masters first.

As for your second point, I believe the standard library upgrade accomplishes the same thing. That's what I did, and I now have a new "Aperture Library", and the old "Aperture Library_original" in the same folder. I'm pretty sure my version 2 library is intact!

Enjoy!

Jim

Feb 10, 2010 10:57 PM in response to lukelucas

Those of you that gave trouble with faces should try deleting all previews in your library. Aperture have never been so quick. And previews can be regenerated after the faces scan is done.

Feb 10, 2010 11:03 PM in response to lukelucas

OMG, I am in Aperture ****. I am using a MacPro with 9 gigs of memory and everything is just crawling till it crashes. And crashes it does every few minutes. So now I am just letting it detect faces over night as suggested. Hopefully once this is done things will get back to normal. Meanwhile I can't use even my mail as all the power seems to be routed to Aperture if that makes any sense.

Clem

Level 3

701 points

Feb 10, 2010 11:19 PM in response to Community User

Scott, with a lg library its best to just leave it alone and come back later ( ie, the next day) and check on progress. I wouldn't quit it. Does the console say anything?

Feb 11, 2010 12:19 AM in response to danielhoughton

What are you seeing? Did you resolve your issue? I believe I'm having the same problem.

I get to:
Upgrading Library 7% complete (updating master metadata - 5,068 remaining)

After restoring from a file vault with Aperture 2, I get to the same spot, with or without previews. I tried deleting previews within Aperture and reimporting. I got to the same exact spot as before. The computer becomes nearly unresponsive, and I have to force quit Aperture after hours of sitting at 5,068 remaining.

I have 6GB of RAM, a 80GB and 22,000 image library.

Message was edited by: apple_enthusiast

ruimoura

Level 1

0 points

Feb 11, 2010 1:07 AM in response to lukelucas

My short take on Aperture 3 (with a test library with about 2GB of photos).

Places crashes Aperture 80% of the time.
Faces works fine.
The Loupe doesn´t minimize if it's on when i minimize Aperture, i get the Loupe on the desktop, it's somehow funny.
It's way faster than Aperture 2, and i mean really, really faster, on my Macbook 3.1 with Intel graphics.
Flickr export is so bad it hurts, they could have fixed it since iPhoto 09, but they just copied it. Waiting for a plugin to work on the new version.
When i open the Loupe, if i move it around, i get a square line around it (graphical glitches). It's really annoying.

Other than this, i'm enjoying Aperture 3 a lot, it's a game changer, totally, they just need to squash some bugs.

Kawanaut

Level 1

55 points

Feb 11, 2010 1:16 AM in response to lukelucas

I kept an eye on Activity Monitor as I did adjustments to a picture. The more adjustments I do (brushes, retouch etc) the more memory is used - eventually, all 4GB of my MacBook Pro memory will be gone. At that point, I can forget all about doing anything but wait for Aperture to finish. Often I will save much time by simply restarting Aperture and continue from where I left off, rather than waiting 10-30 seconds for each retouch.

Unfortunately my unibody 2.4GHZ MacBook Pro is from late 2008 so I don't think it will take more than 4GB of memory, otherwise I would be out buying 8GB of memory right now!!

Feb 11, 2010 1:56 AM in response to ruimoura

Agreed,

1. crashed on me about 15 times yesterday with a library of 50 images (D700 NEF files).

2. Loupe takes too long to load a preview image. Its really painful.

3. Sliders: very slow, for example updates of sliders to images. The sliders slide quickly enough but the effects take some time, which really changes the experience of the programme.

4. Disappearing cursor.

5. Flickr export is useless and very badly designed.

6. A real CPU hog.

7. Oh, and did I say that this programme crashes constantly? I would have thought a 'pro' or 'industrial' software application would address reliability.

So to summarise: very unstable and poor performance on my 2009 Macbook pro with 4gb of RAM.

They have a lot of bugs to fix and performance issues to resolve. I expect an update very shortly.

My biggest disappointment in terms of features is the lack of lens correction.

Feb 11, 2010 2:03 AM in response to Alex Wilkie

Oh,

and just tried to email some photos (8) at JPEG small. Was wondering why mail kept informing me that it couldn't send the mail. Turned out the mail was 156mb in size. Looks like another bug.

Aperture 3 hanging... and hanging... and chewing...