Previous 1 2 Next 16 Replies Latest reply: Aug 30, 2013 7:02 AM by anandmak
Gary i Level 5 Level 5 (6,190 points)

Hello every one, this will be my last ditch attempt with aperture before binning it.

 

Its been very unstable for me for sometime now many months on both an imac and macbook, updates from apple seem to be making matters worse.

 

To cap it all photostream seems to kill it entirely. Most of the time it seems to either be processing images or doing something with photostream. Whilst this is happening aperture is either dog slow or totally unresponsive and infact half the time my entire mac seems like its about to melt down.

 

Aperture as a programme seems to be falling over pretty rapidly for me, I don't know if anyone else feels that way. In an attempt to mitigate the issues I expereince all the time I have given up using raw, because these knock it over, on an imac quad core i7 with 8 gig of ram. Lion certainly has not helped and with photostream compounding it, I am finding productivity with aperture sliding.

 

IS anyone else having issues with this 'professional' software now?

 

Yes I have rebuilt the database and library many many times, fixed permissions, done all those things that make no difference what so ever. I repprossed all masters and thumbs before going to be one night and this helped for a while.

 

Aperture on my macbook is game over really, its just too slow and unresponsive to be considered viable.


i7 27 imac, 2ghz macbook, Mac OS X (10.6.5)
  • Shuttleworth125 Level 2 Level 2 (415 points)

    We run Aperture on Lion on an i7 iMac, (though with 16GB RAM, SSD + 2TB HDD and 2GB graphics card)  and don't suffer anything like you are describing (TBH we dont see it on our old 2.8GHz Core 2 duo either). We have photostream set so that it doesn't add all images added to the library. Occasionally Aperture will "hang" (usually during a big Time Machine backup) but it never runs slow. I'm not an expert but I don't think our upgrades over yours are preventing us from seeing problems.

     

    Our 1TB+ library is mostly referenced images, only the most recent jobs are managed and all photo's are RAW.

     

    We run a little app from the app store called MemoryFreer that monitors memory usage in the menu bar and can free up available memory when available memory gets low. Even with 16Gb we can sometimes get theu usage quite high when using Aperture and Photoshop together.

     

    I know none of this helps solve your problems, but it may indicate it's not hardware related.

  • léonie Level 9 Level 9 (65,385 points)

    Gary,

    I don't see any of these problems either, not on my MBPs (Lion (8 GB RAM) and SL (4GB RAM)), nor on my iMac.

     

    the only time I had trouble with Aperture was, when the free disk space was getting low - after I freed enough diskspace (20% of the disk empty) all was running smoothly again. So how much free disk space do you have? With less than 20% free the performance will decrease notacibly.

     

    The second problem with the Photo Stream: I also have disabled autoimport, and that helps a lot, if my network connection is shaky.

     

    Also it helps to keep the size of projects small - Aperture is slower when working with projects with several hundred images then with smaller projects. I try to keep the size of projects well below 200 images.

     

    If none of this applies to your case, you may consider to keep the Activity window visible while working with Aperture, to see what the application is actually doing when things slow down. Maybe there are still maintainance jobs to be done -building previews, raw conversion, faces scan. And check the console window if you see diagnostic messages related to Aperture.

     

    Regards

    Léonie

  • Gary i Level 5 Level 5 (6,190 points)

    The problem is it appears to be processing all of the time. It never ends. If you leave it all night every thing seems fine, then you click in a different project and poof off we go again, processing images.

     

    Its just not a very sharp product, its doggy and slow. Would referenceing be a mistake or might this eleviate some of the issues.

     

    Yes I have a reasonably large library. probably not as big as many peoples but it sits around 110 gig on the imac and around 15 gig on the macbook.

     

    If I was to reference is there a sensible way to get this files out of aperture?

  • bobwild Level 4 Level 4 (1,575 points)

    have determined what Aperture is doing, when you start it?

    Go to menu>Window>Show Activity

    That should show what Aperture is doing.

     

    I am running Aperture 3.2.2 on  older iMac 24" 3.06GHz core 2 duo with 6GB of RAM. Also running Lion. I have about 12,000 raw picture files, using referneced files. No prroblems running Aperture.

  • léonie Level 9 Level 9 (65,385 points)

    Would referenceing be a mistake or might this eleviate some of the issues.

    That depends; referencing will help, if you do not have enough free space on your system drive and you can free your disk this way. But you should connect your external drive to a fast port - fire wire, thunderbolt ...

    If you on the other hand allready have all the disk space you need, this might may things worse, if your external disk is slow.

     

    You really need to find out, what Aperture is doing; that is why I suggested to show the Activity window and watch the Console Window (Utilities -> Console). The performance you see is very untypical for a moderate sized Library.

     

    I suspect your Aperture LIbrary may be corrupted in some way or your Preferences are faulty.

    How to solve such problems is described in this support article.

     

    Aperture 3: Troubleshooting Basics

     

     

    Try to repair the permissions in your Library, and if that dos not help, repair the library as described in the article.

     

    Post back, if that does not solve the problem.

     

    Regards

    Léonie

     

    P.S. I would not change the type of the library to referenced, while there may be a problem with the library that need repairing.

  • Gary i Level 5 Level 5 (6,190 points)

    I believe I had said what its doing, processing images. Its all it ever seems to do.

     

    Its not doing it all the time. For instance right now its stopped But if I make a change to an image, obvioudly it updates photostream. And it literally does this the second you let go of the mouse, so if you are making a bright ness change and let go of the mouse, photostream gets updated. Then you make a slight other change and off it goes again, its utterly stupid for it to be doing that.

     

    BUt my main gripe is with the general clunkiness of it. It got signficantly worse with Lion, on the imac its usable just on the macbook, its a no go area.

     

    So I am going to try referencing on the iMac at least. Please is there a simple way of exporting images, or is it going to be a case of exporting from each prject one at a time?

  • léonie Level 9 Level 9 (65,385 points)

    To relocate masters to a different drive you select them all at once in the browser, then select from the Aperture menu

         File -> Relocate Masters

     

    In the Library Inspector you can select more than one project at once by holding down the shift key, while you select the projects.

     

    You can even select all your images at once by going to the "Photos" View, but frankly, I would not relocate all at once. First check with one project, if all goes well, then you can go for larger transfers.

  • Shuttleworth125 Level 2 Level 2 (415 points)

    You can even select all your images at once by going to the "Photos" View, but frankly, I would not relocate all at once. First check with one project, if all goes well, then you can go for larger transfers.

    If you are importing photo's regularly it might be better, to start a brand new library for all new images and import them as referenced. If it's an old library you are using then fragmentation may be an issue, it certainly wouldn't hurt to try a fresh library that won't be fragmented.

    I'd also make a note of your preference settings and delete Aperture Preferences as described in the troubleshooting document before creating the new library, and try it with photostream left off for the new library.

  • Gary i Level 5 Level 5 (6,190 points)

    Well I references the lot and certainly within the application it feels snappier.

     

    But again, a bunch of random processing has began. I opened the app today and its been sat int he back ground for over an hour with nothing in activity.

     

    Then I outputted a single JPG from my work project.

     

    Then it starts processing 1500 images from a folder from 2008!

     

    Why does it do this. If I could just understand what its doing and why then I could stop getting so angry at it. On my imac this random processing is OK as its a pretty meaty processor. but on my macbook the thing grinds to a halt as random images, already processed a 1000 times get processed again!

  • léonie Level 9 Level 9 (65,385 points)

    That behaviour is not normal at all.

    What I do not understand: Are you using the same, identical Aperture Library on your imac and your MB? Or do you get the same sluggish behaviour with different libraries?

     

    If you are using the same library on both machines - how are you sharing it? A Shared folder, anetwork volume, or do you mount the drive with the library alternatele on both machines?

  • Gary i Level 5 Level 5 (6,190 points)

    Hi.

     

    No I am not sharing a library both are seperate, apart from what ever happens with photostream.

     

    I would agree this does not appear to be normal behaviour, thing is how do I stop it?

     

    Today I tried to open aperture without a network connection and yet again it went into melt down. Spinning beach ball 'Aperture not responding'

     

    The only way to get it back was a full rebuild of the database, of course followed by ALL the images reprossesing. Honestly there is only like 15gig of photos on the macbook. And I am at the end of my tether. As a forty quid app this thing will probably do. Sadly I am one of the muppets that paid £280 when it came out and two consequent £70 updates.

     

    I realy like the idea of photostream though, but I have not researched if anyone else is doing anything similar.

  • Shuttleworth125 Level 2 Level 2 (415 points)

    Gary i wrote:

     

     

    No I am not sharing a library both are seperate, apart from what ever happens with photostream.

     

     

    From the description in the manual:

     

     

    Photo uploaded from Aperture on one Mac and pushed to Aperture on another Mac: If the Aperture library the photo is pushed to contains a duplicate of the project or album in which the photo originated, the photo is placed in that project or album—even if the project and any subordinate folders and albums have been renamed or restructured. If the project or its albums don’t exist in the Aperture library the photo is pushed to, the project hierarchy is replicated and the photo is placed in its original position.

     

     

    Have you tried turning off photostream since referencng your library?

  • Gary i Level 5 Level 5 (6,190 points)

    I have, but I really like photostream.

     

    Are we saying in order to have a stable Aperture one cannot use photostream?

     

    Do other service exist has google got anything?

  • léonie Level 9 Level 9 (65,385 points)

    Gary,

    The only way to get it back was a full rebuild of the database, of course followed by ALL the images reprossesing. Honestly there is only like 15gig of photos on the macbook. And I am at the end of my tether. As a forty quid app this thing will

    That looks to me, like you may have a corrupted image or a corrupted xml-file in your Aperture Library, that cannot be repaired by "rebuild library"; in that case Aperture will try to fix it each time, when it launches.

     

    You might try to manually repair your Aperture Library - I did not suggest this previously, for it seems to be extremely unlikely, that you have the same corruption in your both your library on both your machines, unless you copied a corrupted library.

     

    To manually fix the Aperture Library try this:

    Manually repairing the Aperture Library: Re: Aperture 3 rebuild library - SQLITE MISUSE

     

     

    Regards

    Léonie

Previous 1 2 Next