I just updated to Aperture 3.3 and I didn't even know the changes were coming, so I was excited. I am a full-time photographer and a full-time Aperture user and I think I noticed 3.3 acting a little more sluggish than normal.
I also just got my new Nikon D800 with super-large, 36 MP photos. And after loading in and editing my first couple of weddings with the new photos from the D800 - Aperture 3.3 is VERY MUCH slower and driving me crazy.
The real slow down seems to be happening when re-rendering the previews after making an adjustment … ANY adjustment. When trying to crank through hundreds of photos, this slow down is costing me valuable time.
Has anyone else experienced a slow-down with A3.3? Is anyone else crunching large files, like those from the D800 through A3.3?
What do you guys think?
I’m using a 27” iMac, 3.4GHz Intel Core i7 with 12GB RAM
Did you Repair your Library before the Upgrade to Lion and AP3.3? Repair or rebuild and then make new vault? both of those updates at once might be hard on your library. Are you Reference or Managed? What is the percentage of your freespace on the HD?
for all of the above check out the FAQ in maintenance and esp HT3805.
However I don’t feel sorry for anyone with a newer camera and Mac than I. :0 :) ;)
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
No I haven’t repaired my library, so i just did for the first time ever.
I use managed files and I don’t use vaults. I’ve got about 35% free space on my hard drive.
Honestly, I haven’t spent any time “under the hood” getting to know Aperture, I just dove in and started swimming.
I think and others can chime in but a Vault is another backup for the library as you know and would be a good idea. Im sure you have other backups of the images but this is a another way do triple check your safety. 35% is good don’t let it get to 10%. Try the other suggests in FAQ Maintence and esp HT3805 sheet from apple.
davidbmoore@mac.com
Twitter= @davidbmoore
Scottsdale AZ
John,
You said you went to Aperture 3.3 and also just got this massive D800 — was this at the same time, or are you comparing rendering speed of the D800 files in Aperture 3.3 to that in Aperture 3.2?
To isolate the issue, create a new library and import a few photos into that, and let’s see if the speed is the same or faster.
@PhotoJoseph
— Have you signed up for the mailing list?
Here is an update!
I just edited engagement photos all shot using my Nikon D3s, and only 12 MPx - and everything went perfectly. And in fact, I might say A 3.3 felt snappier and a little faster than A 3.2.
SO, it appears to be the Nikon D800 36 MPx files that are causing the sluggishness. And it is bad. Here is where I notice it most. I will edit and enhance one image, shadows, exposure, white balance, RAW sharpening, vibrance, contrast, etc. Then LIFT the settings and STAMP them on 10 images. THEN, I go through the 10 images for minor tweaks to cropping, etc. THAT TAKES FOREVER for the STAMPED settings to click in.
I’m even getting the spinning Beach Ball - which I haven’t seen in years!
All that said, this is after cleaning up my hard drive a bit, archiving a bunch of projects, and rebuilding the Aperture Library Database.
But the D800 files is STILL super slow.
Joseph - I’ll give the new library a try.
And as far as the Vault - initially I felt like it slowed me down (v.2.x), so instead I keep the live projects in my Managed library, then when I’m done I will export the project as a new Aperture Library to my external hard drive for storage, then delete the files from my computer Aperture 3 Library. I’m counting on Time Machine to cover my disaster recovery.
Is there a better way?
No performance problem noticed. RAW files typically between 44 - 49MB. I have a “green start” workflow since I use a managed library for each job. iMac 3.4Ghz i7 w/16G RAM, AMD Radeon HD 6970M w/2G memory
John,
Do let us know how the new library test goes.
As far as backup, that’s fine. Nothing wrong with it. Vaults or archived projects, as long as they are backed up you’re good to go!
@PhotoJoseph
— Have you signed up for the mailing list?
I haven’t upgraded to 3.3 yet, but have the D800 and haven’t seen any major performance lag with 3.2.4. Of course, the importing takes a bit longer than it used to with my D300, but I would expect that as the Raw files are normally around 75mb in size.
I’m using a 2.93 ghz i7 with 16 G RAM.
I have just finally received my Nikon D800 too and just for some general info, Aperture SUCKS THOSE BABIES DOWN compared to Lightroom 4.1 which takes almost twice the time, both of my libraries are referenced on a 6TB Thunderbolt LaCie. So a 5 minute download in Aperture is (approx) 9ish minutes in Lightroom 4.1 and god help you if you shoot any video for lightroom, you may as well just play it in, or tether it as I think it takes longer but I haven’t timed it.
75MB raw files….damn. I wasn’t expecting much more than 60MB… How large are the D3s files? I’m a Canon guy, so I don’t know too much about NEF, but I’m assuming they’re both 14 bit and include the jpeg preview for the camera?
Do you know if Aperture is also trying to generate preview files while you’re editing the D800 files? And does the situation improve if you’re only using Aperture on your Mac? 12GB is definitely a lot of RAM, but if you’re doing lots of multitasking it can disappear quickly. I would try changing your preview settings to make sure it says “Camera Previews” under the Import tab of Aperture’s preferences.
Also, one other thing that’s worth pointing out about Vaults: they’re a great strategy for backing up a library, but they do not included the referenced files. However, even if you’re library is 100% referenced I still recommend using a Vault because it backs up all your other Aperture data like key commands, preferences, all the presets, etc. Those things are copied over if you just backup your library file/folder regularly. And while the image files are the most important, backing up the library will save you tons of time if you ever need to restore since you would otherwise lose all you project, album, light tables, web pages, etc work.
@John Wohlfeil - What is the configuration of your system? How much memory?
Photographer | https://www.walterrowe.com | https://instagram.com/walter.rowe.photo
So I upgraded to 3.3 last night and can confirm that the D800 files are taking a LOT longer to process than when I was handling them in 3.2.4. The importing is fast, but the editing is slower. Of course, it’s not a controlled environment as I don’t have 3.2.4 any more to compare the speed, but at least I am finding things a bit slower than I would like.