This discussion is archived
2064 Views 13 Replies Latest reply: Aug 28, 2007 6:49 AM by Pim Versteeg
Currently Being ModeratedMay 29, 2007 3:38 PM (in response to Brian O\'Reilly)The script works great, bring all the exif data from a Canon 350D plus 16-35, 24-70 and 70-200 lens.
The only problem is that is unable to get the location with referenced files so only works with managed images.iMac 20" 2.1 Ghz 1.5Gb RAM - Mac OS 10.4.8
Currently Being ModeratedMay 30, 2007 1:40 AM (in response to Brian O\'Reilly)Eduardo
Perhaps add this comment to the original dpreview thread...
Perhaps someone will be able to assist
I only use managed files and am hopeless with AppleScripts
PS - glad to see someone (other than myself) finds this a great addition to Apertures capability
Currently Being ModeratedMay 30, 2007 5:01 AM (in response to Brian O\'Reilly)I actually did, but not reply so far.
Thanks for the info Brian.iMac 20" 2.1 Ghz 1.5Gb RAM - Mac OS 10.4.8
Currently Being ModeratedMay 30, 2007 2:12 PM (in response to Brian O\'Reilly)I'd love to use this. But when I try it it quits with an error, and following the Applescript log I'm not quite able to parse out where the error comes from. Does anyone have an email address for the author?20" iMac 2GHz 2GB, Mac Book Pro 2.66GHz 2GB, Mac OS X (10.4.9)
Currently Being ModeratedMay 31, 2007 1:15 AM (in response to Charles Hartman)Charles
Have you altered the AppleScript as per the info on dpreview?
You will need to set the path to your Aperture library.
You should be able to get back to both of the AppleScript authors via the info in the dpreview article and possibly a Google search or two
Hope this helps
Currently Being ModeratedJun 1, 2007 3:31 PM (in response to Brian O\'Reilly)Yes, I did. I tried it both ways (library hard-coded, find the library). It doesn't work, and I've started a correspondence with Brett Gross who wrote the core find-the-image-file code, which is where the problem seems to originate.
As far as I can tell, the problem is that if you have selected an image which has a version name different from the filename, the script looks for the file under the version name (and of course doesn't find it). This is an Applescript problem, and Aperture's dictionary--as I read it--may or may not provide a solution. I don't know enough Appescript to get far with it myself.20" iMac 2GHz 2GB, Mac Book Pro 2.66GHz 2GB, Mac OS X (10.4.9)
Currently Being ModeratedJun 2, 2007 12:53 AM (in response to Charles Hartman)Hi,
I'm the "author", if you can call it that, since most of the script is, as someone earlier mentioned, Brett Gross' work. I was the one that glued exiftool to it and got it working with my Aperture setup. I am looking at the various problems that have popped up on dpreview and with personal correspondence and trying to find solutions.
But it isn't easy. As Charles said, the Aperture dictionary isn't helpful in that regard. And with the flexibility that Aperture provides in naming is the curse here. And all the variables with versions, external edits, etc. It gets very complicated. But if you look at the thread on dpreview, someone has possibly found a way to query the SQL database to make it all work smoothly.
It is very easy to do this stuff at import. I am just putting the finishing touches on an Automator action to import the files and add the EXIF data (it will even query GeoNames and add the city, state & country IPTC data if there is GPS data present in the file).PowerMac G5 2.3GHz, Mac OS X (10.4.9)
Currently Being ModeratedJun 2, 2007 8:05 AM (in response to Allan Hise)Alan
Many thanks for your efforts - quite an eyeopener as to what can be done
Look forward to the Automator action
Currently Being ModeratedJun 4, 2007 2:52 PM (in response to Brian O\'Reilly)I finally have my solution ready that will add all of the custom metadata (and more!) to Aperture at import, which should take care of most of the problems with the script that runs on already imported images.
If GPS EXIF data is present, it will also query the GeoNames database and fill in the IPTC City / State / Country fields.
Check it out here:
PowerMac G5 2.3GHz Mac OS X (10.4.9)
Currently Being ModeratedJun 8, 2007 7:54 AM (in response to Allan Hise)Allan,
Brett Gross has managed to track down and solve a problem in his find-the-file code, so it now works with images that were renamed on import. If you don't have his e-mail address, write to me (firstname.lastname@example.org) and I'll send it to you. It would be great if you could incorporate it into your script to add extra EXIF data after import.
Charles20" iMac 2GHz 2GB, Mac Book Pro 2.66GHz 2GB, Mac OS X (10.4.9)
Currently Being ModeratedJun 11, 2007 10:01 AM (in response to Charles Hartman)Hi Charles,
I tried emailing you but haven't heard back. Maybe I got stuck in a spam filter.
I am ready to add a couple more bug fixes into the script, so I would like to incorporate yours as well.
Please contact me at allan at hise dot org
AllanPowerMac G5 2.3GHz, Mac OS X (10.4.9), 5 GB RAM, ATI Radeon X800 XT
Currently Being ModeratedJul 16, 2007 1:36 PM (in response to Allan Hise)a little curious about this ...
does it work with images already in the library yet, or is it only on import ???
i would love to run it on my entire library and have it add all that meta in for me !!!PM G5 Dual 2.0 4GB RAM - X800XT w/30" and 23" Cinema Displays, Mac OS X (10.4.9), PB G4 12" 1.5 1.25GB RAM - MBP C2D 17" 2.33 2GB RAM
Currently Being ModeratedAug 28, 2007 6:49 AM (in response to tidysteve)it works for pics in the library as well, like a dream
another question, I am not a comaand line wizzard, and although I managed to install exif tool, there is no way I can get geo:geonames installed.
is there a kind soul out there who could spell this out for me?
many thanksPB, iMac, G5, MacBookPro, Mac Pro, Mac OS X (10.4.8), 2*23" Cinema's