Main menu

SmartFeed by FeedBurner Subscribe to the site feed.


If you find the information here useful, then please consider a small donation, or linking to this site.

Recent Comments

Recent Tweets

  • RT @robmargel: http://tinyurl.com/y8tcrhr - Parental Controls in Windows 7 and Windows Vista ^MW practical advice for parents
  • Just caught up for a coffee with an old friend at Microsoft UK (we were grads together 15 years ago... now I feel /really/ old)
  • Grrr... I paid £5 to respond to an ad on preloved.co.uk and the advertiser didn't even respond. There's a site to avoid in future...
  • [blog] Safer Internet Day: Educating parents on Internet safety for their children http://bit.ly/c0s8Jt
  • European Safer Internet Day: ChildLine's advice on staying safe online - parents might want their kids to read this: http://bit.ly/92HY9C

Calendar

August 2008
M T W T F S S
« Jul   Sep »
 123
45678910
11121314151617
18192021222324
25262728293031

Archive

When “non-destructive” edits start making changes to the original files…

Written by: Mark Wilson

A few days back, I was extolling the virtues of the Sidecar (.XMP) file format that Adobe uses for storing updated metadata and edits to digital images in Adobe Camera Raw (ACR):

“It turns out that Bridge (together with ACR) is exactly what I needed to organise my images, open them in ACR (and optionally Photoshop) to perform non-destructive edits, with the changes (and associated metadata) stored in Sidecar (.XMP) files alongside the original image (avoiding the need to maintain multiple copies of images.”

Well, soon afterwards I found out that, for raw image files, ACR does indeed create XMP files (which are also used by Adobe Photoshop Lightroom and are visible in Bridge) but, if ACR is used for JPEGs (or TIFFs), then the original files are modified.

In a blog post from February 2007, Adobe’s John Nack explains why non-destructive edits to JPEGs may be considered an oxymoron – basically Adobe appends the metadata that would normally be stored in the .XMP file to the JPEG. That means that, if I view an edited file using an Adobe product, it can see the changes but other viewers are unaware of the additional data and ignore it.

The accompanying images show a JPEG file that I opened in ACR (via Bridge) to adjust the exposure and to straighten the image. Bridge shows the updated file as being 2848×1894 pixels in size and the image edits are visible in the preview:

JPEG file edited with Adobe Camera Raw 4.0 and viewed in Bridge CS3

Meanwhile, the Mac OS X Finder (or any other image viewer) sees the original 3008×2000 pixel image, still underexposed and leaning to one side:

JPEG file edited with Adobe Camera Raw 4.0 and viewed in the Mac OS X Finder

If, like me, you like your digital asset management software to maintain the original images untouched and only perform non-destructive edits, then this may come as a bit of a shock.

Write a comment

Please note the rules for comments and the privacy policy and data protection notice. I'm sorry but, because not everyone sticks to the rules, I've had to implement some spam prevention measures - if you're experiencing difficulties leaving a comment, please let me know.





The following XHTML tags may be used: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>