fredmiranda.com
Login

Moderated by: Fred Miranda
  New fredmiranda.com Mobile Site
  New Feature: SMS Notification alert
  New Feature: Buy & Sell Watchlist
  

FM Forums | Leica & Alternative Gear | Join Upload & Sell

1       2       3       4              end
  

Archive 2010 · New article - Why shoot RAW - The real answer

  
 
TonyBeach
Offline
• • •
Upload & Sell: Off
p.5 #1 · New article - Why shoot RAW - The real answer


mawz wrote:
Umm, no. Uni-WB does absolutely nothing to affect how RAW converters handle WB gain and may seriously screw with the default conversions if the RAW converter is using the camera's WB settings by default.

[Snipped.]

Since WB in the RAW file is merely metadata, the RAW file from a Uni-WB shot and a standard WB shot using the same exposure settings will produce the same final result.


Do some testing (as I've done) and you may see what is going on. Minimizing changes to WB from a neutral setting minimizes issues that do crop up when making changes to WB settings in some RAW converters. Here's a test for you, shoot a CC24 colorchecker at 10000K, 2500K and using uni-WB under sunlight and incandescent lighting, and shoot it so that the 10000K blows a channel; then see if you can restore that blown channel in the 10000K file with NX. Oh right, you can't do that because you don't use NX, but you seem to think you are qualified to pontificate on how every RAW converter interprets WB.

Using a CC30M filter to tame the green channel will have an actual effect in the RAW converter, but at the cost of causing WB problems since you are mucking with the Bayer demosaicing algorithm's basic assumptions. The green channel is stronger for a reason, because the human eye is far more sensitive to green. It's not a very good idea to use a CC30M if you want anything resembling accurate colour.

Obviously you haven't done it; because if you had, you would know better (as I do).



Feb 09, 2010 at 11:35 PM
theSuede
Offline
• • • •
Upload & Sell: Off
p.5 #2 · New article - Why shoot RAW - The real answer


There are more people than me working on/with de-mosaic algorithms presently on this board, and I doubt any one of them will contradict me when I say that as the signal is in linear format (no gamma has been applied) there will be NO difference whatsoever in a CC030-filtered signal compared to a non-filtered signal when you check the large-scale end result after interpolation - except for a slight colour-shift effect. The "assumptions" made in a de-mosaic interpolator are all based on inter-channel ratios/sums, and those are kept almost exactly the same - filtered or not - as long as no channels are clipped. Increasing R/B channel SNR (by increasing their relative signal strength) improves the demosaic accuracy, improving shadow colour accuracy and mid-high-tone detail estimation accuracy.

The main reason for a CC030 messing up your colour is not WB, but that it changes the relative response slopes of the built-in CFA, so you need a different correction profile in your raw-converter. The attenuation of green will shift some hues, this effect is strongest at the midpoint between G-R and G-B (yellow and greenish blue repectively). It will shift those points a small bit in towards pure green. A filter as strong as the 030 might make a change strong enough that your regular profile (or in-camera jpg) will give a noticeable with/without difference.
All of this happens AFTER de-mosaic, in the colour correction profile. The difference is smaller than that between two cameras of different make/models - so I would definitely not say that it makes a crucial difference to "accurate colour".



Feb 09, 2010 at 11:43 PM
mawz
Offline
• • • • • •
Upload & Sell: Off
p.5 #3 · New article - Why shoot RAW - The real answer




But you're assuming here that I'm going to blow the channel when not using Uni-WB. If I'm using a meter and not the histogram to check exposure, I'm not going to blow that channel in the first place. So ni-WB doesn't save anything.

Note it's sort of hard for me to do any conversions in NX these days, I don't shoot Nikon anymore. But I am familiar with NX, given that it was my converter of choice for the D300 and I've done a LOT of conversions in it. I'm also aware that it does tend to handle the preset WB
...Show more

And you're assuming you know better when your solution breaks both the colour balance assumptions of the RAW converter and of the base colour interpolation algorithm. What you're doing is breaking the green channel in order to rescue highlights in the red and blue channels. It might work in some cases, but it will definitely cause problems in others.

Here's a hint, if taming the green channel didn't have significant downsides, we wouldn't be seeing the current bayer mosaic pattern (or Sony's 2-green variation).



Feb 09, 2010 at 11:49 PM
TonyBeach
Offline
• • •
Upload & Sell: Off
p.5 #4 · New article - Why shoot RAW - The real answer


TonyBeach wrote:
Do some testing (as I've done) and you may see what is going on. Minimizing changes to WB from a neutral setting minimizes issues that do crop up when making changes to WB settings in some RAW converters. Here's a test for you, shoot a CC24 colorchecker at 10000K, 2500K and using uni-WB under sunlight and incandescent lighting, and shoot it so that the 10000K blows a channel; then see if you can restore that blown channel in the 10000K file with NX. Oh right, you can't do that because you don't use NX, but you seem to think you
...Show more

mawz wrote:
But you're assuming here that I'm going to blow the channel when not using Uni-WB. If I'm using a meter and not the histogram to check exposure, I'm not going to blow that channel in the first place. So ni-WB doesn't save anything.


No, I'm assuming that you want to utilize ETTR, and understand that just because a channel is blown by the WB setting, it isn't actually blown (if you are shooting RAW and not JPEG, which was the original point of this thread).

mawz wrote:
Note it's sort of hard for me to do any conversions in NX these days, I don't shoot Nikon anymore. But I am familiar with NX, given that it was my converter of choice for the D300 and I've done a LOT of conversions in it. I'm also aware that it does tend to handle the preset WB somewhat problematically.


Then you agree that there is a problem that occurs with some RAW converters.

mawz wrote:
Of course I could just load that 10000k file into CaptureOne and rescue the channel just fine that way. No Uni-WB needed.


As much as I like Capture One, sometimes I find myself using ACR or NX. Nonetheless, the more important issue for me is actually being able to see how well exposed my shot is, something that is easier and quicker to do with uni-WB than with any other method (and you've not actually offered any here).

mawz wrote:
You're generalizing one specific implementation to a general superiority of Uni-WB. Now you MIGHT have a point if you specifically state that if you use a supported Nikon body and CaptureNX, then UniWB has some value. But this is the first time you've ever specified a RAW converter. Note my point has ALWAYS been that Uni-WB's value is entirely implementation-specific.


Well, I pointed out in my first reply to you on this that, "RAW converters can do funny things when applying WB gain." I didn't say all RAW converters, and I didn't say it always happens (it never happens with Capture One for instance). That said though, the issue can subtly degrade image quality under some circumstances, and downright ruin it as far as using a preferred RAW converter is concerned in some circumstances.


mawz wrote:
Using a CC30M filter to tame the green channel will have an actual effect in the RAW converter, but at the cost of causing WB problems since you are mucking with the Bayer demosaicing algorithm's basic assumptions. The green channel is stronger for a reason, because the human eye is far more sensitive to green. It's not a very good idea to use a CC30M if you want anything resembling accurate colour.



TonyBeach wrote:
Obviously you haven't done it; because if you had, you would know better (as I do).


mawz wrote:
And you're assuming you know better when your solution breaks both the colour balance assumptions of the RAW converter and of the base colour interpolation algorithm. What you're doing is breaking the green channel in order to rescue highlights in the red and blue channels. It might work in some cases, but it will definitely cause problems in others.

Here's a hint, if taming the green channel didn't have significant downsides, we wouldn't be seeing the current bayer mosaic pattern (or Sony's 2-green variation).


You are clearly confused about what happens when you use a CC filter. There are still two green photosites for each red and each blue photosite; the difference in sensitivity is because less light arrives at each red and blue photosite because those photosites require more filtration than the green photosites require. The only thing that changes when the green light is reduced with a color correction filter is that less WB gain is required to attain a balanced color. In effect, applying a 25% gain to the blue channel and a 40% gain to the red channel (those are typical gains applied under daylight conditions) is the same as boosting the ISO in those channels.

If color correction filters were such a bad idea, than Iliah Borg would not be using them. Iliah is a color guru who uses many systems and writes code for a couple of different RAW converters. I'm sure Iliah agrees with what Joakim (aka, theSuede) wrote above.

If uni-WB was deleterious to demosiacing performed by RAW converters, then Thom Hogan wouldn't use uni-WB, but Thom Hogan does use uni-WB, as does Iliah Borg.



Feb 10, 2010 at 01:14 AM
Bifurcator
Offline
• • • • •
Upload & Sell: Off
p.5 #5 · New article - Why shoot RAW - The real answer


theSuede wrote:
Bifurcator - Now that's STILL one more definition - is this "measurement resolution related" or "signal quality related"? :-)
...But I actually meant "range" - as in "signal quality related minimum step count". This resolution has very little to do with how many bits/steps you quantize your measurement with (as long as you use a quantization step small enough - 12 bits or more). This value wouldn't change if you used 16, 18, 20 or 24bit ADC's... It is defined by the amount of minimum signal change steps you can fit in between the lower (noise floor) and upper (clipping) boundary
...Show more

True. I was defining the virtual container, not the contents nor the I/O devices. It that regard we're most commonly dealing with an R,G,B axial cube space with an exact number of steps 256 (8bit), 4096 (12bit), 65536 (16bit) per channel (cube for the total number of colors). It is simplest and most useful to primarily consider this model alone in general conversation concerning file formats - which is (was) the topic here. We can express these divisions in floating point numbers or percentages as well but now we're rummaging around inside the box-space and are not longer talking about the defined box itself. Floats and percentages are useful for calculations independent of the box but not for describing the container - the box itself. In any of these formats the intensity range is fixed. It is said to be non-dynamic - because we defining the box and not the contents. With high dynamic range images (HDRI), floating point numbers are used to describe values in above and below displayable "100% white" and "100% black". But we're still talking about resolution - typically 32 bits of accuracy are used to resolve the color space of HDR Images. In the case of HDR the box is expanded dimensionally while all other formats being discussed are described within the same sized box - just in different degrees of accuracy (resolution). Of course the contents of all of these boxes are dynamic within the given box's defined dimensions - the range. Given an 8 bit per channel color model, I can independently multiply a red channel intensity level of 1 (almost black by anyone's eyes) by the value 1.01 in software but it will be resolved to a value of 1 within the file space (box) definitions.

Thus when discussing file formats (as opposed to data generation and manipulation) either disk based or in memory, KISS applies and I've found that bringing the properties of the input and output devices into the discussion only serves to confuse matters.



Feb 10, 2010 at 03:27 AM
mawz
Offline
• • • • • •
Upload & Sell: Off
p.5 #6 · New article - Why shoot RAW - The real answer


theSuede wrote:
There are more people than me working on/with de-mosaic algorithms presently on this board, and I doubt any one of them will contradict me when I say that as the signal is in linear format (no gamma has been applied) there will be NO difference whatsoever in a CC030-filtered signal compared to a non-filtered signal when you check the large-scale end result after interpolation - except for a slight colour-shift effect. The "assumptions" made in a de-mosaic interpolator are all based on inter-channel ratios/sums, and those are kept almost exactly the same - filtered or not - as long as
...Show more

I stand corrected, I would have expected a larger colour shift from the CC30M, and more significantly so than the boost in the R/B channels.

Note I was referring to a colour shift being the problem with the CC30M.



Feb 10, 2010 at 09:23 AM
theSuede
Offline
• • • •
Upload & Sell: Off
p.5 #7 · New article - Why shoot RAW - The real answer


Just as you say, KISS is good. And the definition of a signal can't get any simpler than the definition of its' DR, and the actually reality-relevant usable signal resolution contained in this DR. :-)
-And both of these can be inferred from the SNR/signal level curve - Which in a way is the base for all signal definition.

HDR is another thing, and manipulation flexibility yet another.

RAW keeps the base information quality in a firm grip, and for the picture information things can only get worse from here (unless you count upsampling and FP-conversion to improve manipulation accuracy - which is not a part of "base information quality").

JPG makes a lot regarding the camera/picture handling a lot easier/more compact, and it does indeed have enough signal quality lattitude for smaller manipulations - as long as base exposure, WB and compression settings are "good enough".

The main losses with jpg as I see it is WB adjustment, highlight range resolution and the re-compression of material that has already once been lossily compressed. A 10-bit jpg XR in ProPhoto would remove those boundaries (except for the fact that it is a Seriously Bad Idea to try and adjust WB in gamma-corrected, already profile-converted RGB files...)



Feb 10, 2010 at 09:38 AM
theSuede
Offline
• • • •
Upload & Sell: Off
p.5 #8 · New article - Why shoot RAW - The real answer


maws; no worries. It's a highly "un-necessary" piece of trivia. The effects are there though, as you say. So you are correct in essence but not in cause - which makes the method kind of redundant for people not anal enough to worry about a 0.5Ev increase in shadow resolution... :-) The noise-decrease "gain" is somewhat negated by the colour accuracy "loss" unless your camera profile is adjusted for the change.

I must add that I have used both FLD and CC030/020 filters for landscape shots on windy days when multi-exposures/stacking or stitching wasn't possible. It DOES make a positive difference when trying to get the last iota of detail from your scenery shot.

And then you have three hells and a violent fit trying to get the detail to print... :-)



Feb 10, 2010 at 09:48 AM
erichard
Offline
• • •
Upload & Sell: Off
p.5 #9 · New article - Why shoot RAW - The real answer


This DR, bit depth discussion is above my pay grade, but my lay interpretation is that by definition, what some here are calling DR goes from 0% to 100%, and 0% is the same for everyone, and 100% is the same for everyone, because the darkest dark is theoretic absolute black, and the whitest white is a theoretic whitest white. The output might vary according to your printer and screen, but, however dark your screen could get, that would be 0, and however white your paper or screen can get, that would be 255 (or whatever with respect to bit depth). That is just a mathematical assumption to me. If one takes that point of view, DR is not a very useful concept.

If you tweak that definition just a tad, and say that the useful definition is really not the difference between the minimum of 0 and maximum of 100%, but rather one increment away from those numbers, it becomes a useful notion. So 8 bit can record useful info from 1 to 254 before it begins to clip out. In 12 bit, you can have useful info from 1 to 4094 before you clip out in each channel. 4095=255 in brightness on your screen or paper, but 1 to 4094 is a heck of a lot more useful dynamic range than 1 to 254 (***ie. it is both wider, and more incremental in gradations***), those being the limits just before you start to clip white or black (or various color channels).

As some were saying, the bit depth definitely allows recovery of seemingly blown channels (look very bright or dark) because they haven't truly blown out yet as they still have many increments left before clipping (eg 12 or 16 bit photos). While of course some data is accurate at 255 or 4095, this value is where clipping starts on the high end. If you have data at 254 or 4094, you know it's useful info and not clipped (whereas one increment higher you are not certain), so I think the useful definition for DR has to include the difference between the low and high, less one increment on either extreme (plus one on the low end).

Just keep in mind, your paper does not get whiter, nor your screen brighter at 4095 vs 255, nor any other number you come up with at the high end of bit depth. Absolute white remains the same. BUT, 4094 is without question brighter than 254, and 1 on the 12 bit scale is definitely darker than 1 in the 8 bit scale. I do not understand how you get more staircases out of the situation, but I do understand getting more stairs.



Feb 10, 2010 at 11:18 AM
theSuede
Offline
• • • •
Upload & Sell: Off
p.5 #10 · New article - Why shoot RAW - The real answer


You get 255 steps from putting 256 discrete points on the value vector... 253 in the middle that has strictly defined upper and lower boundaries - and then two more at the end-points with only one boundary. One of them will mean [brighter than 254] and one will mean [darker than 1].

In the shadow part of the usable range, 8-bit gamma 2.2 (sRGB or ARGB) actually has almost exactly half the resolution of a 14-bit linear scale - not 64x less resolution as the bit-numbers would imply... But when you get up into the brighter portions of the image the steps are spread out so that the resolution in the top end is about 140 14-bit values per step.

In 14-bit equivalents, an 8-bit gamma2.2 series start with:
0,2,4,6,8,10,12,14,16,,,,,,
and ends with:
,,,,,15410,15547,15685,15823,15962,16102,16242,16383

That mapping covers one thousand 14-bit linear steps in the last eight steps of the gamma-corrected 8-bit word. This is one of the reasons why jpg's have trouble with posterization of colour when you approach signal saturation (white).


I'd like to see the industry really adapting to the jpeg XR standard - then a ProPhotoRGB (gamma 1.8) 10-bit jpg-XR out of camera would have better signal resolution than the raw file can provide.... And that in the same file-weight as the standard jpg has today.



Feb 10, 2010 at 08:00 PM
Bifurcator
Offline
• • • • •
Upload & Sell: Off
p.5 #11 · New article - Why shoot RAW - The real answer


Umm, I may not be understanding you two correctly but non-dynamic file formats are indeed non-dynamic. It is NOT 256 discrete steps of any shade you want. For example from 40% pure red to 60% pure red there are approximately 50 steps of resolution given a normal JPEG or etc. You can not express that range in 256 steps. The data will remain in the center and the higher/lower values will remain unused. You could then take it to 16 bit per channel color and interpolate it into 13,100 steps if you have the tools but it will still even then remain only the centermost 20% of the total (pure red) range. In this way we have changed the resolution of the color spread but the range remains the same. These are non-dynamic range file formats.

The reason there is still "room" in a JPEG that seems blown out is because we are remapping some higher tonal ranges to lower ones (in the case of clouds for example). We are thereby increasing the contrast between 255,255,255 and 254,254,254 for example. We edit the data and the pixel values that were 254.254.254 become 242.242.242 or whatever - (remapping). When there are no pixel values at all in the range we're interested in remapping (say, between 254 and 230) then we say it is truly blown out and unrecoverable. In such a case there are no pixel values in the range we need, available to remap. This is a software operation done to the data tho and not to do with the ranges and resolutions of file formats - (other than that there is a greater likelihood for pixel values to exist in the range(s) we need, and a finer control over them, in higher bit acquisition file formats, etc.). It does have something to do with what our monitors and our eyes are capable of though.

How useful is it? I dunno, you use it everyday. How useful is it to you? Are we past due for better standard file formats? Yes, we certainly are! Way past! I think we should have seen a change around 2000 but we never did. The formats were developed and released but never made it into wide use as an accepted standard like GIF and JPEG. Jpeg XR would certainly be an improvement! As I understand it Jpeg XR is a 16 bit IFD layered format that has native support for both 4-color (CYMK) and 3-color (RGB) color models with lossless colorspace transformation and it's compression can be optionally either lossy or lossless. So it has most of the things I typically need. I hear there's a 4GB file size limit though and if that's not addressed that may kill it for some of us.

theSuede,
Lastly, are signal descriptions requiring a least algebra and Fourier transform to understand and discuss, really simpler for you to explain to FM users than container arrays needing mostly only addition and subtraction to understand and discuss? I know you're one of the smartest guys here but...




Feb 11, 2010 at 02:24 AM
theSuede
Offline
• • • •
Upload & Sell: Off
p.5 #12 · New article - Why shoot RAW - The real answer


The gamma-conversion you do when raw-converting to sRGB or Adobe RGB jpg gives:

One value-step in a jpg in the darkest areas of the picture equals roughly two steps in the raw.
One value-step in the brightest areas of the picture equals roughly 140 steps in the raw.
-If the raw is 14-bit...

The effects that this has isn't really that simple to grasp, as light is roughly Ev-based in most photographers' mindset.



Feb 11, 2010 at 01:41 PM
EricBSTL
Offline

Upload & Sell: Off
p.5 #13 · New article - Why shoot RAW - The real answer


Wow...this a lot of debate over file choices. Certainly each type has it's place. When I'm shooting a wedding for instance, I shoot RAW because you only get so many chances to capture a kiss, the rings, etc. And, if I got a good shot that was poorly exposed or balanced, RAW files give me the most options for correcting in post.

On the other hand, when I shoot poker tournaments which are thousands of shots with multiple chances of getting it right, I shoot jpeg...simply because there is little to no post work that will take place, and poor shots are just dropped. No need to bog the work flow down with conversions...etc.

Just how I do it....no rule to live by or anything implied...



Feb 11, 2010 at 03:03 PM
theSuede
Offline
• • • •
Upload & Sell: Off
p.5 #14 · New article - Why shoot RAW - The real answer


"Use what works for the situation" is one of the implied meanings to your above sentence as I read it - and for me that seems like a very good rule to live by... :-)


Feb 11, 2010 at 05:06 PM
1       2       3       4              end




FM Forums | Leica & Alternative Gear | Join Upload & Sell

1       2       3       4              end
    
 

Welcome back
Log in to your account