Red Highlights

[Colin]

Daniel,


Colin, Each RAW converter will render the RAW data slightly different from one another. I'll let Daniel do the in-depth. The originals are for anyone who wants to check the gradients up close and personal. If you really want to see something wild, develop this CR2 with ACR 4.4 or higher along with the Canon camera profiles. Standard, Faithful, Neutral, Landscape, etc. The outputs are miles apart when pushing a red gamut this hard. sRGB is as good as all the other color spaces when developing for the web.


That's why I'm curious as to which output renders the most true. I'd like to think that SilkyPix does. At least for me, 90% of the time it's really faithful at rendering accurate color output.
<div style="CLEAR: both"]</div>

My only experience in rendering raw data is with DPP and Adobe Lightroom.


According to the Canon descriptions, Faithful is the only rendering option that is accurate. Neutral is compressed in color space to minimize clipping and expects generous post-processing. Everything else is a stock enhancement preset. I played with lightroom for awhile, but while I subjectively liked a few renderings better in their effect, I couldn't get images that looked much like the 'Faithful' initial settings on DPP.


Something, though, bothers me. While I'm all for tweaking images for the best representation of what we want to present, if different software takes the same data and, by default, presents a drastically different image in the same color space, then, technically speaking, I would think that means that they can't all be right, i.e., most, if not all of them, are wrong.


I think I'll put these more advanced raw rending methods on my long term wish list, along with Photoshop and more sophisticated noise reduction software. Need more time for this.... [:P]

[Daniel Browning]

Ah, so are you saying that, in terms of dynamic range and detail, it's generally better to overexpose and then dial back in the raw conversion?

Yes. When most folks do "ETTR", they don't realize that they are only doing ETTR for the JPEG on their camera, which is easily two stops off from the raw data (as in this case).

For web display, i'd assume that we'd be looking at sRGB or what have you.

Correct.

If that's the case, shouldn't all of these images look similar?

As Chuck said, the differences are due to different converters and different settings. Colors that can't be displayed in sRGB (such as the true saturated red of this flower captured by the raw file) can still be *mapped* to a similar color in sRGB. (Just as you can't take a picture of the sun and print it on paper that is bright enough to blind people: you have to "map" the brightness of the sun to a lower brightness on the paper because the paper just isn't capable of reproducing the natural world.)

Thanks for the pat. I did learn something today. I was glad I waited until I got home to look at some things before I posted. I was amazed to see those images on my new HP monitor. Obviously, we're all not seeing the same thing when it comes to high gamut renderings like these red flowers.

Yes, cheaper monitors and laptops (like my Macbook Pro) do an especially poor job. I'm using a NEC 2490WUXi, which has very good reproduction of sRGB.

On my HP2275w there is no visible clipping that I can see in the OP's image.

Pull it into photoshop and isolate the red channel to see the clipping. There are many areas with no detail (253+). The blue and green channels are fine, which is why we can still see some detail in those areas.

Of course, most monitors will show even more of it as blown (including blue and green channels) even though it isn't.

sRGB is as good as all the other color spaces when developing for the web.

I would add that most computers/browsers aren't color aware and so cannot deal with anything other than sRGB. But it would be possible to upload a 16-bit tiff that has a color space with a very wide gamut (e.g. BetaRGB) so that nothing was clipped in the image *file*. But to view it, the display has to convert it to sRGB anyway, and so it will get clipped. So unless it will be printed, it's better to do a quality conversion to sRGB (and avoid clipped colors) during raw conversion.

Daniel,

http://photography-on-the.net/forum/...d.php?t=485349

Is there any validity to this one. Like that poster, I'm lazy too.

Yes. Those instructions will often get your Uni-WB within 1/3 stop, which is close enough for most folks. The best method takes a little more work, but you only have to do it once in the life of the camera:

http://www.dpreview.com/forums/read....ssage=31582853

One of these days I'm going to try to build a Custom Picture Profile that does a reverse sRGB curve like so:

http://www.dpreview.com/forums/read....ssage=31842306

That would allow the histogram to be linear instead of gamma, which is much easier to see and use.

If your taking about the green cast white balance for accurate raw histograms,

Yes, that's precisely it.

I tried, but just couldn't get use to it.

The way I do it is to switch back and forth, because color is obviously an important part of composition.

The biggest thing that I keep messing up on is forgetting to shoot a white/gray card at the beginning of session.

Just make sure all your subjects wear something white. ("I hereby award you this commemorative white ribbon in honor of UniWB Awareness Day.")

We would all have a better idea of what color those red flowers really are!!

Indeed. One of those mysteries that keeps our interest. ("Were those skies really that purple? Or was it just Velvia film? We'll never know.")

Something, though, bothers me. While I'm all for tweaking images for the best representation of what we want to present, if different software takes the same data and, by default, presents a drastically different image in the same color space, then, technically speaking, I would think that means that they can't all be right, i.e., most, if not all of them, are wrong.

That's certainly a valid way to look at it. Technically, they're all wrong. All that matters is the one that gets in wrong in the most pleasing way.

[Chuck Lee]

Colin,


I personally like SilkyPix. I started using it when I shot Pentax.I'm use to it and can get alot out of my photos. Most of the time I can pull around 1 to 2 ev out of blown highlight land. I don't shoot for that, but can use it if it's there. I find most photographers that shoot in raw find a particular program they like andworks for them.Raw rendering color accuracy is a subjective game that requires a bit of practice with ones chosen program. Once a confidence level is reached, it is very hard to switch to something else. Look at Bryan's photos. His color is as consistent across all images as any photographer I've ever seen. It is more than obvious that he knows "his" workflow. Whether, raw or in-camera, if you know what the output is going to look like based on the control variables you can get repeatable results and feel confident with what you are doing. Heck, just try shooting the same scene in JPEGusing the in camera scene modifiers; Standard, Faithful, Landscape, etc. and you will see all the variationthat the built-in raw processor can offer. Which one of those is right?


So, Take your time.......it's alot to digest.


Later...

[Dumien]

SilkyPix Development Studio Ver 3.0.25.1 - Default Settings

This one looks kind of purple on my monitor, or not really red, whatever color that may be.

ACR 4.4 with ACR4.4 selected as the camera profile. Default Settings

This one is the one I prefer, it's very nice, thanks

Picasa from Google - Go figure, I like the way it rendered the 450D RAW!

As much as I think it's weird that PIcasa did something like that, I think it's pretty good, but not as good as the ACR one...





still, my monitor sucks, i guess ... lol


thanks again,


Andy

[Chuck Lee]

Yea, I had a sneaky suspicion ACR was the one. I sort of expected that after seeing the Picasa version. Your right, the SilkyPix default was heavy on the magenta. The first thing I would have done was back that off. SP has a tendency to use a fairly heavy color deflection when dealing with Canon raws. It is usally toward the magenta side. But, that's OK, I think I would have gotten it close just processing it the way I do most of my shots. I am always curious to know how the "default" renders. I forgot to add that Irfanview can also be used to convert CR2 files for those that like free stuff.


I didn't know what I was missing until I bought the HP2275w. Unfortunately, it's defaults are way over the top and it needed to be adjusted. That's a whole other story. I'm sorry you have a "sucky" monitor. If you decide to upgrade, do good research. The LCD stuff today is very tricky.


Thanks Andy, Great thread!


Daniel,


I had a "Duh!!" at 7:00AM today. The 2.3 ev headroom you were taking about was extra usable space in the raw histogram. No data was there, so there wasn't any reason to see clipped red highlights. Got it!! That's why I commented to Colin about pulling down 1-2 EV of blown highlight data when using RAW. It all came together with that first cup of coffee. Sorry bout that Daniel. I'm denser some days than others.


Chuck