4 Replies Latest reply: May 3, 2013 10:36 AM by ipanacea
ipanacea Level 1 Level 1 (0 points)

Anyone else have this issue? I always switch back to the local library before quitting Aperture, but when the screen saver launches, it sits at a black screen for an extended period of time with the message "Looking for photos…" on it. I use a specified project from my iPhoto library as my screen saver for the Vintage Pics saver so I'm curious how I can make it stop looking for the Aperture library on that external device in another location entirely.


MacBook Pro, Mac OS X (10.6.8), 15" Core i7
  • 1. Re: Screen saver hangs looking for offline Aperture library.
    Frank Caggiano Level 7 Level 7 (23,830 points)

    You switch back to the local library in Aperture?  How long does it wait and what happens after the wait perirod is over?

     

    And are you really on 10.6.8 as your profile says?

  • 2. Re: Screen saver hangs looking for offline Aperture library.
    ipanacea Level 1 Level 1 (0 points)

    Yes, before I quit Aperture I switch it back to the local library to try and eliminate a variable, but it doesnt' seem to make any difference.

     

    The screen saver is set to come on after 10 minutes of inactivity, and the display goes to sleep after 25 minutes of inactivity. When it comes on it shows the message and it never goes away because by the time 25 minutes comes around the display is sleeping anyways.

     

    When I wake it up there's a Finder window saying it can't find the location of the files in the offline library (well no kidding) and an OK button to click it away.

     

    So unless I can get the Screen Saver pref to stop looking for these offline photos I might as well switch to one of the lame built in ones.

  • 3. Re: Screen saver hangs looking for offline Aperture library.
    Frank Caggiano Level 7 Level 7 (23,830 points)

    Ok if I understand correctly the screensaver you are using is actually using the iPhoto library. This looking for the Aperture library seems to be an artifact of just having Aperture on the system.

     

    So try this start Aperture on the local library and actually select an Aperture image or project that is in the local library as your screen saver and see if that runs OK with the external library offline. If it does then try switching to the iPhoto library.

     

    I'm thinking that at some point the screen saver did get an image from the external library and is stuck looking for it. If you force it it take an image from the local library it might clear it up.

     

    If this doesn;t work you can try the screen saver preference file. I'm not sure where that is (an if there is just one) so try what I wrote above and I'll see if I can track down the files.

     

    BTW you never answered my question concerning your system if it is really 10.6.8 there might be a problem. I'm on ML and the files setup might have changed.

  • 4. Re: Screen saver hangs looking for offline Aperture library.
    ipanacea Level 1 Level 1 (0 points)

    Ok Frank, thanks for your responses, another mind on the matter is always helpful.

     

    Here's what I did, but as I'm pretty busy today I won't have time to test it until I get home for cocktail hour. The Aperture library was just a reference of the original files that were on the external drive. When I originally created the library I thought that was the best method and it created a library that was only a couple gigs in size instead of copying all the files into it and having one that was 60+ gigs.

     

    I moved that library off my local machine and put it on the server that's holding all the photos. Now when I go into the Screen Saver pref pane, it loads up the options almost instantly as it should so I'm betting when the screen saver kicks in it will do the same.

     

    I thought the idea behind a reference library, or one that leaves all the original photos in place, was just that and that it wouldn't be necessary to have the connection to the originals unless I wanted to edit or use them. Seems kinda lame to me that that isn't the case.

     

    And thanks for the heads up on the profile change, I hadn't noticed that, but have made the corrections. (: