7131 Views 14 Replies Latest reply: Sep 12, 2010 7:48 PM by mlondon
I have a similar problem. When I upgraded to Aperture 3.03, all the Referenced Files from iPhoto were no longer connected. Although it is easy to re-connect Referenced Files, I can not figure out how to do it with iPhoto due to its complicated directory structure. The only way I have figured out as a workaround is to take individual folders within iPhoto, copy them to the desktop, and then re-connect from there.
Did you find a solution?
When I go File>locate referenced files, Macintosh HD is offline (which i'm guessing is my old HD). Thing is, under the Not Found column, it says 0..... Can someone please help me with this??
Were you simultaneously using iPhoto and Aperture to work on the same master images? (Ouch.) Do you want them permanently living in your iPhoto library? If not, you could try Exporting all of them from iPhoto to a single visible folder somewhere (make sure you use iPhoto's File Export with Original and Filename selected), run Aperture's Locate Referenced Files command and point it at the new directory, cross your fingers and see if it can hook them up.
Alternatively if there's any way that you can install your old drive in an external enclosure and mount it, then Aperture may be able to find them again if you give it the option of Locating Referenced Files. Then you could relocate them to your new drive, although you'd now have a 2nd copy of each one, not in your iPhoto library.
I just ran into the very same issue even if my main HD still have the same volume name.
Googling I found this http://blogs.oreilly.com/aperture/2008/01/a-few-troubleshooting-updates.html and I am currently trying the trick (Aperture says 56% ended).
Hope it can help
I found I have this issue as well. The problem lies in that i cannot reconnect my images in iPhoto because when I navigate in the bottom pane to my iPhoto library, it brings up my album list with nothing in them.
The problem lies in that Aperture relies on using the HD UUID to identify the volume for referenced images. The UUID is generated when you create a new volume. Thus, installing a new HD gets a new UUID, regardless of volume name, so your aperture reads your HD as being offline. You can fix thus by getting your current Mac HD UUID, going into the Aperture Library package, editing the library.apdb file and replacing the old UUID with your new one.
For the record, I would've tried that solution before messing with my Aperture database, but I could NOT navigate to photos in my iPhoto library in the bottom window. When I clicked on iPhoto Library, it just gives links to my albums with nothing in them (could be an issue with my iPhoto Library).
Its not an issue with your iPhoto Library. I have spoken with Apple Technical Support about this issue with Aperture, and they acknowledge that this is a bug. In previous versions, it was possible to navigate to the correct photo within the iPhoto Library and reconnect the images.
What I did as a workaround is to copy the specific folders needed from the iPhoto Library using Finder to the desktop, and then reconnect the images and then consolidate the masters.
I am relatively new to Mac so forgive me if this is a silly question. Exactly how do you edit the library and alter the disk UUID. Locating the library is not an issue but the library.apdb appears to be a binary file and as such editing this becomes an issue as does an entry for UUID.
Many thanks in advance as this will save me a lot of time as I just had my 7200 RPM disk replaced with a 5400 rpm due to vibration and heat problems.
The aperture library data base, library.apdb is actually a SQlite database, so you need an SQlite editor. I got the info from:
Look at one of the later replies.
Effectively I used the trick based on files outside iPhoto. Maybe if you want to reconnect images you could try to launch the database update using a picture outside a iPhotoLibrary (hopefully you have one ?).
I recon that iPhoto integration with Aperture is not that good. When I made the switch I could not transfer my MobileMe galleries and the books I made. I still need to hold all my iPhoto libraries on the hard drive meaning loosing twice the place...
So I just had the same problem. I had restored my whole disk drive from a backup after Apple replaced the hard drive.
All images that were referenced on the internal drive were listed as offline even after a Aperture DB rebuild and a disk drive identically named to the original.
Procedure: first test this on a few files, then you can do the whole library.
Select any project with multiple pictures that are referenced and have a red tag indicating offline. Do a select all on the images in that project, even if some do not have offline indicated. After the selection use File -> Locate Referenced Files.
Uncheck the box that says "Show Only Referenced Files" Select one of the files that you know has a status of offline. Next, in the bottom window, navigate to that exact file and select it. Click the Reconnect All button, it may take a few minutes, but when it is done the number of offline files will have decreased and the new number of online files will be reflected.
The Reconnect All feature is smart enough to figure out the folder hierarchy for your whole library. I subsequently used the HUD to select all 14,300 "offline" images in the library, I then selected one and told it to Reconnect All as above. Took about 15 minutes but at least there was a progress bar.
It looks like the solution to my problem of altering the diskUUID was temporary. I was having issues with my library and so rebuilt it. Afterwards, the iPhoto referenced files once again reared it's head, somehow reverting the UUID to my old drive, thus unlinking all my referenced images. Sure, I could go back and put my current UUID in the Library.apdb, but it's obvious that the UUID is recorded somewhere else, and that gets used during a rebuild.
I'm going to try and reference an external file on my current hard drive and see if I can relink all my photos, thus having it reconnect the rest. Fingers crossed.
I recently had to rebuild a failing RAID which holds my Libraries and Referenced Masters, and ran into this same issue. While waiting for Aperture to reconnect 100,000+ files, I looked around and found this thread.
I know understand the UUID issue. But if I had to rebuild the RAID again, I would simply consolidate everything into the Library first (assuming the RAID was still running) and then rebuild. That way, when I copy the data back onto the new volume (same name, but different UUID) all the files will be safely inside the library and won't need to be reconnected.
This whole experience is making me reconsider using referenced masters to begin with. It was more of an issue when my drives were smaller, but know that I'm on a massive RAID, it is not an issue for my home MacPro. When I'm on the road, referenced has it advantages.