
Apple Aperture (Photo credit: Wikipedia)
Its silly because this issue gave me stress. I switched on referenced image badges the other day because I was quite surprised when I tried to archive my library to a file vault that it told me 133 images could not be archived because it couldn’t find my masters. A bit of googling lead me to believe that this was because the somehow I had imported referenced images rather than managed ones – this was not true! I found the library that had the not found badge icons on (from Disney on Ice) and following instructions I tried to “Locate Referenced Files”. It told me there were no referenced files.
Some people probably wouldn’t be as annoyed as I would – I mean the thumb images that are generated from my raw files are of high enough quality for most people but I don’t like this. and I needed to get rid of the little icon with the warning sign. Not every image in the project was missing – so I located the directory with the issue by going into terminal and finding it in Unix. I kept Aperture closed throughout the next steps.
I did a cd to my drive – I kind of cheat here:
cd /Volumes
cd Back*
find . -name \*_4915.CR2\*
The first Cd takes you to the place MacOS mounts your volumes – my backup volumes are in an externally mounted drive named Backup Drive – (the Back* thing is laziness). it then iterated though my photo libraries and found the real path from the master files. with aperture if you right-click on the aperture library and select Open Stack you can see its internal structure – within the Masters directory is where the files are kept, the exact path I found with the find statement above.
At this point i discovered files were missing! I had hoped it would just be a permissions issue. I have no idea how. I used to own a time machine before it blew up so i mounted the old drive from that and used pretty much the same commands as above to locate the missing files within the old time machine archive. I restored the files from the backup by just copying them into the aperture directory and the problem was solved.
I really do not like that this happened. this was one of the few libraries that I had published to mobile me before and I cant help but wonder if it had something to do with the way mobile me was recently decommissioned, but I don’t know anything for sure. I will be keeping an eye out for more strange things!
Like this:
Like Loading...