So the default gamma transformation will be used.ДЄnd the default gamma transformation is -g 2.222 4.5 ('BT.709'). So white level will be based on the histogram,

So thanks again.ДЎ) Any ideas why RawDigger would load images (with RGB render enabled) that look like my 'sRGBII conversion'? i.e. I had some time to look into this again today and things are starting to make sense, and I can convert between linear/gamma and colour spaces perfectly (for now anyway!). SRGB color space, 16 bit/channel output with no gamma transform and automatic white level What I think you are looking for in the last image would beДcraw.exe -v -w -H 0 -o 1 -q 3 -6 -g 1 1 -T -W And specifically, the last image does not have -g 1 1 as you might have expected, but a gamma gamma curve with exponent of 2.22 and toe slope 4.5, closer to sRGB than to linear. So actually, images 3 and 4 differ in two ways from the preceding one (white level and gamma). And the default gamma transformation is -g 2.222 4.5 ('BT.709'). But '-4' means '-6 -W -g 1 1', in other words, we no longer use -W, so white level will be based on the histogram, and no more -g option, so the default gamma transformation will be used. This looks almost the same as the second command, 'just' with -4 replaced by -6. And the whitepoint will be determined based on the histogram. Here's where things get interesting: now we specify a gamma transformation corresponding to the sRGB (-g 2.4 12.9).

Using the sRGB color space does NOT by itself apply a gamma transformation, and the -4 option implies -g 1 1 (so we stay in linear space) camera-specific), with 16 bits/channel (-6), fixed white level (-W) and no gamma transformation (-g 1 1)ДЄlmost the same, except that the image will be in the sRGB colour space (-o 1). Image will be in raw colour space (-o 0, i.e.

This equivalent to dcraw.exe -v -w -H 0 -o 0 -q 3 -6 -W -g 1 1 -T T : write converted image as TIFF with metadata I'll just list the conversions you used in the order they appear above, then say where I think something might have gone differently than you expect (or perhaps not)ДЇor those not familiar with dcraw, I'll explain all the options used: Here are my dcraw settings: NOTE: All saved out as sRGB JPEGs in NukeДcraw.exe -v -w -H 0 -o 1 -q 3 -g 2.4 12.9 -6 -TД¬an anyone suggest whether I'm going wrong somewhere? The files are pretty big, should I convert to Jpeg and upload?ДЄre you sure your conversions do exactly what you think they are doing? The thing I'm not sure about is with regards to my sRGB conversion(s), I would expect to be able to linearize these and they match my linear images but they don't, they are much brighter - and I say 'they' because I've tried a couple of different options. Although I'm wondering if it's more complex than I first imagined? There's a clear difference in vibrancy but I'm pretty happy that is because of using sRGB primaries and the other not. I'm using Nuke as it works in linear space but displays all inputs in sRGB space, you just tell each input node what colour space the incoming image is.ДЄnyway I'm trying to verify that I'm able to acquire images with the following conversions:ДЄnd I want to open in Nuke to compare, linearize/gamma/convert to ensure I have used the corerect settings and understand what I'm working with.Д¬onversions 1) and 2) look (in non technical terms) the same in terms of exposure/contrast (viewed in sRGB gamma space). I have been experimenting with different dcraw conversions and am comparing the results in Nuke. Wondering if someone can shed some light on what dcraw is doing to my CR2 files. I've been browsing these forums for a while.

Rawdigger highlight analysis