Skip to main content
_
_Greg_Hinch_
Participant
January 3, 2009
Question

Writing EXIF data like XMP

  • January 3, 2009
  • 2 replies
  • 1229 views
I'm trying to write a little script to upload my photos from Bridge to Flickr. I shoot in DNG, and Flickr won't accept RAW files, so I'm converting the files to JPEG using the BitmapData to export a new file. I want to try and preserve all the EXIF data from the file because Flickr can read this and display it, and if I take one of the photos into Photoshop and save it out as a JPEG it does preserve the data.

The only method I can find to try and do this in scripting seems to be to serialize the Metadata object from the Thumbnail that I am reading from, make a new XMPFile out of the newly exported JPEG and open it for update, and then run putXMP with the serialized Metadata. This succeeds in writing the XMP data, but does not appear to properly preserve the EXIF data. Neither Flickr nor Mac OS X Get Info can detect any data about the new file other than the date.

Any help in this is appreciated,
Thanks,
Greg
This topic has been closed for replies.

2 replies

0
01af
Known Participant
February 21, 2009
You may also download Phil Harvey's ExifTool and then call that from your Bridge script using the app.system() function. Building an argument file via Javascript and then passing that to ExifTool is a very powerful way to deal with metadata tasks and issues.

For me, that's working great to circumvent a whole lot of Bridge bugs and shortcomings.

-- Olaf
_
_xbytor_
Known Participant
February 22, 2009
> You may also download Phil Harvey's ExifTool and then call that from your Bridge script using the app.system() function. Building an argument file via Javascript and then passing that to ExifTool is a very powerful way to deal with metadata tasks and issues.
>

exiftool -tagsFromFile image001.nef image001.jpg
_
_David_E__Franzen_
Participating Frequently
January 5, 2009
Hi Greg,

Traditionally XMPFiles (and Camera Raw) treat most of the native EXIF as read-only data. Exceptions, like the dates, are properties stored in EXIF which you can also actually modify using a user-interface in an Adobe product. So, putXMP will only put most of the EXIF properties into the XMP packet stored in the file and not also into the EXIF or TIFF IFDs in the file. In other words--you can't get there from here with CS4. Flickr apparently only reads EXIF properties from the native EXIF and not from XMP.

Right now your best bet is a) live without the EXIF showing up in Flickr or b) have your script automate opening the original files in Photoshop and saving them as JPEGs there instead of using the faster BitmapData approcah.

-David
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices