The Online Photographer

Check out our new site at!

Saturday, February 24, 2007

There's DNG—And Then There's DNG

by Carl Weese

After traveling all last week I've been playing catch-up and it took me until Wednesday to realize that Adobe posted the latest update to Adobe Camera RAW, version 3.7, on Sunday. ACR is the part of PhotoShop that interprets RAW digital capture files. ACR's controls for color and tone are so good that I seldom need to do anything to a digital capture file in Photoshop itself other than specific sharpening for intended use.

This update is important because the new version supports the Pentax K10D camera I bought a couple months ago (Nikon's new D40 is also supported). I've been using ACR version 3.6 right from the start for my K10D files, because Pentax offers the option of saving files in the "universal" DNG format instead of their proprietary PEF format. The reason I put universal in quotes is because even though ACR could open and work with the Pentax DNG files it was obvious that the protocols involved were not fully supported. The worst anomaly was in the vital White Balance function.

In ACR, White Balance is adjusted with two sliders. The first, Temperature, reads in degrees Kelvin, so a file captured in ordinary daylight should have a Temperature near 5000. Moving the slider to the right to a higher temperature makes the color warmer, moving to the left for a lower temperature makes it cooler. The second slider, labeled Tint, controls the magenta/green color axis and in normal light should read near zero. Moving to the right, into positive numbers, shifts the color to magenta, left to negative numbers shifts the color to green. (For example, a strong shift of +40 or so will correct for the green cast of fluorescent light.) But when ACR 3.6 read a K10D file, normal daylight files showed WB readings about 1800 degrees too high in Temperature and 60-70 points too high in Tint. These files looked perfectly OK on screen as long as the shooting white balance was correct, and they could be tweaked for color balance either visually or by sampling within the picture with the eyedropper, but the numerical readout was totally out of whack. It was still possible to process files out to printable .psd files and web-postable JPEG files, but the weird WB numbers were disconcerting and made me wonder what else about ACR's interpretation of the files might also be sub-optimal.

So I wasted no time downloading and installing ACR v. 3.7 yesterday. As soon as I turned Bridge loose on a big folder of captures it set to work making a new cache. Bridge is the browser element of Photoshop CS2, and it uses ACR to create thumbnails and previews of RAW files. When it finished the cache for a folder with about 900 captures I made last week on my trip, I highlighted a few files and hit which brings the files directly from Bridge into ACR in slideshow mode. The files looked normal, and daylight shots that had showed WB numbers in 3.6 like 6700/65 now showed proper numbers like 4900/-4. Whatever it was that ACR couldn't understand about the K10D white balance settings in the previous version is clearly fixed. As expected, files whose white balance had been left as shot simply changed their numbers and needed no further attention. Files that I had previously tweaked for white balance however all turned bright orange-red, just as you'd expect of a file with WB numbers like 6700/65. As it happens this isn't too hard to fix. Highlight any group of these files and bring them into ACR. Hit the Select All button, then the Synchronize button, adjust the white balance to where it belongs and the whole set is corrected in unison.

What about other aspects of ACR's processing of the K10D files? I had an immediate sense that the files looked just slightly better in a subtle way. But since 3.7 had replaced 3.6 on my computer there was no way to bring up the two versions side by side on screen. So I tried a little experiment. Since Monday I've been posting pictures from my California trip on my web log. To prepare the files for these posts I had tweaked each picture in ACR, then run them through a Batch Action that opened each file, resized it, mode-changed from 16 to 8 bit, changed color profile to sRGB and then saved a JPEG to my "for the blog" folder. I made a new folder, then selected a handful of these same RAW files and invoked the Batch Action directly from Bridge without touching the files in ACR. This meant that they were processed out of version 3.7 and so, after renaming the files, I could bring them up side by side on screen with identical files processed out by 3.6. There are indeed differences. It's very subtle, but I'm convinced the tonal transitions are smoother and separations in the deep values a bit more distinct. Running the curser over the pairs of files gives slightly different rgb numbers in the Info palette. If I find more differences, I'll report on them.

Meanwhile, apropos of nothing at all, while out in Berkeley on business I had a chance to meet with the author and teacher Huston Smith. I studied with him on a scholarship almost forty years ago, and while we've corresponded, this was our first real reunion. The reason I bring this up is simply because, sometimes you just want to take a snapshot:

Carl Weese, Huston Smith

To end up back on topic, this was made with the K10D and 21mm DA "pancake" lens.

Posted by: CARL WEESE


Blogger FN said...

See, if I'd known you'd be out in the Bay Area, I would have tried to finagle the chance to play with a K10d!

Seriously, I do wish my K100d had the DNG option. I mailed Pentax but got no response. I have no problems with PEF processing, but I'd love to have a more "future-proof" archive.


12:20 AM  
Blogger Boris said...

Thanks. Very useful article. It seems to me that batch conversion from PEF or original Pentax DNG to compressed Adobe DNG for storage and saving disk space is rather premature idea. It turns out that not all DNG files are born equal. Thanks again!

6:52 AM  
Blogger FN said...

I think Carl was saying that the DNG files didn't change, but the new ACR recognized and processed them better. So, with 3.6, it didn't recognize K10d PEF files at all, and did an OK job with K10d DNG files. With 3.7, it now recognizes K10d PEF files (according to the feature list) and also does a better job with K10d DNG files.

If I'm reading this right, and Carl correct me if I'm not, Carl didn't change his practice. He was using DNG all the time. Even his "better" results with ACR 3.7 were from DNG files.

I think the point was that DNG doesn't automatically get you perfect processing. ACR had to learn about the K10d before it could do perfect processing, regardless of whether you are doing PEF or DNG files.

On the other hand, ACR 3.6 couldn't process K10d PEF files at all. So using DNG got Carl the ability to process his files, even if it wasn't perfect.

I still call that a win for DNG.


3:42 PM  
Blogger Romerican said...

The upcoming Camera RAW for Photoshop CS3 looks quite improved.

6:22 PM  
Blogger Dave Story said...

Just a quick note -- ACR 3.6 had only "preliminary" support for the K10D until the camera was fully supported. Adobe does that in order to allow you to open a new camera's files, but doesn't officially do "final" quality support until a next release.

So that's what you experienced.

Hope that helps! And Yes, DNG is a good solution for a lot of folks.


9:44 PM  
Blogger johnfalky said...

V. 3.7 for Windows. I downloaded it, put the 8Bi section into the plug in folder according to the Adobe instructions, but where the Sam Hill do I put the DNG converter. Adobe instructions for this part appear to be missing totally.

8:57 PM  

Post a Comment

<< Home