Luminous Landscape Forum

Equipment & Techniques => Digital Cameras & Shooting Techniques => Topic started by: macgyver on November 11, 2006, 11:33:24 pm

Title: RAW benifits/costs?
Post by: macgyver on November 11, 2006, 11:33:24 pm
First off, I'm not sure if this would go here or in the image processing fourm, but it seems to fall under the "shooting techniques" thing.  At least to me.  So, if its not a good place for it, I'm sorry.

Anyway...

Since I started serious photography, I shot in JPG.  It was a combination of lack of software, hardware limitations and general laziness.  In another thread earlier in the week I made this statement:

"I understand and enjoy and take advantage of how RAW files can be tweaked for better exposure, but I know photographers to have gotten quite lazy when shooting by using the excuse of "well, I'm shooting in RAW, I can fix it later".

There are some of us who, raw or jpg, try to get it as right as we can the first time."

I fully agree with this statement, however I thought of something today.  Only fairly recently have I really started to work with and realize the potential of RAW files.  I've shot two events in the past week or so in RAW + JPG, with the idea to have the jpgs I know and love but also be able to start working with the RAW files.  So far, I've been impressed.  Anyway, this made me consider what I earlier said.  Do you think RAW makes folks lazier?  I, of course, will always try to get it right the first time, but now I have an extra layer of assurance.  I love the ability to fine tune the exposure, WB, etc and all, but I do wonder if in the long run it will make me lazy about things.  Also, it makes me wonder how faithful I'm being to the color and look and all.  I'm one of those people who likes to try to keep it as natural and close to the orginial as possible (usually) and the more room I have to explore, the harder it is to keep it in the original ballpark.

Your thoughts?

-macgyver
Title: RAW benifits/costs?
Post by: sgwrx on November 11, 2006, 11:58:40 pm
there are other benefits to shooting raw than basic editing. image quality is also better, letting a program specifically designed to convert is typically better than that program in a camera.  there is also more data to work with when you want to dodge or burn areas of the photo.

i learned earlier this year that there is no substitue for getting it right, every time.

as far as being faithful, i think this is where artistic intent comes in.  i remember the limited color film shooting i did all those years back that fuji film showed very different color than kodak film.  raw is one option for interpreting what you see through your own artistic vision.  if you intend hyper-realistic colors of a scene you can shoot a color target and adjust as needed.  otherwise you can develop a raw file to give the impressions you had when you first saw your scene.  'wow that was really green moss on that rock' might look dull when you go for realism, but your impression was much more green.
Title: RAW benifits/costs?
Post by: dlashier on November 12, 2006, 04:14:32 am
I don't think raw has made me any lazier - I am a stickler about getting it right in the camera. True, occasionally it helps you salvage a shot where you screwed up, but there are a number of things where raw gives you flexibility than jpeg just doesn't offer. The two biggest ones that come to mind are white balance and HDR.

- DL
Title: RAW benifits/costs?
Post by: Tim Gray on November 12, 2006, 09:14:10 am
Lazier? I don't think so.  I've never thought, "well this will be ok - doesn't look all that great on the histogram, but I can fix it in RAW".

One of my lasting regrets is a trip I took to Nevada/Utah/Arizona with a 1d2 and only a 20 gig Nixvue.  I shot one the first day RAW in Valley of Fire and realized there was no way I had enough memory, so shot the rest of the trip in JPG, including Upper and Lower Antelope - what a mistake.

To Quote Mahesh Thapa from Fred Miranda's landscape site:  "Memory is cheap, but memories are priceless".

It will be interesting to see how the debate evolves now that you can do the same white balance fixes against JPGs in Lightroom as you can with RAW.

Edit:  Actually the one element of "laziness", if you will, is that I am too lazy to go through the process of deciding - "Do I need RAW for this shot, or will JPG be OK."
Title: RAW benifits/costs?
Post by: PeterLange on November 12, 2006, 06:09:26 pm
Quote
It will be interesting to see how the debate evolves now that you can do the same white balance fixes against JPGs in Lightroom as you can with RAW.
Technically impossible (whatever the SW claims).

Peter

--
Title: RAW benifits/costs?
Post by: Tim Gray on November 12, 2006, 07:02:16 pm
Quote
Technically impossible (whatever the SW claims).

Peter

--
[a href=\"index.php?act=findpost&pid=84850\"][{POST_SNAPBACK}][/a]


but practically possible (because I've actually tried it)

It 'technically' may not be 'white balance', but if it looks like a duck, and quacks like a duck...
Title: RAW benifits/costs?
Post by: dlashier on November 12, 2006, 07:07:54 pm
Quote
but practically possible (because I've actually tried it)
[a href=\"index.php?act=findpost&pid=84856\"][{POST_SNAPBACK}][/a]
I suspect that theoretically it is possible - in an ideal world (infinite DR). But I can see problems arising if the WB used for conversion induced channel clipping, which is not all that uncommon. That information is gone and no amount of tweaking after-the-fact will recover it.

- DL
Title: RAW benifits/costs?
Post by: John Sheehy on November 12, 2006, 07:17:01 pm
Quote
I, of course, will always try to get it right the first time, but now I have an extra layer of assurance.  I love the ability to fine tune the exposure, WB, etc and all, but I do wonder if in the long run it will make me lazy about things.  Also, it makes me wonder how faithful I'm being to the color and look and all.  I'm one of those people who likes to try to keep it as natural and close to the orginial as possible (usually) and the more room I have to explore, the harder it is to keep it in the original ballpark.

Your thoughts?
[a href=\"index.php?act=findpost&pid=84738\"][{POST_SNAPBACK}][/a]

There is no one such exposure that's "right", or even "natural".

The RAW data is counting photons (and adding some noise), and nothing else.  The trade-off with various levels of exposure are only signal-to-noise ratios, and highlight clipping, not "saturation" or any other concern.  If you take a shot of colorful fall trees with +2 EC and a camera contrast setting of minimum, and the colors are pale, it is not because you exposed it wrong, but because the camera's JPEG engine compressed the highlights.  Same for your favorite RAW converter.  Its default conversion may compress the highlight ranges, and depending on the converter, may or may not return the full, saturated colors when you use -1 or -2 exposure in the converter.  If you can't make it look right, it's the converter's fault, not the exposure's.  Unfortunately, many converters are pretty useless for anything more than -1 or -2, and get weird beyond that, instead of just downscaling the RAW data.  This limits how much you can "expose to the right" with your particular RAW converter.

I shoot RAW (with a few Canon DSLRs) as precisely as I can, to get as high an exposure as possible without clipping desired highlights.  I will not hesitate to go to a higher ISO to do this.  This often results in a washed out JPEG, or default conversion in software.
Title: RAW benifits/costs?
Post by: Mark D Segal on November 12, 2006, 08:19:53 pm
RAW capture isn't an invitation to be lazy, because the better the photograph the better the photograph regardless of the post-processing potential. JPGs get baked in the camera, while RAW captures need careful post-capture processing. The choice of file format is really a bit of a non-brainer. People who have the need, time or interest to maximize image quality will shoot RAW and people who don't will shoot JPG. It isn't a value judgement on either practice - just a matter of needs and preferences.
Title: RAW benifits/costs?
Post by: BernardLanguillier on November 12, 2006, 09:04:11 pm
Quote
RAW capture isn't an invitation to be lazy, because the better the photograph the better the photograph regardless of the post-processing potential. JPGs get baked in the camera, while RAW captures need careful post-capture processing. The choice of file format is really a bit of a non-brainer. People who have the need, time or interest to maximize image quality will shoot RAW and people who don't will shoot JPG. It isn't a value judgement on either practice - just a matter of needs and preferences.
[a href=\"index.php?act=findpost&pid=84864\"][{POST_SNAPBACK}][/a]

RAW is not really a choice for me, it is the only available option from a pratical standpoint.

Why am I saying so?

There are physical limitations on camera bodies that make it impossible to add many more controls beyond those already present (and mostly the same as those we had in the film days). We do now have ISO and WB readily available on some bodies, but that is basically it.

However, digital photogaphy introduces many other important "software" variables that greatly impact the final image. Contrast, color space, sharpness,... each image would in fact require tweaking of these paramaters to get best results.

These parameters are available in camera, but mostly only through menus... and therefore practially unusable for anyone shooting in the outdoors in changing conditions.

One the main values of RAW from this standpoint is the fact that we do not have to think about those parameters in the field. This is a life saver when looking for the best image quality when speed matters.

Cheers,
Bernard
Title: RAW benifits/costs?
Post by: jani on November 13, 2006, 04:56:00 am
Quote
One the main values of RAW from this standpoint is the fact that we do not have to think about those parameters in the field. This is a life saver when looking for the best image quality when speed matters.
Bingo!
Title: RAW benifits/costs?
Post by: Henrik Paul on November 13, 2006, 05:11:01 am
To my mind, shooting raw doesn't have to do with laziness. The ability to correct the exposure later on on raw is much less to that of black and white negative film (not to mention also the lack of white balance settings there .

But on a serious topic, it's a tit-for-tat situation, as I see it. Sure, you get more leeway in adjusting on the computer, but then again you most often have to do adjusting on the computer. With shooting JPEG, you get much less freedom to correct your photo afterwards, but then again, the camera has already done that for you.

So, actually, IMO shooting raw means more work than JPEG.
Title: RAW benifits/costs?
Post by: PeterLange on November 13, 2006, 03:37:02 pm
Quote
It will be interesting to see how the debate evolves now that you can do the same white balance fixes against JPGs in Lightroom as you can with RAW.
Quote
Technically impossible (whatever the SW claims).
Quote
but practically possible (because I've actually tried it)

It 'technically' may not be 'white balance', but if it looks like a duck, and quacks like a duck...

Proper white-balance all along the grayscale (!) requires native Raw data, before they get bended through the inevitable tone curve.

As concluded earlier:  to white-balance JPGs is like trying to “nailing jelly to a tree”:
http://luminous-landscape.com/forum/index....l=white+balance (http://luminous-landscape.com/forum/index.php?showtopic=9312&hl=white+balance)

Or should we try it with the duck .

Seriously, it’s both – a math thing as well as a real-world issue.

Peter

--
Title: RAW benifits/costs?
Post by: John Sheehy on November 13, 2006, 04:42:50 pm
Quote
Proper white-balance all along the grayscale (!) requires native Raw data, before they get bended through the inevitable tone curve.

As concluded earlier:  to white-balance JPGs is like trying to “nailing jelly to a tree”:
[a href=\"index.php?act=findpost&pid=85000\"][{POST_SNAPBACK}][/a]

An easy way to demonstrate this is to create a gradient in Photoshop that goes from 0,0,0 to 255,255,128 [later edit; originally mistyped 0,0,128].  You get a gradient that goes from black to yellow, such as with a yellow light.  After filling a rectangle with the gradient, open the levels tool, select the blue channel, and pull the input whitepoint down to 128.  Everything turns grey; nice.

Cancel out of the Levels dialog, and open curves.  Make a nice big s-curve.  Now, go back to Levels and try again - no matter what you do, the bright half will always be too yellow, or the dark half will always be too blue.
Title: RAW benifits/costs?
Post by: PeterLange on November 14, 2006, 03:27:51 pm
Quote
An easy way to demonstrate this ...
[a href=\"index.php?act=findpost&pid=85009\"][{POST_SNAPBACK}][/a]
Couldn't agree more.
Such testing hits the nail on the head.

Peter

--
Title: RAW benifits/costs?
Post by: larsrc on November 14, 2006, 03:44:57 pm
Quote
But on a serious topic, it's a tit-for-tat situation, as I see it. Sure, you get more leeway in adjusting on the computer, but then again you most often have to do adjusting on the computer. With shooting JPEG, you get much less freedom to correct your photo afterwards, but then again, the camera has already done that for you.

So, actually, IMO shooting raw means more work than JPEG.
[a href=\"index.php?act=findpost&pid=84907\"][{POST_SNAPBACK}][/a]

That's one thing that has bothered me about the raw conversion programs I've tried so far (UFRaw, Bibble) -- where's the "I want this converted like the camera took a JPG" option?  White balance, yes, but the camera exposure curve I haven't been able to find.  Is this just me, or crappy tools?  If I had a single button going "To camera JPEG", I would never consider RAW+JPEG again.

-Lars
Title: RAW benifits/costs?
Post by: 32BT on November 14, 2006, 04:33:08 pm
Quote
An easy way to demonstrate this is to create a gradient in Photoshop that goes from 0,0,0 to 0,0,128.  You get a gradient that goes from black to yellow, such as with a yellow light.  After filling a rectangle with the gradient, open the levels tool, select the blue channel, and pull the input whitepoint down to 128.  Everything turns grey; nice.

Cancel out of the Levels dialog, and open curves.  Make a nice big s-curve.  Now, go back to Levels and try again - no matter what you do, the bright half will always be too yellow, or the dark half will always be too blue.
[a href=\"index.php?act=findpost&pid=85009\"][{POST_SNAPBACK}][/a]

You guys crack me up... :-)  wrong approach:

Presuming you meant (0, 0, 0) to (255, 255, 128), otherwise it'd be blue, try this:

- create the image with S-curve and all.
- go to curve dialog
- select blue channel
- move the white point horizontally toward the blackpoint side until the midtones are gray
- add a midpoint to fix the curve
- move the white point back (curve will automatically clip with a shoulder)
Title: RAW benifits/costs?
Post by: Tim Gray on November 14, 2006, 04:58:55 pm
I'd be interested in someone describing a test that demonstrates the shortcomings of adjusting JPG WB in Lightroom, not PS.
Title: RAW benifits/costs?
Post by: dlashier on November 14, 2006, 05:23:33 pm
Quote
I'd be interested in someone describing a test that demonstrates the shortcomings of adjusting JPG WB in Lightroom, not PS.
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=85251\")
Haven't tried this but I'm guessing [a href=\"http://www.lashier.com/home.cfm?dir_cat=26147]this shot[/url] would cause problems. I don't have LR installed but if you want to try it, the "as shot" jpeg (web sized) is at http://lashier.com/images/ND26149p.jpg (http://lashier.com/images/ND26149p.jpg)
I'd be surprised if you can get anything that even remotely resembles adjusting WB in the RC.

This is not my image - if you post a result please tag it with Bernd Angerer's copyright.

- DL
Title: RAW benifits/costs?
Post by: PeterLange on November 14, 2006, 05:26:36 pm
Create a grayscale in a D65 space like Adobe RGB.
Convert AbsCol to a D50 space like ProPhoto RGB,
in order to create a realistic cold bluish grayscale
(including a nice clipping issue, but let’s ignore this for the moment).

Try to whitebal via Levels’-highlights. Should still work because linear scaling is ignorant to ‘gamma’.

Apply a pronounced S-curve.

Try to whitebal to neutral R=G=B again, with any procedure preferred…

A curve is then of course better than setting the highlights, but all in all Good luck!  Knowing the law of gravitation, I don’t have to drop all the dishes to see it work.

Peter

--
Title: RAW benifits/costs?
Post by: John Sheehy on November 15, 2006, 12:29:45 am
Quote
You guys crack me up... :-)  wrong approach:

Presuming you meant (0, 0, 0) to (255, 255, 128),

Yes, that's what I meant to type, but isn't what came out.

Quote
otherwise it'd be blue, try this:

- create the image with S-curve and all.
- go to curve dialog
- select blue channel
- move the white point horizontally toward the blackpoint side until the midtones are gray
- add a midpoint to fix the curve
- move the white point back (curve will automatically clip with a shoulder)
[a href=\"index.php?act=findpost&pid=85239\"][{POST_SNAPBACK}][/a]

It will never be exact, though, and any further processing will bring that out.  Real RAW conversions and JPEGs also have other issues, much more complex than a curve applied to an RGB image; hues are shifted and saturation is altered based on RAW hue and saturation, black is not black, etc.

In an already-converted image, you do the best you can to WB.  In a yet-to-be-converted one, you do it right.

My demo was not intended to be a hopeless case that could not be adjusted, at least coarsely; it was a visual demonstration of the effects of inconsistent gamma on color balance.
Title: RAW benifits/costs?
Post by: Wayne Lorentz on November 15, 2006, 12:34:22 am
Quote
Do you think RAW makes folks lazier?
[a href=\"index.php?act=findpost&pid=84738\"][{POST_SNAPBACK}][/a]
A lazy photographer will be a lazy photographer no matter what equipment or technology he has.

That said, I made the switch from JPEG to RAW about two years ago and will never go back.  Here's why:

Not everyone shoots in a studio.  If you're like me, and shoot outside, you don't have the time that a studio photographer has to compose your subject.  You can't tell a deer to "gimme that look again" after it bolts off through the woods.  Capturing the moment in RAW means that I have the moment, even if I have to extract it from the data with a computer.  At least I have an image I can work with.  Yes, I might have that same image in JPEG.  Or I might not.  If the exposure or some other factor wasn't quite right, I could end up with a garbage JPEG instead of a salvagable RAW file.
Title: RAW benifits/costs?
Post by: John Sheehy on November 15, 2006, 12:37:03 am
Quote
I'd be interested in someone describing a test that demonstrates the shortcomings of adjusting JPG WB in Lightroom, not PS.
[a href=\"index.php?act=findpost&pid=85251\"][{POST_SNAPBACK}][/a]

That was about mutliple gammas used in an image, not about PS per se.
Title: RAW benifits/costs?
Post by: 32BT on November 15, 2006, 04:08:17 am
Quote
It will never be exact, though, and any further processing will bring that out.  Real RAW conversions and JPEGs also have other issues, much more complex than a curve applied to an RGB image; hues are shifted and saturation is altered based on RAW hue and saturation, black is not black, etc.

In an already-converted image, you do the best you can to WB.  In a yet-to-be-converted one, you do it right.

Agreed. In that respect I'm still not sure what to make of the white balance implementation in Aperture (and some of the other converters). Is the WB corrected after the fact? (As the WB adjustment module is the last in the row?)
Title: RAW benifits/costs?
Post by: 32BT on November 15, 2006, 04:41:03 am
Quote
Knowing the law of gravitation, I don’t have to drop all the dishes to see it work.

Sure, but varying a single channel only, as per the original example, does not introduce the problematic hue shifts. The hue shifts introduced there are a result of applying the cure (gamma curve instead of a linear curve). In other words, the dishes didn't break because of gravity, but because of trying to nail the jelly to the dishes afterwards... ;-)
Title: RAW benifits/costs?
Post by: PeterLange on November 15, 2006, 07:39:31 am
Quote
In other words, the dishes didn't break because of gravity, but because of trying to nail the jelly to the dishes afterwards... ;-)
Or this way round.

Tell you what - I simply join your agreement with John:

>>  In an already-converted image, you do the best you can to WB.  In a yet-to-be-converted one, you do it right.  <<

Peter

--
Title: RAW benifits/costs?
Post by: Mark D Segal on November 15, 2006, 08:03:43 am
Quote
Or this way round.

Tell you what - I simply join your agreement with John:

>>  In an already-converted image, you do the best you can to WB.  In a yet-to-be-converted one, you do it right.  <<

Peter

--
[a href=\"index.php?act=findpost&pid=85384\"][{POST_SNAPBACK}][/a]

Peter it isn't clear to me what you are saying here. First  when is the image converted - by the time it is downloaded from the camera and opened in Camera Raw, or after youo finish in Camera Raw and open it in Photoshop. Usually when we speak of "conversion" it is the latter. Now if we're on the same page with that, I'm not sure what " doing it right" means in this context. We can white-balance either in the raw converter (say Camera Raw or Lightroom) or in Photoshop in largely the same way. I know the data differs between these two platforms, but setting theory aside I haven't seen what difference it makes to the quality of real-world (16-bit) images whether one makes this adjustment in the one program or the other.
Title: RAW benifits/costs?
Post by: Tim Gray on November 15, 2006, 09:24:44 am
At at least one point in the thread the question was how well (or how poorly) the "one click" WB tool in LR could deal with WB error in an 8 bit file.  The concensus was "nailing jello to a tree" - but that was in the context of PS, not LR.

If the issue is that the WB adjustment in 8 bit space causes clipping (or can cause more clipping than adjusting in 12/14bit space) then that's fine, but I'm just wondering when saying that the benefits of RAW are better dynamic range/headroom AND the ability to adjust WB after the fact - if the reference to WB is redundant.

I'll play around this weekend with some shots of a Gretag card, solux light and see what happens. For example, RAW, WB based on the dropper, convert to 8 bit tif.  Then compare to the same RAW file that's been WB'd based on, say tungsten, convert to 8 bit tif, bring back into Lightroom and re-white balance with the dropper, export to 8 bit tif and compare to the first file.
Title: RAW benifits/costs?
Post by: jani on November 15, 2006, 12:00:24 pm
Quote
At at least one point in the thread the question was how well (or how poorly) the "one click" WB tool in LR could deal with WB error in an 8 bit file.  The concensus was "nailing jello to a tree" - but that was in the context of PS, not LR.

If the issue is that the WB adjustment in 8 bit space causes clipping (or can cause more clipping than adjusting in 12/14bit space) then that's fine, but I'm just wondering when saying that the benefits of RAW are better dynamic range/headroom AND the ability to adjust WB after the fact - if the reference to WB is redundant.

I'll play around this weekend with some shots of a Gretag card, solux light and see what happens. For example, RAW, WB based on the dropper, convert to 8 bit tif.  Then compare to the same RAW file that's been WB'd based on, say tungsten, convert to 8 bit tif, bring back into Lightroom and re-white balance with the dropper, export to 8 bit tif and compare to the first file.
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=85399\")

I tried to test JPEG vs RAW in Lightroom a real world example that I've struggled with earlier, without being completely satisfied with either alternative.

The lighting conditions in the scene are pretty bad; tungsten and fluorescent, spotlights bounced out of store windows, and it's night time. The JPEG was shot with auto white balance.

[a href=\"http://folk.uio.no/jani/hobbies/photo/test/high+shadow/_MG_8285.JPG]Original JPEG[/url], 2544x1696, ca. 1.75 MB
DNG from raw file (http://folk.uio.no/jani/hobbies/photo/test/high+shadow/_MG_8285-raw.dng), 3504x2336, ca. 7 MB

Feel free to download the above unprocessed files and experiment a bit for yourself for the sake of this discussion; sorry about the different sizes, but I don't shoot full size JPEGs (not that the quality is such that full size would be defendable, anyway).

The wall of the building in the background is painted concrete, I don't recall which colour exactly. The street sign has an almost perfectly white plastic bag over it. The girls' tops were almost perfectly white, the jeans are of course jeans-blue. The concrete stairs were close to neutral grey, the tiles on the ground are perhaps a shade warmer than neutral.

The results by using the WB tool on the JPEG are abysmal; skin tones are either too pink, or other parts of the image are way too blue, or a combination. No matter how I tweak colour temperature or tint, I can't get close to what I get from the raw conversion.

(my interpretation (http://folk.uio.no/jani/hobbies/photo/test/high+shadow/_MG_8285.jpg))

Is that worth it? Not to me.

FWIW, Lightroom makes the raw adjustments significantly easier than ACR ever did, I feel like I have better control of the light curve. But I'd still like to have even more control over the light curve, similar to that of the curves tool in Photoshop, or perhaps something even better, whatever that would be.
Title: RAW benifits/costs?
Post by: Mark D Segal on November 15, 2006, 01:26:40 pm
Quote
At at least one point in the thread the question was how well (or how poorly) the "one click" WB tool in LR could deal with WB error in an 8 bit file.  The concensus was "nailing jello to a tree" - but that was in the context of PS, not LR.

If the issue is that the WB adjustment in 8 bit space causes clipping (or can cause more clipping than adjusting in 12/14bit space) then that's fine, but I'm just wondering when saying that the benefits of RAW are better dynamic range/headroom AND the ability to adjust WB after the fact - if the reference to WB is redundant.

I'll play around this weekend with some shots of a Gretag card, solux light and see what happens. For example, RAW, WB based on the dropper, convert to 8 bit tif.  Then compare to the same RAW file that's been WB'd based on, say tungsten, convert to 8 bit tif, bring back into Lightroom and re-white balance with the dropper, export to 8 bit tif and compare to the first file.
[a href=\"index.php?act=findpost&pid=85399\"][{POST_SNAPBACK}][/a]

Tim, unless I don't understand properly - always possible - it seems to me that too many variables are being comingled here. If you are going to test anything, best to sort out the questions and the procedures to isolate one variable at a time.

I doubt that 8 or 16 bit image mode has anything to do with WB or the ability to achieve an acceptable WB by making adjustments in any of these programs. But that is one question to test all by itself.

As far as I understand, the WB dropper in Lightroom is about the same as the WB dropper in Camera Raw, is about the same thing as the middle grey dropper in Curves in PSCS 2. You point all of them to something you think or are sure is neutral and it will make that hue neutral and adjust everything else "pro rata". So the second question is whether for a given bit depth any one of these programs do it better IN REALITY than the others.

I believe that in the process of applying a WB adjustment, the larger that adjustment needs to be the more assurance you will have from both a RAW file and higher bit depth that the risk of image break-up is minimized, but testing the exact value of that "insurance" (RAW versus JPG and/or 8 bit versus 16 bit) is yet another question.
Title: RAW benifits/costs?
Post by: dlashier on November 15, 2006, 02:05:35 pm
Quote
If the issue is that the WB adjustment in 8 bit space causes clipping (or can cause more clipping than adjusting in 12/14bit space) then that's fine, but I'm just wondering when saying that the benefits of RAW are better dynamic range/headroom AND the ability to adjust WB after the fact - if the reference to WB is redundant.
[a href=\"index.php?act=findpost&pid=85399\"][{POST_SNAPBACK}][/a]
The clipping issue I'm referring to has nothing to do with 8/16 bit space but rather the fact that with an image like the example I provided earlier, WB choice at raw conversion time affects clipping at both ends of the spectrum, and once this data is gone there is no way to recover it for a different WB without guessing. This is aside from the fact applying gamma and tone curves have been applied that further stretch or compress parts of the data. I would think that a very smart algorithm that was aware of preceding tonal/gamma adjustments could accurately do after the fact WB adjustment (preferably on a 16 bit image), but I don't see how it could account for clipped data.

Again, non-believers can try the example I posted. The original impetus for that example was because Bernd ran into exactly this sort of problem when trying to adjust the WB in Photoshop.

- DL
Title: RAW benifits/costs?
Post by: PeterLange on November 15, 2006, 04:53:55 pm
Quote
[{POST_SNAPBACK}][/a] (http://index.php?act=findpost&pid=85387\")
Quote
[a href=\"index.php?act=findpost&pid=85447\"][{POST_SNAPBACK}][/a]
Mark,

I’m not sure what I could further contribute. Your last post seems to answer your previous one perfectly.

The second aspect of WB Raw vs JPG (beside channel clipping) is Uniformity.  Without indenting to advocate for neutral white, for example, when you adjust one single bright gray patch to R=G=B, does it lead to neutrals all along the grayscale, or would a brighter gray still show e.g. a green color cast while a darker gray patch might reveal a complementary magenta hue.  For illustration, above suggested tests (as they read now) should have their validity.  Relevance will certainly depend on the image content, light conditions, personal tolerance and the WB approach in detail, etc.  Let’s hope that the WB dropper in LR at least switches from linear scaling via single R/G/B ‘highlights’ (perfect with Raw data) to something more complex & curved for already-processed JPGs; as it was good [a href=\"http://www.creativepro.com/printerfriendly/story/13811.html]tradition[/url] in Photoshop.

Peter

--
Title: RAW benifits/costs?
Post by: howiesmith on November 16, 2006, 11:43:23 am
I may have missed it, but I can't find any info here on the cost of RAW.

IF you could get two identical cameras except for RAW (one with, one without), how much difference in price should there be?  How much more would you actually pay (not might be interested at this price)?
Title: RAW benifits/costs?
Post by: Tim Gray on November 16, 2006, 01:00:44 pm
I don't think the difference in camera cost is the issue.  All cameras actually capture RAW in the beginning regardless of what happens later - maybe a bigger buffer etc.  The incremental cost is in needing more field storage, higher horsepower processing and more archival storage, as well as potentially conversion time (although that's easier to manage/mitigate).
Title: RAW benifits/costs?
Post by: howiesmith on November 16, 2006, 01:38:35 pm
Quote
I don't think the difference in camera cost is the issue.  All cameras actually capture RAW in the beginning regardless of what happens later - maybe a bigger buffer etc.  The incremental cost is in needing more field storage, higher horsepower processing and more archival storage, as well as potentially conversion time (although that's easier to manage/mitigate).
[a href=\"index.php?act=findpost&pid=85624\"][{POST_SNAPBACK}][/a]

Understood.  But all that comes with a $$$ cost.  What is it?  And how much are you willing to spend to get it - even if it is there and just discarded.

Horsepower is your example.  I can buy a car that is essentially equivalent to another but for horsepower (and the stuff that comes with more or less horsepower, like mpg.)  How much more will I pay for a car with just more power?

Let's say I have a kit that you can install on a G7 to get RAW output.  How much would you pay for it?
Title: RAW benifits/costs?
Post by: Tim Gray on November 16, 2006, 03:30:20 pm
Quote
Understood.  But all that comes with a $$$ cost.  What is it?  And how much are you willing to spend to get it - even if it is there and just discarded.

Horsepower is your example.  I can buy a car that is essentially equivalent to another but for horsepower (and the stuff that comes with more or less horsepower, like mpg.)  How much more will I pay for a car with just more power?

Let's say I have a kit that you can install on a G7 to get RAW output.  How much would you pay for it?
[a href=\"index.php?act=findpost&pid=85632\"][{POST_SNAPBACK}][/a]

From strictly the camera perspective I would be irritated to have to pay anything.  As I said, the camera already creates a RAW file.  But to specifically answer the question, I'd pay - say $100 to get a 3 or 4 shot buffer with, say 1 second between shots.  I'd pay $200 to get a 5 shot buffer with no noticeable lag between shots.  I'd pay $300 to get a 15 shot buffer etc. etc. etc.

"Getting it" is more than just the cost of the camera.  If I was shooting JPG and was considering RAW (I shoot roughly 20,000 frames per year) I'd need to add another 4 gig in CF cards (assuming my 1d2) and 8 gig if it was a 1ds2.  I'd need a bigger drive in my Hyperdrive - say $50 incremental difference between a 60 gig and 120 gig.  I'd want 2 gig ram in my pc over 1 - say another $100. ($ CDN)  Archiving depends.  I only save the raw files that I work up and I only save the raw and final jpg, not multilayer 16 bit tif files, so your mileage will vary.  If I upgrade to the mythical 1d3 I'd probably get an entire new PC system.
Title: RAW benifits/costs?
Post by: howiesmith on November 16, 2006, 04:02:13 pm
Quote
From strictly the camera perspective I would be irritated to have to pay anything.  As I said, the camera already creates a RAW file.  But to specifically answer the question, I'd pay - say $100 to get a 3 or 4 shot buffer with, say 1 second between shots.  I'd pay $200 to get a 5 shot buffer with no noticeable lag between shots.  I'd pay $300 to get a 15 shot buffer etc. etc. etc.


[a href=\"index.php?act=findpost&pid=85662\"][{POST_SNAPBACK}][/a]

I think you know you are paying to get RAW now.  There is no free lunch.

But, at about $450 for a RAWless G7, you would pay 20 to 60% more to get  a G7 with RAW?  That is a lot of money to some folks who just want a "nice camera."
Title: RAW benifits/costs?
Post by: Tim Gray on November 16, 2006, 06:33:46 pm
Well, I wouldn't buy a G7 at any price since my Sony R1 (with RAW) is perfect for my needs as a second camera.  But, if a "P&S" had everything I wanted except RAW, I'd pay $100 to get basic raw capability, IF I wanted a bigger buffer and faster read times, I'd pay for that as well.  Regardless, a P&S with everything I want except RAW is going to cost significantly more than $500.

The lions share of the cost attributable to RAW in my 1d2 isn't having raw per se, rather its the cost of the buffer and speed with which 8 mpx files can be captured.  As I said before, RAW is captured by every digital camera made.  What you're paying for in a camera with no raw option, is the programming that processes  raw, ie the in camera jpg processing and associated options - sharpening, saturation, file size, degree of compression etc.  There's no free jpg lunch either.  The creation of the raw file is always there, it's not an option.
Title: RAW benifits/costs?
Post by: thomashoven on November 17, 2006, 12:15:22 am
I am a lazy photographer - I shoot all my stuff in RAW even if I only use a digicam. Then I don't need to think about what format when I shoot. From my Digicam, $100 worth of memorycards can hold 100s of pics - no need to run out of memory these days.

At home, I batch-convert everything into JPG, and keep both the RAW and JPG files (DVD discs are also cheap these days).

With family and friends, I fool around with my JPG files. If I find a smashing shot where the JPG look terrible, I go back to the RAW of that image for a customized conversion/editing.

Rgds,
Thomas
Title: RAW benifits/costs?
Post by: rainer_v on November 17, 2006, 04:43:28 am
mcgyver,- may i ask what this tread has  to do in any way with mf backs?
i am not often unpolied, but if you were shooting jpegs till now, you might find really better forums for such fundamental steps.
Title: RAW benifits/costs?
Post by: macgyver on November 20, 2006, 02:07:03 am
Quote
mcgyver,- may i ask what this tread has  to do in any way with mf backs?
i am not often unpolied, but if you were shooting jpegs till now, you might find really better forums for such fundamental steps.
[a href=\"index.php?act=findpost&pid=85771\"][{POST_SNAPBACK}][/a]


Rehnniar,

First, I never said anything about Medium Format backs, although my original question works for any camera.

Second, thank you for suggesting I head for fourms more suited for more "fundamental steps", however, you will notice that my question was not a technical one, but an invitation for an open discussion on how shooting raw affects someone's desire for precision.  (For lack of better terms)  The thread has strayed a bit, but still been very interesting reading.

Let me ask all of you this then, did my question make sense to you?  Do you think you know what I was getting at?

-mac
Title: RAW benifits/costs?
Post by: Jonathan Wienke on November 20, 2006, 06:57:12 am
I shoot RAW basically 100% of the time; the only exception being when I have to shoot so fast that the camera will not keep up in RAW mode. This is a pretty rare thing; the last time it happened was when covering a horse show event where I had to shoot 25 horses & riders in an event lasting <5 minutes and get salable shots of each. For the remaining 99+% of my shooting, RAW has the following advantages:

1. The freedom to defer all processing decisions until after the shoot. I don't have to care about white balance, color spaces, tone curves, sharpening, etc.; all I need to think about while shooting is getting composition, exposure, and focus right.

2. RAW gives you 100% of the camera's color gamut and capture dynamic range. Camera JPEGs do not. Period. The amounts of DR and gamut you lose by shooting JPEG vary from camera to camera and depend on the camera settings, but you always lose something. I'd rather not.

3. Your image processing options are much more flexible when working with high-bit image data that hasn't been dumbed down to 8 bits per channel. Noise is easier to get rid of, you don't have any JPEG artifacts, and you can get much more aggressive with levels and curves before encountering banding and posterization. A high-bit workflow will always deliver a better result than an 8-bit workflow; if you perfectly expose and white balance in camera, you can get kind of close with 8-bit. But if you don't get everything perfect in-camera, the 8-bit version will be noticeably inferior.

4. A properly-profiled RAW converter will save you an enormous amount of time color correcting images. All you need to do is set the white balance properly to get accurate, natural colors that in many cases will not need any further tweaking. This is a godsend when batch processing wedding images or yearbook portraits. I use Tom Fors' ACR calibration script and a Color Checker, and my Canon 1Ds, 1D-MkII, and Olympus SP-350 RAWS all deliver consistent, natural colors that require very little tweaking in PS. The same is not true of most cameras' internal JPEG processing profiles, especially if the camera white balance setting isn't quite perfect. It's like using a custom printer profile instead of the canned one-size-fits-all factory profile. Many of you have seen the difference a good printer profile can make for your prints; shooting RAW can do the same for your image files in PS.

Shooting RAW means larger files and more storage, and maybe a faster computer. But it makes a real difference in the end product if you master it. It is not a crutch for technical sloppiness, but it can make the difference between an acceptable and unacceptable end image if Murphy happens to stand over your shoulder when you press the shutter release.
Title: RAW benifits/costs?
Post by: digitaldog on November 20, 2006, 02:05:52 pm
Quote
but practically possible (because I've actually tried it)

It 'technically' may not be 'white balance', but if it looks like a duck, and quacks like a duck...
[a href=\"index.php?act=findpost&pid=84856\"][{POST_SNAPBACK}][/a]

You can 'white balance' on any file in Photoshop; all you're doing is altering pixel values. We've had the white/gray and black eyedroppers since V1.

The big deal about doing this in raw is you're never touching the raw data, the white balance info is simply some EXIF data recommendations and you can render the WB in the converter as many times and ways as you wish, always producing new sets of pixels from the data source. You could kind of do the same on a JPEG or TIFF by first duplicating the file 10 times and applying 10 different image tweaks which you can call white balance (or gray balance or anything else). You need 10 copies because if you try this 10 times on the same file, unless you do this on 10 adjustment layers, you're going to degrade the file once you stamp the edit(s).

LR isn't any different in handling rendered image compared to Photoshop using 10 adjustment layers in the end. The main differences are the speed and the ability to render only the one edit into the pixels once you find a setting you like. But all LR edits require you build a copy of the original and then apply the edits to the copied rendered pixels. I don't see this fundamentally different from Photoshop other than the workflow involved.
Title: RAW benifits/costs?
Post by: digitaldog on November 20, 2006, 02:14:25 pm
Quote
As far as I understand, the WB dropper in Lightroom is about the same as the WB dropper in Camera Raw, is about the same thing as the middle grey dropper in Curves in PSCS 2.

Considering that LR and ACR use the same processing pipeline, that's a fair assumption.

As for Photoshop, the big difference I can think of is the fact that you're working in a gamma encoded working space which isn't the case in LR or ACR. Both are working in ProPhoto RGB primaries and White Point (so in Photoshop you'd need to use that) however, in those converters are using a linear gamma encoding. How that may or may not affect WB I don't know (but suspect it would play some role). EVEN with existing rendered images, LR uses this "bastard RGB" color space as it's been described inside of Adobe (a better name is Melissa RGB).
Title: RAW benifits/costs?
Post by: ErikKaffehr on November 20, 2006, 04:16:32 pm
Why I prefere raw:

These are the advantages I see with raw:

1) I don't need to care about white balance I leave it on auto and fix later.

2) I can optimize exposure for highlights. My main concern is that I don't get overexposure in important parts of the picture, I can fix the rest later.

I don't really see any disadvantages, but quite clearly it is more work!

Best regards

Erik

Quote
First off, I'm not sure if this would go here or in the image processing fourm, but it seems to fall under the "shooting techniques" thing.  At least to me.  So, if its not a good place for it, I'm sorry.

Anyway...

Since I started serious photography, I shot in JPG.  It was a combination of lack of software, hardware limitations and general laziness.  In another thread earlier in the week I made this statement:

"I understand and enjoy and take advantage of how RAW files can be tweaked for better exposure, but I know photographers to have gotten quite lazy when shooting by using the excuse of "well, I'm shooting in RAW, I can fix it later".

There are some of us who, raw or jpg, try to get it as right as we can the first time."

I fully agree with this statement, however I thought of something today.  Only fairly recently have I really started to work with and realize the potential of RAW files.  I've shot two events in the past week or so in RAW + JPG, with the idea to have the jpgs I know and love but also be able to start working with the RAW files.  So far, I've been impressed.  Anyway, this made me consider what I earlier said.  Do you think RAW makes folks lazier?  I, of course, will always try to get it right the first time, but now I have an extra layer of assurance.  I love the ability to fine tune the exposure, WB, etc and all, but I do wonder if in the long run it will make me lazy about things.  Also, it makes me wonder how faithful I'm being to the color and look and all.  I'm one of those people who likes to try to keep it as natural and close to the orginial as possible (usually) and the more room I have to explore, the harder it is to keep it in the original ballpark.

Your thoughts?

-macgyver
[a href=\"index.php?act=findpost&pid=84738\"][{POST_SNAPBACK}][/a]
Title: RAW benifits/costs?
Post by: Tim Gray on November 20, 2006, 05:46:04 pm
Quote
You can 'white balance' on any file in Photoshop; all you're doing is altering pixel values. We've had the white/gray and black eyedroppers since V1.

The big deal about doing this in raw is you're never touching the raw data, the white balance info is simply some EXIF data recommendations and you can render the WB in the converter as many times and ways as you wish, always producing new sets of pixels from the data source. You could kind of do the same on a JPEG or TIFF by first duplicating the file 10 times and applying 10 different image tweaks which you can call white balance (or gray balance or anything else). You need 10 copies because if you try this 10 times on the same file, unless you do this on 10 adjustment layers, you're going to degrade the file once you stamp the edit(s).

LR isn't any different in handling rendered image compared to Photoshop using 10 adjustment layers in the end. The main differences are the speed and the ability to render only the one edit into the pixels once you find a setting you like. But all LR edits require you build a copy of the original and then apply the edits to the copied rendered pixels. I don't see this fundamentally different from Photoshop other than the workflow involved.
[a href=\"index.php?act=findpost&pid=86199\"][{POST_SNAPBACK}][/a]

Just to reiterate the context of my original post, and for the record I shoot 100% raw.  

In every summary recitation of the benefits of RAW 2 things are mentioned - WB adjustment and more headroom when making level/curve/shadow/highlight etc. etc. adjustments.  I was trying to get a sense of how the LR wb tool fit in the context of those 2 advantages.  I got the comment several days ago from a friend when I was discussing the benefits of RAW that since LR now had an explicit wb tool that can be applied to JPG, that that negated one of the 2 fundamental reasons to shoot raw over jpg.  

As far as I can tell so far, the LR wb tool is easier than doing it in native PS, but still falls considerably short of what you can do in RAW with a challenging file.
Title: RAW benifits/costs?
Post by: Chris_T on November 26, 2006, 09:51:02 am
Quote
I shoot RAW basically 100% of the time; the only exception being when I have to shoot so fast that the camera will not keep up in RAW mode. This is a pretty rare thing; the last time it happened was when covering a horse show event where I had to shoot 25 horses & riders in an event lasting <5 minutes and get salable shots of each. For the remaining 99+% of my shooting, RAW has the following advantages:

1. The freedom to defer all processing decisions until after the shoot. I don't have to care about white balance, color spaces, tone curves, sharpening, etc.; all I need to think about while shooting is getting composition, exposure, and focus right.

2. RAW gives you 100% of the camera's color gamut and capture dynamic range. Camera JPEGs do not. Period. The amounts of DR and gamut you lose by shooting JPEG vary from camera to camera and depend on the camera settings, but you always lose something. I'd rather not.

3. Your image processing options are much more flexible when working with high-bit image data that hasn't been dumbed down to 8 bits per channel. Noise is easier to get rid of, you don't have any JPEG artifacts, and you can get much more aggressive with levels and curves before encountering banding and posterization. A high-bit workflow will always deliver a better result than an 8-bit workflow; if you perfectly expose and white balance in camera, you can get kind of close with 8-bit. But if you don't get everything perfect in-camera, the 8-bit version will be noticeably inferior.

4. A properly-profiled RAW converter will save you an enormous amount of time color correcting images. All you need to do is set the white balance properly to get accurate, natural colors that in many cases will not need any further tweaking. This is a godsend when batch processing wedding images or yearbook portraits. I use Tom Fors' ACR calibration script and a Color Checker, and my Canon 1Ds, 1D-MkII, and Olympus SP-350 RAWS all deliver consistent, natural colors that require very little tweaking in PS. The same is not true of most cameras' internal JPEG processing profiles, especially if the camera white balance setting isn't quite perfect. It's like using a custom printer profile instead of the canned one-size-fits-all factory profile. Many of you have seen the difference a good printer profile can make for your prints; shooting RAW can do the same for your image files in PS.

Shooting RAW means larger files and more storage, and maybe a faster computer. But it makes a real difference in the end product if you master it. It is not a crutch for technical sloppiness, but it can make the difference between an acceptable and unacceptable end image if Murphy happens to stand over your shoulder when you press the shutter release.
[a href=\"index.php?act=findpost&pid=86144\"][{POST_SNAPBACK}][/a]

Can the RAW shooters comment on whether shooting RAW influences how they set their exposures? Do you use the cameras' AE modes, or do you set the apertures and shutter speeds manually? And why? When shooting film or without RAW, do you set your exposures differently?
Title: RAW benifits/costs?
Post by: dlashier on November 26, 2006, 02:41:35 pm
Quote
Can the RAW shooters comment on whether shooting RAW influences how they set their exposures? Do you use the cameras' AE modes, or do you set the apertures and shutter speeds manually? And why? When shooting film or without RAW, do you set your exposures differently?
[a href=\"index.php?act=findpost&pid=87144\"][{POST_SNAPBACK}][/a]
A: no

B: manual, because it's more accurate and more reliable, and lets you judge the relative importance of parts of the scene yourself.

- DL
Title: RAW benifits/costs?
Post by: jani on November 26, 2006, 04:00:41 pm
Quote
Can the RAW shooters comment on whether shooting RAW influences how they set their exposures?
Since I know that I have a bit more latitude with highlights than with JPEG, raw can give me more detail in shadows, should the need arise.

I have a fairly good idea about what I can recover of seemingly blown highlights, and that I have a fairly good chance of pushing the image. It provides me with a bit more breathing space, so to speak.

So yes, having the option of shooting in raw mode may influence how I set exposure, but it depends on the shooting situation. Generally, I prefer not to, though, since it's also easy to misjudge the amount of latitude raw provides; the histogram and flashing highlights warning may not be sufficient indicators, and only experience can tell.

In this regard, I find it very similar to shooting with different film types.

Quote
Do you use the cameras' AE modes, or do you set the apertures and shutter speeds manually? And why?
I set my exposures depending on the situation.

Sometimes I use aperture priority, sometimes shutter priority, and other times I use manual. I may use program mode in some situations, for instance when someone else is borrowing my camera to take a picture of me.

I use aperture priority when I think it's more important to control depth of field than shutter speed. Typical circumstances include any photography of mostly stationary subjects, and I either use a tripod or have enough light that I know hand-held will do.

Shutter priority is for when I need a certain shutter speed either to capture motion or to reduce camera shake blur, and don't care about depth of field, just getting the shot.

Manual mode is both for when I want near absolute control of exposure, or when I need both a certain depth of field and aperture, such as shooting under difficult light conditions or when I use a flash.

Hand-held shots for street shooting, discreet family events, etc. would be typical for shutter priority or manual mode.

But this really doesn't have anything to do with shooting raw or not.
Title: RAW benifits/costs?
Post by: Jonathan Wienke on November 26, 2006, 05:19:32 pm
Quote
Can the RAW shooters comment on whether shooting RAW influences how they set their exposures? Do you use the cameras' AE modes, or do you set the apertures and shutter speeds manually? And why? When shooting film or without RAW, do you set your exposures differently?

I'll decrease exposure somehat when shooting JPEG since there is less highlight latitude. I use either manual or aperture priority whether shooting RAW or not; aperture priority when the lighting is changing a lot and manual is not practical (like partly cloudy days when the sun is going in and out of the clouds), and manual the rest of the time.
Title: RAW benifits/costs?
Post by: bjanes on November 26, 2006, 07:33:04 pm
Quote
In every summary recitation of the benefits of RAW 2 things are mentioned - WB adjustment and more headroom when making level/curve/shadow/highlight etc. etc. adjustments.  I was trying to get a sense of how the LR wb tool fit in the context of those 2 advantages.  I got the comment several days ago from a friend when I was discussing the benefits of RAW that since LR now had an explicit wb tool that can be applied to JPG, that that negated one of the 2 fundamental reasons to shoot raw over jpg. 

As far as I can tell so far, the LR wb tool is easier than doing it in native PS, but still falls considerably short of what you can do in RAW with a challenging file.
[a href=\"index.php?act=findpost&pid=86247\"][{POST_SNAPBACK}][/a]

WB is much easier in RAW than with an image rendered in a gamma 2.2 space since the WB adjustment for RAW is linear and merely requires multiplying each channel by a given WB factor. With gamma corrected data, the WB function is nonlinear. With RAW files you have more bits to work with (usually 12) than in the usual JPEG, which has only 8 bits. Drastic edits such as WB on 8 bit data are liable to posterization. Bruce Fraser discusses this on pages 11 and 12 of his ACR with PSCS2 book.

When doing WB in Lightroom, I would suspect that the results would be better with a 16 bit TIFF rather than an 8 bit JPEG.

Bill
Title: RAW benifits/costs?
Post by: PeterLange on November 27, 2006, 12:57:19 pm
Quote
WB is much easier in RAW than with an image rendered in a gamma 2.2 space since the WB adjustment for RAW is linear and merely requires multiplying each channel by a given WB factor. With gamma corrected data, the WB function is nonlinear.

Well, that’s what one would expect. Surprisingly, there’s a kind of commutative law in place regarding linear-scaling and matrix-to-matrix conversion (including different gamma). The sequence is exchangeable, because the scaling factor can be extracted from the exponential term, though it changes before vs after.

It’s in fact the common tone curve (brightening, S-shaped) - amplified by further hue & saturation tweaks - which disturbs color integrity and which makes proper white-balance of already Raw processed JPG’s so hard (see above). In this matter, conversion back to a linear space doesn’t help.

Peter

--
Title: RAW benifits/costs?
Post by: foobarred on November 28, 2006, 03:03:38 pm
To be honest, your concern about whether it makes people lazier probably makes the ability to shoot RAW similar to the effects of alcohol.

If you're naturally lazy to begin with, yes, it probably brings that out more since it's an enabler and allows you to be more lax in your photography technique.  If you tend not to be a lazy person, but rather a perfectionist, then no, it probably doesn't make you lazier.

Not that lazy is bad.  The pursuit of means to be lazier, when properly applied, can lead to efficiency gains.  This is a common characteristic of computer people who are really good at automating things via scripts et al.

Frankly, I'm more of the school of making sure I get it as close to right as possible and using the flexibility of RAW to bail me out when I mess up on what could have been a missed incredible opportunity.  I still shoot film and it makes no sense to get lazy habits that might transfer to when I shoot film and can't just easily bump the exposure up or down with a slider, or shift the WB with a click.

--foobarred