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

Aperture 4 Wish List

Aperture 4 Wish List


Lens distortion correction.

Panoramic function and 360Âș photo (like QuickTime VR)

Time lapse function. (This would be great)

Better noise reduction.

Film grain emulation.

Twitter integration.

Aperture 3, Mac OS X (10.7.2)

Posted on Dec 28, 2011 3:50 PM

Reply
317 replies

Feb 17, 2012 1:46 PM in response to SiliconTlaco

I really wish Apple would decide what Aperture is to be. A pro app, or a half-a pro app. I am running Aperture 3 concurrent with Lightroom 4 Beta and well, Lightroom is simply better. Aperture is a ram hog that gets my fans moving faster than a cat can scratch its belly. I am running my libraries from a Thunderbolt drive. In Lightroom, not one beach ball, but in Aperture, stop, beach ball, go, stop, beach ball... As others have mentioned, it appears that the inclusion of iPhoto into Aperture, Apple has decided to severly dumb down Aperture for the casual user. It is a shame as Aperture once had a bright future.

Feb 17, 2012 6:07 PM in response to Yer_Man

Hi and thanks for the response. I have rebuilt my library more time than I care to remember. The issues that I am having with Aperture do not exist in Lightroom. I tried to remain faithful to Aperture as well as liking its integration into Mac OSX but for me, it is simply too clunky. I think Aperture has lots of potential but Apple seems to drop the ball time and time again.

Feb 18, 2012 5:08 AM in response to Yer_Man

Sorry but I don't go for the: "it must be your setup" argument. I am not the only one complaining that Aperture is pretty slow. This is know in these very forums as well as complained about on the Internet, so in this case, I will go with the majority as they are saying the same thing as me. Second, I didn't say that LR was the right app for be but that it is the app that does not beach ball. Just because you haven't seen a beach ball doesn't mean that Aperture isn't flawed, because it is.

Feb 18, 2012 6:11 AM in response to Don Trammell

Don Trammell wrote:


I didn't say that LR was the right app


No. But you did say ...


Lightroom is simply better.

Aperture is a ram hog that gets my fans moving faster than a cat can scratch its belly.

In Lightroom, not one beach ball,

but in Aperture, stop, beach ball, go, stop, beach ball...

Apple has decided to severly dumb down Aperture for the casual user.

It is a shame as Aperture once had a bright future.


I can see where someone might think you feel Lightroom is the right app for you. But, Terence didn't say that. He said if Lightroom is the right app for you then go for it.


Why do you use Aperture instead of Lightroom? I just started using Aperture myself and I had the make the decision which one to use. So, I'm interested in why you have chosen (or chosen to stay with) Aperture, given your concerns about how poorly Aperture is working and how well Lightroom is working.


I was also wondering about your experience in comparing the performance of the two. In Aperture you get the beach ball a lot, but you don't get it in Lightroom.


Are the two libraries identical between both apps?

Exact same images and exact same quantity?

Exact same adjustments applied to all the images in both?

Same amount of Keywords applied to all the images in both?

Same amount of ratings and flags applied to all the images in both?

Same number of Albums, books, slide shows, etc?


It would be interesting to know if you've had the chance to make (sorry for the pun) an Apples to Apples comparison between the two, in terms of performance. When I was comparing the two, I compared features and workflow. I never took the time to put together large complex libraries to compare how each would eventually handle all of my images, with all of the various adjustments/developments and organizational tools applied to both.

Feb 18, 2012 6:38 AM in response to 1 Open Loop

You are correct and I need to amend my original statement regarding Lightroom. It is not better per se, but it does not cause the beach ball effect. That being clarified and said, my libraries are both being run from a Thunderbolt drive. Both Aperture and Lightroom have carbon copies of the same files. I can start LR, and Aperture, and after a bit LR runs right along but Aperture (Ap from here on out) starts to beach ball. Where does Ap keep its scratch file? Maybe I can move it to the TB drive but then again, I have to SSD's in my MBP so speed should not be an issue.


I stay with Apertures mainly because I started out with it. Version 1.0 and have continued on with it up to 3.2.2. I have recently tried LR simply because I got it free and I use CS5 and it seems that LR integrates better. Not to mention LR has lens correction features, and a few more things that Ap seems to be missing. Maybe they will appear in 4.x and all of this will be moot. However, to see the amounts of complaints regarding the performance of Ap, it does make me aware to the performance issues that currently plague this version. Again, hopefully we will see an upgrade that renders this a moot point.

Feb 18, 2012 9:53 AM in response to Don Trammell

If you are running the Library off Thunderbolt and the OS and the app on an SSD, then that shouldn't be a bottle neck.


What about processor and GPU? How much memory do you have? Maybe LR is more memory efficient? Although I thought it was 64 bit, which usually means the app likes, or would like more memory.


Do you have Faces turned on? That can slow things down and Lightroom doesn't have an equivalent, at least I didn't think it did.


How big is your Library? I'm only making the move to Aperture now, so the largest Library I currently have is only around 20K images. I have an older Mac Pro, but I never see a spinning beach ball, ever.

Feb 18, 2012 11:01 AM in response to 1 Open Loop

Hi,


I agree. The app and OS are running off the same SSD, along with LR.


Brand new 15 inch MBP with 8 gigs of ram. LR is running in 64 bit mode for sure. Even says so when it starts up.


Faces is turned on, and I agree, it could be checking each photo for a face... I will trun it off and run a test....


My active library has about 10K photos. Actually trying to keep from shooting too much as I will sell my D3S and get a D4 and D800, and I want as much resell as possible.


Not sure why the spinning ball of annoyance appears but it does. Especially when trying to brush in adjustments. Fingers crossed for Aperture 4. 🙂

Feb 18, 2012 1:17 PM in response to Don Trammell

Don,


Without knowing all the details, that is a pretty healthy machine; Aperture should be flying. It certainly chugged right along on my Mac Mini with 4 GB RAM, 500 GB 5k RPM drive and a managed Library of 10k images.


Some thoughts, as I have been playing with Aperture a lot since I bought an SSD. (FWIW, the SSD is nice, but it doesn't seem to do much for or against Aperture, the biggest thing is RAM and, to a lesser degree, the GPU.)


An 8 GB MBP with SSD should simply fly.


If you upgraded, You might want to try the "Bergsma Bash." I found this really helped when I migrated from Aperture 2 to 3.


"He suggests that you first make sure to have done all necessary software updates, then delete all files in the following three folders:

Hard Drive/Library/Caches
Hard Drive/System/Library/Caches
Hard Drive/Users/(Your user)/Library/Caches

Also delete this file:
Hard Drive/Users/(Your user)/Library/Preferences/com.apple.aperture.plist

You might want to create a backup first, just in case. But there shouldn’t be any danger here, since we’re dealing with cache folders and a “settings”-file for Aperture 3 (you’ll have to modify settings again, if you’ve changed them in the first place).

Doing the things above and restarting my Mac, solved my Aperture 3 issues."

No guarantees, but I found it helpful and have never had any problems or beachballs with Aperture 3, except on a 2 GB, 2006 MBP.

The other suggestion is to note exactly when Aperture slows down as, at different times, it uses more disk, processor, or RAM. You may find Activity Monitor useful here. Look especially for paging.


For example, scrolling the library is disk/RAM intensive. Brushing, especially with a large file, is processor intensive; you should see all your cores load up.


It is really annoying when Apple software doesn't "just work" but, in the case of Aperture, there is usually a cure. I have a very old, but healthy machine and Aperture runs very nicely.


If all else fails, make an appointment at your local Apple store (should you have one) and get them to help. There are not many Aperture freaks around, but they can read Activity Monitor.


Best wishes.😉

Aperture 4 Wish List

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.