This started happening with the update to 3.4.5 (I think).
When I start an update to a Vault I get a beach ball for a long time - it seems to depend on how many changes there are, but I've seen as long as ~30 min!!! - and Activity Monitor shows Aperture as Not Responding. Eventually, I get the dialogue asking for confirmation (Update/Don't Update). After that, the actual update proceeds at the speed it's always done.
My Vaults are on USB disks attached to my Airport Extreme Base Station but if I connect them locally then this long delay doesn't occur (yes, I know locally attached disks are faster, but not this much faster).
I've tried creating new Vaults rather than updating existing ones and also I've got a new USB disk, but the problem remains. The disks are formatted HFS+ and shared using AFP.
Any ideas? HAs anyone else seen this?
I have been fighting this exact same problem for quite a while. When updating to the vault on my Time Capsule’s internal drive, I get the spinning beach ball for almost an hour after clicking on vault’s update arrow but before getting the “Update vault?” message. The same process takes just a few minutes when updating to a vault on a USB 3.0 external drive. Once I say yes to the “Update vault?” message, though, the vault is updated normally.
15” early 2008 MB Pro, 2.4 GHz Intel Core 2 Duo, 5-GB RAM, OS X 10.8.4
Aperture 3.4.5, 200-GB library size, all photos are managed, have repaired and rebuilt the library
2008 Time Capsule with 1-TB drive, have tried wireless and ethernet (WiFi disabled) connections to the TC drive
Hi Mark
30 min is not long if your lib is big and you have an older compurter with 4gb ram. Need more info there, plus r u referenced or Managed. The rebuild is dependent on how much has been added since last updated. When Activiey Monitor says Not Responding Do not Respond to that, its stll working and normal. Ive always avoided networked connected reference lib and vaults for the reason you seem to be describing. Would love someone with wireless connection experience to chime in. I feel like the doctor who is told that “It hurts when I do this” and he sheepishly says don’t do that. Some people have stopped using Valuts and just copy the lib over the older back up, but that takes hours. good luck
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
Hi,
My Library is Referenced (apart from the small number of managed iages in PhotoStream) and is ~27GB and the Vaults are ~17GB
I’m using a retina MBP with 16GB RAM, so not an old, slow computer.
I realize that it is still running despite Not Responding as the CPU usage varies (but only ~5%) and the memory usage slowly increases.
However, the key point is that this suddenly started happening and I haven’t suddenly added thousands of photos or done any major editing etc.
Well if you notice a slow down then something probably did change. Do you think you need to rebuild the lib with the three steps of permissions, Repair Data, Rebuild data? Have you imported any Video files that might be corrupted or images from a card that is starting to go bad? All previews and thumbnails show up fine? Do you automatically build previews on import? What other programs do you use with AP Photoshop layers, Nik, etc. How are the permissions on your MBA? I have always had similar problems with Vaults and now that I have 16GB ram It goes quicker, but my point is that Vaults are tricky and often take longer than Id like. Back to helping you …. you may have a corrupted file. good luck
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
I’ve done Repair but stopped short of Rebuild. I did the repair because I had a problem with a vault but Aperture kept complaining that the Library was corrupt and needed to be repaired, but it only happened with one of my Vaults (repeatedly). I deleted that Vault and created a new one and haven’t had the problem again (and never did on the other Vault - I have two vaults on different USB disks).
Yes, previews are automatically created on import and I can see no corruption in any images, either in the last few imported projects or a random selection of others.
I don’t import videos into Aperture.
Perhaps I will do a full Rebuild and see if that does the trick.
Ive done multiple rebuilds … I dont think it hurts to do them. They can take awhile.
Cheers
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
Oh after a rebuild check smart albums for managed and referenced images. Sometimes I had files show up in managed when they are suppose to be referenced. Also a smart album of missing images, those are harder to resolve but hopefully you just point the data base in the correct direction of the missing images. All my images have keyword and copyrights so smart albums can check that easily and give me a heads up of still missing database info. After all that I waive a chicken bone over the computer and sing There is a Hole in the Bucket.
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
I’m running Rebuild as I type this.
I do have a handful of images lying around in Masters inside the Library but these appear to be dross left lying around and connected to PhotoStream as they are all <100kB and are only 720x540 size.
I wonder if Rebuild will remove these orphans? If not, is it safe to manually delete them in Finder?
I posted in this thread on the Apple Support forums about it and got some feedback.