omancini

Q: Aperture 3.4.4 Library Problem

After Aperture was updated to 3.4.4 I could not start the program again, when I initiate the program it tries to open the Aperture Library but it may stay in that condition even for hours without any result, at the end I close the application (the Aperture Bar is there, and you can also access the preferences) and it closes normally although it never finish opening, it permanently shows the next message:

 

Screen Shot 2013-04-28 at 10.14.12 PM.png

 

These are the steps I tried before deciding start this discussion:

 

1. Used the Aperture Library I have in a backup hard drive that is cloning my primary HD regularly but no improvement.

2. Sent the Aperture app to the trash can and installed version 3 from scratch, after that installation I had to update to 3.4.4 because Aperture identified that the library was from a new version. After the new update the program succeded to open. When I closed and tried to open again I got nothing again.

3. In order to verify that the library is not corrupted I used the "Show Package Content" and can browse the information inside the library without any problem.

4. Changed the name of my Aperture Library and started Aperture but  although I see that a new Library file is created but the original problem remains, Aperture never opens.

 

The original Aperture Library is a 70.24 GB file that contains adjustments for all the thousands of photos I used to manage with this application, not been able to open the program is causing a lot of frustration, specially because I keep taking pictures and saving them in the Hard Drive but I am not able to produce them or export them anymore.

 

I am not sure if somebody else experienced this problem but if not is important that Apples know that this is a very annoying problem that must be fixed ASAP.

 

Thanks

Mac Pro, Mac OS X (10.7.5), 2 x 28 GHz Quad-Core Intel Xeon

Posted on Apr 28, 2013 7:44 PM

Close

Q: Aperture 3.4.4 Library Problem

  • All replies
  • Helpful answers

first Previous Page 3 of 3
  • by omancini,

    omancini omancini Jun 8, 2013 9:58 AM in response to omancini
    Level 1 (4 points)
    iPhone
    Jun 8, 2013 9:58 AM in response to omancini

    Update. After installing the 3.4.5 Aperture update the application started to work as expected. I tried different scenarios since the released date and the only inconsistency found is the time it takes to start, otherwise I was able to work with my pictures.

     

    Will test for another couples of days, if the issue does not appear again will consider to close this discussion.

     

    Thanks

  • by omancini,

    omancini omancini Jun 13, 2013 6:39 PM in response to omancini
    Level 1 (4 points)
    iPhone
    Jun 13, 2013 6:39 PM in response to omancini

    After opening and working with Aperture 3.4.5 everyday since the last update was released i noticed that the opening time was slightly increasing each time I open the app after a restart or wake but was quite fast if I opened the program some minutes after I closed it.

     

    Finally today Aperture did not start as it did before the update. Tried several times and as it happened before, some minutes after I launched the program, I could close it while the message öpening Aperture Library" was still running as it shows in the picture.Screen Shot 2013-06-13 at 9.35.06 PM.png

  • by léonie,

    léonie léonie Jun 13, 2013 11:16 PM in response to omancini
    Level 10 (108,869 points)
    iCloud
    Jun 13, 2013 11:16 PM in response to omancini

    i noticed that the opening time was slightly increasing each time I open the app after a restart or wake but was quite fast if I opened the program some minutes after I closed it.

    That a program will be "quite fast if I opened the program some minutes after I closed it" is normal for the process modell used  by Lion and Mt. Lion (automatic termination): If you quit an application, the OS might decide just to close the application window, but keep the app cached with all data, in its current state, ready to be launched again immediately. Only log-off ad on again (or restart) will ensure that the application really will quit.

first Previous Page 3 of 3