Apple Event: May 7th at 7 am PT

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

Aperture. Time to quit.

I've used Aperture since it came out. It's now unusable, needs to be force quit all the time. When I re-open, I'm greeted by a status bar, telling me that it's waiting for Time Machine to finish backing up library. I don't use time machine, it's turned off, and I have no Time Machine enabled Disks.


I think it's time to give up on this pos software, I'm on a new Macbook pro with 8gb ram, and it's rubbish. I've run Onyx, repaired permissions, pulled my hair out, it makes no difference.


Lightroom seems to be the only option, taking 6 libraries with 1TB of images with me.


I'm unhappy about that, but I can't deal with an allegedly pro app that can't deal with the basics.

If it's not the application, then it's the machine. I bought it because it was just supposed to work, but maybe they've given up on that bit of marketing.


Adios.

Macbook Pro

Posted on Apr 30, 2012 4:05 PM

Reply
21 replies

May 2, 2012 3:02 PM in response to jb-7

jb-7 wrote:


I have a feeling that it might be easier to maintain a snappy library with a small number of small images, but I need a Pro Program, hence my frustration.

Joseph -- we're telling you there is something wrong with your installation on your hardware. You don't need a "better" program. Almost everyone who posts regularly here experiences either "snappy" performance or understands where and why it is limited.


The suggestion to try a new, small, Library is a good one -- standard trouble-shooting. When you say "I'm not sure ... " and don't try what is suggested, you defeat the purpose of trouble-shooting, which is to fix your trouble.

May 2, 2012 5:19 PM in response to jb-7

jb-7 wrote:

I presume your enquiry relates to another issue?

Correct. Aperture will run a 100k+ images Library, no problem if the workflow is properly set up; I did that on a 2006 MBP with 3 GB RAM. We are trying to find out what is wrong with your installation, hardware or workflow. Suppose for instance you have ONE corrupt image file in the existing Library that crashes Aperture under certain conditions.


Also you mention Time Machine messages that sound nonsensical. Is TM turned OFF under System Preferences?

May 4, 2012 8:11 AM in response to SierraDragon

Hello- sorry for the late reply-


Yes, I ran a large library on a 2006 MBP myself, but with only 2Gb ram...

When I migrated, I split them into smaller libraries, which is a bit unweildy, but seemed like a good idea, approaching 100k images.


It's a pity that there is no tool to identify a corrupt image- apart form a crash. My intermittent problem re-surfaced, and I identified an image which might have been an issue, and deleted it.


It was large, and I thought its 155Mb might have been the cause of the slowdown, but perhaps it was also corrupt. In any case, the library seems to perform better without it. There may be others too; next time I'm forced to quit, I'll go searching again.


I also opened a new library in a new user account- there is no doubt, Aperture preforms flawlessly with just a few new images. It's possible that there are deeper issues too, perhaps at system level, but repairing new computers is not one of my favoured pastimes, and I consider it more of an unnecessary chore than an interesting challenge.


And yes, Time Machine is turned off in System Preferences. I've never used it on this machine, though there is a slight chance that the disk on which the referenced files reside might once have been selected as a backup disk for Time Machine on a previous system. Unlikely, since I've never used TIme Machine, but that's not to say that I haven't idly opened it at some stage.


Decanting and formatting a pair of 1.5 Tb disks is not to be taken lightly, and I'd need more disks to do it, so I can't see that happening unless absolutely necessary...


Thanks again for the assistance, much appreciated.




joseph

May 4, 2012 8:30 AM in response to jb-7

jb-7 wrote:


I also opened a new library in a new user account- there is no doubt, Aperture preforms flawlessly with just a few new images.

Image count should not matter in a well set up workflow (except that no individual Project should exceed 400-500 image files). The point of the new Library test is not the performance "with just a few new images" but rather the fact that Aperture is performing flawlessly with the new Library. That implies something about the old Library is flawed.


Perhaps try just using the new Library (and I strongly recommend maintaining it as referenced rather than managed) for all new image files.


-Allen

May 4, 2012 8:51 AM in response to SierraDragon

I also opened a new library in a new user account- there is no doubt, Aperture preforms flawlessly with just a few new images.


Allen, I am not quite so sure about this:


The point of the new Library test is not the performance "with just a few new images" but rather the fact that Aperture is performing flawlessly with the new Library. That implies something about the old Library is flawed.

The above test mix two tests in one:

  • new user account
  • new, small library


So the better performance on a new library in a new user account also could mean, that the preference files in the in the regular user account need fixing. To be sure if it is the regular Aperture Library and not the Aperture Preferences (or other preferences, e.g. Time Machine) that need fixing, we would also need a test run with a new Aperture Library in the regular user account.


Don't you think so?


Regards

Léonie

May 4, 2012 1:46 PM in response to léonie

leonieDF wrote:


I also opened a new library in a new user account- there is no doubt, Aperture preforms flawlessly with just a few new images.


Allen, I am not quite so sure about this:


The point of the new Library test is not the performance "with just a few new images" but rather the fact that Aperture is performing flawlessly with the new Library. That implies something about the old Library is flawed.

The above test mix two tests in one:

  • new user account
  • new, small library


So the better performance on a new library in a new user account also could mean, that the preference files in the in the regular user account need fixing. To be sure if it is the regular Aperture Library and not the Aperture Preferences (or other preferences, e.g. Time Machine) that need fixing, we would also need a test run with a new Aperture Library in the regular user account.


Don't you think so?


Yes, I fully agree. My original instruction had not included opening into a new user account and I missed the fact that Joseph had done that concurrently.


A new user account is a good troubleshooting step but not concurrent.


-Allen

Aperture. Time to quit.

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