This is the blog archive site. For the latest blog articles, click here.

Blog Archive

Raw Conversion: Better Never Than Late

April 24, 2008

And can we please stop calling them raw converters?

Most Digital SLRs, the Leica M8 rangefinder, and a few mid-priced non-SLRs (Canon G9, Leica D-Lux 3/Panasonic DMC-LX2, Sigma DP1, Ricoh GX100) can capture raw data, as well as JPEGs. A raw capture is taken straight from the sensor, so, unlike a JPEG, it has to be processed before you get a useful image. Raw captures are stored in files that end in .NEF, .CR2, .RAW, .DNG, and so on.

Operationally, the main difference between raw and JPEG is that with raw you process the data on your computer to form the image, not in the camera using preset controls (white balance, saturation, etc.). That gives you a lot more flexibility, since you can tailor the processing to the specific image, instead of having to make decisions before you've pressed the shutter. Processing is interactive—you can immediately see the effects of various adjustments.

Rather than say that a raw capture has to be processed with a computer, as though it's a disadvantage, it's better to say that it can be processed, which is an advantage. Or, to say it another way, if you edit images on a computer anyway, you're better off editing a raw capture rather than a JPEG, just as a baker can bake a better cake from raw ingredients than from an all-in-one cake mix.

(It used to be true that processing raw captures was more complex than processing JPEGs but, with modern raw processors, this is no longer the case. With some applications like Lightroom, Aperture, and Adobe Camera Raw, there's no difference at all other than file size and, of course, the results you can achieve.)

Michael Reichmann of The Luminous Landscape web site has written an excellent article that shows why editing a raw is better than editing a JPEG. You'll also want to read Thom Hogan's Quick & Dirty Guide to RAW.

Unfortunately, the most common term used to describe raw processing is "raw conversion", which implies that the purpose is to convert the raw data to a more accessible format, typically JPEG or TIFF. But as soon as you've converted you've baked in the adjustments you've made (color balance, saturation, sharpening, contrast, brightness, etc.). You may have benefited from the advantages of shooting raw while processing initially, but once you have a JPEG or a TIFF those advantages are gone for good, unless you go all the way back to the original raw and start completely over.

Raw conversion isn't the purpose of raw processing—it's an unnecessary evil. It's better not to convert at all, as I will explain.

It's useful to classify raw processors into three types, two converting and one non-converting. I'll add in-camera processing for completeness. They're listed from worst to best.

Type Comments When Appropriate
No raw Shooting JPEG rather than raw. In-camera processing based on camera settings prior to exposure. Computer processing still possible on already-baked image. When raw-processing is too time-consuming or unwarranted, file size is an issue, or the camera doesn't shoot raw.
Early Conversion Some camera-manufacturer-supplied Photoshop plugins work this way. If, when you first open a raw file you're presented with an initial panel with only a few adjustments (maybe white balance, contrast, brightness and maybe one or two others), and then the image shows up in the full-blown editor, you have early conversion. If there is no initial panel, or there is but it offers extensive editing, then you have late conversion (see next row). Should never be necessary. If you think you're getting early conversion, use a different raw processor or, if you're using Photoshop, switch to Adobe Camera Raw.
Late Conversion You do nearly all your editing, including cropping, sharpening, and maybe even spotting and localized adjustments, entirely in the raw processor, working on the full 16-bit image (or as many bits as the camera produces).

Many advanced raw-conversion applications supplied by camera manufacturers (as opposed to plugins; see previous row) work this way. So do most advanced third-party applications like Capture One, BreezeBrowserPro, and Adobe Photoshop with Adobe Camera Raw as the raw-processing plugin (if you finish by editing in Photoshop). Apple's iPhoto works this way, too.

No difference in the quality of conversion compared to non-converting (see next type), but you have to make sure you've taken full advantage of the raw form before you finish. Subsequent editing must be on the saved image (TIFF or PSD, usually) or on the original raw; no way to pick up from where you left off and still stay in the raw domain.
Non-Converting Parametric Raw file isn't modified (non-destructive editing), and neither are the changes saved as an image. Instead, your edit parameters are kept in a history list, and they're reapplied each time the image is rendered. A JPEG preview may be kept automatically to speed up viewing, but printing and exporting are from the raw image as modified by the parameters. Various formats (TIFF, JPEG, PSD, DNG) can be exported, but they aren't used for editing.

Offered by Apple Aperture, Adobe Lightroom, Nikon Capture NX, Adobe Camera Raw (if you don't go on to edit in Photoshop), Bibble (I'm told), and maybe a few others. (Most such apps provide parameterized processing for non-raw images, too, but this article is only about raw processing.)

Convenient because you don't have to store and name different versions of derivative files, you can go back and tweak the editing at any time, and you can easily and efficiently keep multiple versions of the same image.

The most common industry term for what I call non-converting parametric raw processing is non-destructive, but I don't like that term because early- and late-converters (rows 2 and 3 in the table) are also non-desctructive, in the sense that the raw file isn't modified.

Peter Krogh has written an excellent white paper, Non-Destructive Imaging: An Evolution of Rendering Technology, that explains what parametric editing is and how it works.

The difference between parameterized and non-parameterized raw processing is the same as the difference between keeping a word-processing document file or just keeping a PDF that you've rendered. If you want to make edits later, it's much easier if you can work from the original document instead of only from the already-formatted image.

Even with a parameterized raw processor, you can't stay parameterized forever for every image. If you have to go to Photoshop, you'll have to save your work as a derivative TIFF or PSD. Then it's fully baked and any further processing will be from the derivative. (Although if you're careful you can keep the layers, which gives you some benefits of parameterization.)

So, the goal is to stay raw as long as possible. If you have a non-parameterized raw processor, do as much as possible in the raw domain before you have to save your work and exit the program. With a parameterized raw processor, you can stop editing, exit the program, and pick up where you left off (perhaps rolling back some changes) at any time.

What you want to avoid as long as possible is raw conversion. And better never than late.

Link to this entry

 

Surge Protectors Actually Work!

March 12, 2008

image

I was never really sure. I have two high-end $200+ Brick Wall protectors, for my home theater system and for my computers and external drives, and the usual household assortment of cheap $20 so-called surge-protecting power strips. I had never had any surge damage, not even to a dozen or two of miscellaneous gadgets connected without any protection at all. I don't even know if I ever had a surge for which protection was needed.

So, as far as I knew, my surge protectors were working just as well as my elephant protectors. I never saw any elephants around the house, either.

Well, still no elephants, but a couple of weeks ago I really did get a surge. My alarm woke me up, running on its battery. (Nice feature!) The house had power, but the GFI in the bathroom had tripped, cutting off power to the adjacent bedroom. My computers started up OK, so one Brick Wall had worked. A few things didn't go through the Brick Wall. My DSL modem had no power at all. After I replaced its external power supply it powered up, but couldn't acquire DSL. Some cheap powered speakers were dead, too. The home theater downstairs was OK (another Brick Wall).

But the TV equipment (TV, satellite box, Sony PS2, DVD player) in a cabinet on the main level was without power. Those were connected to a cheap Belkin surge protector, which obviously had taken a big hit, as shown above. Even the case blew apart, as you can see from the damage to the seam on the side. It smelled of smoke, too.

All the equipment behind that Belkin was saved and is working OK. Way to go, Belkin!

So, now I believe in surge protectors, and I'm going to spend more than $20 on them, too. I'm not sure if I want to spring for Brick Walls all around the house, since not everything I have is even worth $200. But, if I don't, I'll probably get Belkins.

Update: Just after I posted this, I found a bunch of Belkins on Amazon, and decided to get two of these and another Brick Wall for that TV cabinet:

image

If you click the link below to buy your own Belkin, I'll get some money from Amazon, and it will cost you nothing extra:

Link to this entry

 

Enter These Characters Correctly to Win $1000

February 23, 2008

image

I am so annoyed by those enter-the-characters tests I have to take to prove I'm not a robot, like this one:

image

I recently sent out some email about a new product of mine (LRViewer), and was confronted by such a gatekeeper in order to get by someone's spam filter. I failed on my first two tries, and then switched to audio, which I thought was a cute feature. That didn't work either. So, sorry you didn't get the email... you'd really like LRViewer!

Here's my version of the test: Email me the characters you see in the figure at the top of this article and I'll send you $1000 if you're correct. I'll post the answer on Tuesday. One entry per person, and all entries must be received by next Monday. (Robots are not eligible. I am the sole judge of whether you are correct.)

In all seriousness, the only decent one I've seen is Jeffrey Friedl's:

image

Why can't everyone do it Jeffrey's way?

Link to this entry

 


Older Entries

Photography Articles

Raw Conversion: Better Never Than Late April 24, 2008

Scanning in India by Way of California With ScanCafe February 15, 2008

How To Back Up Your Personal Computer January 30, 2008

Every Camera I've Ever Owned January 25, 2008

Sharpening JPEGs for the Web January 4, 2008

Lessons Learned From My Memory Problem December 20, 2007

Hunting Down a Mac Hardware Problem December 20, 2007

Trimming GPS Tracks With GPSTrackViewer November 13, 2007

The World's Shortest Camera Buying Guide September 22, 2007

Transporting and Storing Portable Backup Drives August 26, 2007

"The Luminous Landscape" Teaches Me to Print August 4, 2007

Creating a Google Photo Map (Revised) June 26, 2007

Sony GPS-CS1: Not Good Enough for Geotagging Photos June 24, 2007

Epson P-3000/P-5000 Multimedia Storage Viewer March 10, 2007

Trying Out Infrared January 20, 2007

Stupid Designs Hold Digital Back April 1, 2006

 

Other, older articles


Galleries

image

A small collection of my best photos (click the image). You can order prints, too.


Software

image ImageIngester
image ImageVerifier
image LRViewer
image LRVmaker
image PhotoSelectLink™
image ImageReporter
image SpanBurner
image GPSTrackViewer

Books

The 2004 2nd Edition, a so-called "update" of the 1985 book, which turned out, not surprisingly, to be a re-write. Covers Solaris, Linux, FreeBSD, and Darwin (Mac OS X).


Entire contents of this web site Copyright 2006-2008 by Marc Rochkind. All rights reserved.