DR testing results

the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago.
If your assertion is that the in-camera histogram is the same as the raw histogram, that is easily disproven.
  1. Put the camera on a tripod, set the white balance to 3200K.
  2. Observe the histogram.
  3. Now set the WB to 8000 K.
  4. Observe that the histogram is different.
  5. Examine raw files made with the two WB settings.
  6. The raw data is the same.
  7. QED.
Have you forgotten the discussion on DPRevived with A74Me a couple of years ago? Your demonstration there of your Hassy's WB-related histogram behavior and my Oly EM1iii red flower shot histogram demonstration held no sway over A74Me. His Sony A6300 live histogram proved it's all just a "myth"...

I fear we are beyond not even wrong. We are now deep into not even not even wrong! territory... ;-)
I even posted a extreme macro shot of the rear lcd down to pixel level, also a fast raw viewer highlight and shadow clipping image. But the discussion is about the 6 stop variation DR test results not the .3 stop margin of error both ACR and Fast Raw Viewer have built in 😊
 
46080bc0954a4595b1ee4e78301d53d3.jpg

6df2400da5244ffdb916cf53fbe268e1.jpg
I've just found that motorbike picture in the review and I don't think we published the Raw file. Are you trying to assess DR from JPEGs?

Because, as I say, most standard JPEGs use tone curves to convey about 8.5 or so EV of dynamic range, discarding everything beyond that.

Trying to assess DR by pushing JPEGs is like smashing sets of crockery and trying to guess how maleable the clay they were made from was, before they were fired.

Richard - DPReview.com
the histograms are near identical from a pushed gfx100 raw file vers jpeg, im wanting to see the extra 6 stops of DR demonstrated. to be honest id take the d30 jpeg over the raw gfx 100 file till someone can clearly show 6 stops difference when it starts behind from the start 🤔
Is that image one that contains 6 additional stops of DR? How are we to tell?

What is your Raw converter of choice doing to the shadows? How would we know?

Presenting out-of-context screengrabs isn't a convincing way to disprove all existing theory and testing, especially if your reference point is a JPEG, which can't act as a meaningful point of comparison. Even more so when the first images you posted strongly suggested the GFX was capable of showing more dynamic range than the D30 (less noisy darkest tones).

If you download the Raw from this scene:

https://www.dpreview.com/reviews/fujifilm-gfx-50r-review/5#sbs

The brightest tones are at or very close to clipping and the darkest are around 13-14 stops below that. (ie: Raw values around 2 in the shadows and approaching 16813 in the highlights).

You can process that to have nothing rendered as quite black, and get a histogram with everything neatly showing in the middle of the graph, but that doesn't tell us anything. It certainly doesn't prove or disprove how much DR was captured.

Richard - DPReview.com
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
 
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.

DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.

We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.

Richard - DPReview.com
 
the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago.
If your assertion is that the in-camera histogram is the same as the raw histogram, that is easily disproven.
  1. Put the camera on a tripod, set the white balance to 3200K.
  2. Observe the histogram.
  3. Now set the WB to 8000 K.
  4. Observe that the histogram is different.
  5. Examine raw files made with the two WB settings.
  6. The raw data is the same.
  7. QED.
Two back of camera luminance histograms with different WB settings in the camera. No other setting were changed.

1e2351c0bbe14cbdacd5c902872031c2.jpg

Notice how much closer to the right side the lower histogram is.
Notice how much closer to the right side the lower histogram is.

In order to prove that the in-camera histogram doesn't represent the raw histogram, all that's necessary to prove is that WB settings in the camera affect the in-camera histogram, since the two shots above can't possibly represent the raw file data, unless someone is going to claim that the raw data (not the metadata) is affected by in-camera WB settings. Is anyone going to assert that?

--
https://blog.kasson.com
 
Last edited:
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.
i know that i was questioning the difference of cameras in general of that era as dxo didnt do a test of the d30. ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
Richard - DPReview.com
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
 
the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago.
If your assertion is that the in-camera histogram is the same as the raw histogram, that is easily disproven.
  1. Put the camera on a tripod, set the white balance to 3200K.
  2. Observe the histogram.
  3. Now set the WB to 8000 K.
  4. Observe that the histogram is different.
  5. Examine raw files made with the two WB settings.
  6. The raw data is the same.
  7. QED.
Two back of camera luminance histograms with different WB settings in the camera. No other setting were changed.

1e2351c0bbe14cbdacd5c902872031c2.jpg

Notice how much closer to the right side the lower histogram is.
Notice how much closer to the right side the lower histogram is.

In order to prove that the in-camera histogram doesn't represent the raw histogram, all that's necessary to prove is that WB settings in the camera affect the in-camera histogram, since the two shots above can't possibly represent the raw file data, unless someone is going to claim that the raw data (not the metadata) is affected by in-camera WB settings. Is anyone going to assert that?
can you post an incamera rgb histogram instead like on the sony. i will test now.
 
the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago.
If your assertion is that the in-camera histogram is the same as the raw histogram, that is easily disproven.
  1. Put the camera on a tripod, set the white balance to 3200K.
  2. Observe the histogram.
  3. Now set the WB to 8000 K.
  4. Observe that the histogram is different.
  5. Examine raw files made with the two WB settings.
  6. The raw data is the same.
  7. QED.
Two back of camera luminance histograms with different WB settings in the camera. No other setting were changed.

1e2351c0bbe14cbdacd5c902872031c2.jpg

Notice how much closer to the right side the lower histogram is.
Notice how much closer to the right side the lower histogram is.

In order to prove that the in-camera histogram doesn't represent the raw histogram, all that's necessary to prove is that WB settings in the camera affect the in-camera histogram, since the two shots above can't possibly represent the raw file data, unless someone is going to claim that the raw data (not the metadata) is affected by in-camera WB settings. Is anyone going to assert that?
im saying that the incamera histogram/zebras (sony set to 109 + #) can represent an acurate exposure based on the raw file opened in either ACR or fast raw viewer. a raw file has no colours, the sensor just reads voltages/charge. what does a black and white sensor conversion histogram represent 🤔
 
Last edited:
the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago.
If your assertion is that the in-camera histogram is the same as the raw histogram, that is easily disproven.
  1. Put the camera on a tripod, set the white balance to 3200K.
  2. Observe the histogram.
  3. Now set the WB to 8000 K.
  4. Observe that the histogram is different.
  5. Examine raw files made with the two WB settings.
  6. The raw data is the same.
  7. QED.
Two back of camera luminance histograms with different WB settings in the camera. No other setting were changed.

1e2351c0bbe14cbdacd5c902872031c2.jpg

Notice how much closer to the right side the lower histogram is.
Notice how much closer to the right side the lower histogram is.

In order to prove that the in-camera histogram doesn't represent the raw histogram, all that's necessary to prove is that WB settings in the camera affect the in-camera histogram, since the two shots above can't possibly represent the raw file data, unless someone is going to claim that the raw data (not the metadata) is affected by in-camera WB settings. Is anyone going to assert that?
can you post an incamera rgb histogram instead like on the sony. i will test now.
Those are in-camera histograms, from the live histogram on a GFX 100 II. The RGB ones are also different from each other when you change the WB. But I wanted to keep it simple. If the luminance histograms are different, the RGB ones can't be the same.

--
 
ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
I don't know what you're trying to describe here. If you're talking about the point at which a grey card appears as white and black in JPEGs with different exposures, then you're characterising your JPEG engine, not measuring dynamic range.
The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
That's not the same as proving that histograms are based on Raw output. You can get the histograms on a Sony to more closely match the Raw clipping point by using the HLG profile, but this is a fortuitous 'hack,' rather than an expected consequence. It's still prone to the WB problem that's been highlighted elsewhere. But that's still a tangential point.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
You have posted a series of images with no adequate explanation of what they're showing or, really, what you think you're seeing in them. As I say, the overexposed Kodak charts appear to show the Fujifilm has more dynamic range (less noise at the darkest tone), but there's nothing to show us deep shadows.

Beyond that you've posted a processed JPEG, which can't tell us anything useful about sensor DR and a supposed Raw conversion that you say shows less DR because its histogram fits within clipping. Again it's so unclear what you think this demonstrates that it's impossible to sensibly respond to.

I provided a link to an image with DR of around 13EV. I can squash that all into the histogram of a JPEG if I wanted to: it wouldn't tell me anything useful and it wouldn't mean the original shot had less DR than I'd measured.

No one has responded to your claims because it's not clear what you think you're showing.
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
At the point you're testing highlight recovery algorithms, you're not really talking about sensor DR anymore.

Richard - DPReview.com
 
As you have demonstrated, the Canon D30 has underrated DR performance and can keep up with much more modern and expensive cameras. Unfortunately the D30 uses a CMOS sensor, which eliminates it from contention because CCD sensors have superior cinematic colors especially in tricky lighting situations. This is why I still shoot a Nikon D40.
 
Last edited:
the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago.
If your assertion is that the in-camera histogram is the same as the raw histogram, that is easily disproven.
  1. Put the camera on a tripod, set the white balance to 3200K.
  2. Observe the histogram.
  3. Now set the WB to 8000 K.
  4. Observe that the histogram is different.
  5. Examine raw files made with the two WB settings.
  6. The raw data is the same.
  7. QED.
Two back of camera luminance histograms with different WB settings in the camera. No other setting were changed.

1e2351c0bbe14cbdacd5c902872031c2.jpg

Notice how much closer to the right side the lower histogram is.
Notice how much closer to the right side the lower histogram is.

In order to prove that the in-camera histogram doesn't represent the raw histogram, all that's necessary to prove is that WB settings in the camera affect the in-camera histogram, since the two shots above can't possibly represent the raw file data, unless someone is going to claim that the raw data (not the metadata) is affected by in-camera WB settings. Is anyone going to assert that?
can you post an incamera rgb histogram instead like on the sony. i will test now.
Those are in-camera histograms, from the live histogram on a GFX 100 II. The RGB ones are also different from each other when you change the WB. But I wanted to keep it simple. If the luminance histograms are different, the RGB ones can't be the same.
all good Jim, im just going to come to the conclusions that DR measurements are far from the truth from any site. so i just tested my xz1 in my studio and even though dxo says 10.4 and the d30 from DPR 8, after pushing the jpeg file from the d30 and the raw file from the xz1 the d30 is so far in front its not even a competition. even my a7iv is not even close to 15 stops. i get 1+1=2 and 2+2=4 but DR 1+1=7 🤨
 
ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
I don't know what you're trying to describe here. If you're talking about the point at which a grey card appears as white and black in JPEGs with different exposures, then you're characterising your JPEG engine, not measuring dynamic range.
i over/under exposed the raw file til i couldnt recover anymore information in ACR ,and gauging from the shutter speed in combination with the aperture 9.5 stops measured from the exposure settings.
The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
That's not the same as proving that histograms are based on Raw output. You can get the histograms on a Sony to more closely match the Raw clipping point by using the HLG profile, but this is a fortuitous 'hack,' rather than an expected consequence. It's still prone to the WB problem that's been highlighted elsewhere. But that's still a tangential point.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
You have posted a series of images with no adequate explanation of what they're showing or, really, what you think you're seeing in them. As I say, the overexposed Kodak charts appear to show the Fujifilm has more dynamic range (less noise at the darkest tone), but there's nothing to show us deep shadows.

Beyond that you've posted a processed JPEG, which can't tell us anything useful about sensor DR and a supposed Raw conversion that you say shows less DR because its histogram fits within clipping. Again it's so unclear what you think this demonstrates that it's impossible to sensibly respond to.

I provided a link to an image with DR of around 13EV. I can squash that all into the histogram of a JPEG if I wanted to: it wouldn't tell me anything useful and it wouldn't mean the original shot had less DR than I'd measured.
will have a play with that file now

edit , so i had a play with the file, its imposable to recover the information on a single image. and how did you measure the scene was 13 stops. the only way would be to take 2 images at different exposures.
No one has responded to your claims because it's not clear what you think you're showing.
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
At the point you're testing highlight recovery algorithms, you're not really talking about sensor DR anymore.

Richard - DPReview.com
 
Last edited:
As you have demonstrated, the Canon D30 has underrated DR performance and can keep up with much more modern and expensive cameras. Unfortunately the D30 uses a CMOS sensor, which eliminates it from contention because CCD sensors have superior cinematic colors especially in tricky lighting situations. This is why I still shoot a Nikon D40.
i had the k100d same sensor , and the colours were great.

i will have a look at a k100 file now.
 
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.
i know that i was questioning the difference of cameras in general of that era as dxo didnt do a test of the d30. ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
Your evidence was a side-by-side screen grab of two OOC JPEGs of very different subjects in different lighting (one quite high contrast, one low contrast), with indeterminate in-camera settings (noise reduction in particular). Both JPEGs pushed by you to lift the very different shadowed areas. Instead of attending to the patient efforts expended by Richard to educate you on the limitations of your "evidence", your response is that you've offered "evidence" and nobody else has...

...well, here's some counter-evidence for you, selected and prepared and presented the same way you did but at least utilizing considerably more similar scenic and lighting conditions:

Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)
Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)

The D30 shot is ISO 100. Guess what ISO the GFX100 shot is? (Hint: it has something to do with your supposed missing six-stop difference...).

[Apologies to Richard Butler for adopting Donald's flawed methodology for DR comparisons!]
Richard - DPReview.com
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
This is a different topic probably more suited for the Retouching Forum, but please share your test JPEG and results. I am not aware of any insurmountable advantage that ACR has over PS's internal tone controls when ACR is used as a filter in PS (or to otherwise directly edit a JPEG). The real difference is that ACR gives you one targeted tool (the Highlights slider) vs PS giving you multiple generic tools and dozens of different ways to go about taming highlights. Regardless, it's still just the same RGB (or Lab, CMYK, etc.) data (clipped or nearly-so) that you're constrained by.
 
Last edited:
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.
i know that i was questioning the difference of cameras in general of that era as dxo didnt do a test of the d30. ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
Your evidence was a side-by-side screen grab of two OOC JPEGs of very different subjects in different lighting (one quite high contrast, one low contrast), with indeterminate in-camera settings (noise reduction in particular). Both JPEGs pushed by you to lift the very different shadowed areas. Instead of attending to the patient efforts expended by Richard to educate you on the limitations of your "evidence", your response is that you've offered "evidence" and nobody else has...

...well, here's some counter-evidence for you, selected and prepared and presented the same way you did but at least utilizing considerably more similar scenic and lighting conditions:

Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)
Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)

The D30 shot is ISO 100. Guess what ISO the GFX100 shot is? (Hint: it has something to do with your supposed missing six-stop difference...).

[Apologies to Richard Butler for adopting Donald's flawed methodology for DR comparisons!]
Richard - DPReview.com
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
This is a different topic probably more suited for the Retouching Forum, but please share your test JPEG and results. I am not aware of any insurmountable advantage that ACR has over PS's internal tone controls when ACR is used as a filter in PS (or to otherwise directly edit a JPEG). The real difference is that ACR gives you one targeted tool (the Highlights slider) vs PS giving you multiple generic tools and dozens of different ways to go about taming highlights. Regardless, it's still just the same RGB (or Lab, CMYK, etc.) data (clipped or nearly-so) that you're constrained by.
i used both jpegs from DPR at iso 100 not imaging resourse
 
As you have demonstrated, the Canon D30 has underrated DR performance and can keep up with much more modern and expensive cameras. Unfortunately the D30 uses a CMOS sensor, which eliminates it from contention because CCD sensors have superior cinematic colors especially in tricky lighting situations. This is why I still shoot a Nikon D40.
i had the k100d same sensor , and the colours were great.

i will have a look at a k100 file now.
just revisited some images from my k100d, WOW............ how good it the shadow lifting even skin tone in dark shadows can be lifted with perfect skin tones, im impressed and i only shot jpeg back then.



b59b3764c40a42b69cfda8b57e399429.jpg
 
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.
i know that i was questioning the difference of cameras in general of that era as dxo didnt do a test of the d30. ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
Your evidence was a side-by-side screen grab of two OOC JPEGs of very different subjects in different lighting (one quite high contrast, one low contrast), with indeterminate in-camera settings (noise reduction in particular). Both JPEGs pushed by you to lift the very different shadowed areas. Instead of attending to the patient efforts expended by Richard to educate you on the limitations of your "evidence", your response is that you've offered "evidence" and nobody else has...

...well, here's some counter-evidence for you, selected and prepared and presented the same way you did but at least utilizing considerably more similar scenic and lighting conditions:

Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)
Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)

The D30 shot is ISO 100. Guess what ISO the GFX100 shot is? (Hint: it has something to do with your supposed missing six-stop difference...).

[Apologies to Richard Butler for adopting Donald's flawed methodology for DR comparisons!]
Richard - DPReview.com
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
This is a different topic probably more suited for the Retouching Forum, but please share your test JPEG and results. I am not aware of any insurmountable advantage that ACR has over PS's internal tone controls when ACR is used as a filter in PS (or to otherwise directly edit a JPEG). The real difference is that ACR gives you one targeted tool (the Highlights slider) vs PS giving you multiple generic tools and dozens of different ways to go about taming highlights. Regardless, it's still just the same RGB (or Lab, CMYK, etc.) data (clipped or nearly-so) that you're constrained by.
so i took my over exposed Jpeg image into ACR and pulled back the exposure and detail was recovered. in PS i did the same with exposure and it just made the image hazy grey.

but i just took the image into PS and used Levels to pul back the exposure and got the exact results as ACR 🤔I never liked exposure slider in PS and i know why now 😊
 
I have downladed and pushed the shadows of test images from the canon d30 and the results were nothing short of amazing.

1040aeff15304f9e8af00c70f459cfd3.jpg

db5face9880344b9a0a363bf9f17c554.jpg

0b1c0669c0b2471b9cce6f72d9e9147d.jpg

pushed 4 stops

D30

de226b71489c4188b3b691584d769b17.jpg

GFx 100

35b71b91b40946609f46004e269fe398.jpg
The phrase “not even wrong” is a critique in scientific and philosophical discussions. It means that a claim or idea is so ill-posed, incoherent, or misframed that it can’t even be evaluated; it fails to meet the minimum standard of being falsifiable. It was popularized by physicist Wolfgang Pauli.

A statement is “not even wrong” if:
  • It’s vague, non-testable, or internally inconsistent
  • It doesn’t make concrete predictions that could be checked
  • It misuses terminology in ways that render it meaningless in context
I think Richard has explained the main issues.
explain these 2 black level comparrisions when pushed, the d30 clearly out performs the values in the shadows. the smaller pixels have crushed the information.

46080bc0954a4595b1ee4e78301d53d3.jpg

6df2400da5244ffdb916cf53fbe268e1.jpg
I've just found that motorbike picture in the review and I don't think we published the Raw file. Are you trying to assess DR from JPEGs?

Because, as I say, most standard JPEGs use tone curves to convey about 8.5 or so EV of dynamic range, discarding everything beyond that.

Trying to assess DR by pushing JPEGs is like smashing sets of crockery and trying to guess how maleable the clay they were made from was, before they were fired.

Richard - DPReview.com
the histograms are near identical from a pushed gfx100 raw file vers jpeg, im wanting to see the extra 6 stops of DR demonstrated. to be honest id take the d30 jpeg over the raw gfx 100 file till someone can clearly show 6 stops difference when it starts behind from the start 🤔

27d22c79b28f452892f5f784445d8179.jpg
First people have been trying to teach you the difference between the histogram you are showing as it is not a raw histogram and is of the processed raw data that has been placed with in a color space.

I know of at least 7 threads started over various platform that you have not learned the difference, until you fully understand what those extra stops of DR mean and how that relates to what is captured in the raw file I feel it will be the very same runaround many of us have dealt with the past 10 years and trying to tell you what that extra DR is and how it relates to how we process that data into the color space you are trying to display that data in.

In one final attempt to show you where this extra DR comes into play

2d38773702e94cd786044602c2682259.jpg

In the red box the image data falls well below the DR that can be displayed in the color space in the tonal ranges that are held within the standard tonal range.

When we are discussing the DR of the sensor and how much is recorded, we are talking about the range of the lightest to the darkest data being collected with floor to the lowest signal determined by a noise level.

073312b230c64188837f03d373600057.jpg

We are then compressing that range of DR into the color space we are going to display that data in. That red patch was well below the 0,0,0 color space with its placement in the raw data. We then compress that to how we want to display that tonal range of the raw data
your red box is showing 19 19 19 its not below at all.
You know what you have done when reading the RGB values in that red box area?

You are measuring the values of a screen grab on a viewer in a nonsensical way derived that the value is 19,19,19 in the limited range of that grab and its color space.

What you should be looking at is the recorded values shown in the histogram, those values that show -8 to -11 that is the signal that was recorded by the sensor telling us that it is -8 to -10 stops from 0ev with a total of -10 to -12 from the full saturation of what the sensor can record. Clearly you do not understand what is being shown here yet again you should really look at what is being presented to you and let it sink in as to what is being shown.

These are values that cannot be shown in the limited DR of the color space and needs to develop to compress this into the limited color space
the d30 image lowest black is 12 12 12

the myth that the incamera histogram doesnt equal the raw , i disproved that 2 years ago. i just shot an image with the histogram just clipping the blacks and the reading was 0 1 1 😊
Not this again, without understanding what is shown above how can you make such a statement again?
there will never be true black
what is black? is it the lowest signal a sensor can record? or is it what we classify black as within the tonal range of a printed image?
in a high contrast scene ,lens veiling glare takes care of that.
And yet I have an image that is a high contrast image with a DR of 11 stops and lens veiling glare is not a problem



445fa2180d1e4ef49b46a81f2640f76b.jpg

Those trees that are contained within the red box has been lifted several stops placing those tones within the final image into a range showing color and contrast. How can this be if it is as you say it is.



--
The Camera is only a tool, photography is deciding how to use it.
The hardest part about capturing wildlife is not the photographing portion; it’s getting them to sign a model release
 
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.
i know that i was questioning the difference of cameras in general of that era as dxo didnt do a test of the d30. ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
Your evidence was a side-by-side screen grab of two OOC JPEGs of very different subjects in different lighting (one quite high contrast, one low contrast), with indeterminate in-camera settings (noise reduction in particular). Both JPEGs pushed by you to lift the very different shadowed areas. Instead of attending to the patient efforts expended by Richard to educate you on the limitations of your "evidence", your response is that you've offered "evidence" and nobody else has...

...well, here's some counter-evidence for you, selected and prepared and presented the same way you did but at least utilizing considerably more similar scenic and lighting conditions:

Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)
Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)

The D30 shot is ISO 100. Guess what ISO the GFX100 shot is? (Hint: it has something to do with your supposed missing six-stop difference...).

[Apologies to Richard Butler for adopting Donald's flawed methodology for DR comparisons!]
Richard - DPReview.com
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
This is a different topic probably more suited for the Retouching Forum, but please share your test JPEG and results. I am not aware of any insurmountable advantage that ACR has over PS's internal tone controls when ACR is used as a filter in PS (or to otherwise directly edit a JPEG). The real difference is that ACR gives you one targeted tool (the Highlights slider) vs PS giving you multiple generic tools and dozens of different ways to go about taming highlights. Regardless, it's still just the same RGB (or Lab, CMYK, etc.) data (clipped or nearly-so) that you're constrained by.
i used both jpegs from DPR at iso 100 not imaging resourse
You also presented two very different shots involving a motorcycle and a light post for your black level "evidence" and, in so doing, claimed:

explain these 2 black level comparrisions when pushed, the d30 clearly out performs the values in the shadows. the smaller pixels have crushed the information

and doubled down in a later response to Richard:

the histograms [in the motorcycle and lightpost shots] are near identical from a pushed gfx100 raw file vers jpeg, im wanting to see the extra 6 stops of DR demonstrated. to be honest id take the d30 jpeg over the raw gfx 100 file till someone can clearly show 6 stops difference when it starts behind from the start

I've offered the requested counter-evidence. Please comment on whether my counter-evidence "clearly shows 6 stops difference".
 
these measurements are 2 stops different. and there is a discussion happening how accurate is the camera histogram ( in my testing .3 stop), a resitor has as little as 1% tolerance yet these figures are 25 % out. the question remains WHY !

51193d3915fe4432b9c92a8dbf396079.jpg
I note these are figures for the 30D, not the D30.
i know that i was questioning the difference of cameras in general of that era as dxo didnt do a test of the d30. ive just tested my a7iv and couldnt squezzzzz any more the than 9.5 stops on a neutral gray card from clipping to clipping.
DPReview's assessment of DR circa 2006 was of how much of the camera's DR was included in the JPEGs. It's not relevant to discussions of overall sensor DR. (Other than to reinforce what I've said about standard JPEG typically only including around 8.5EV of dynamic range, regardless of how much beyond that the sensor was capturing).

To prevent having to explore any further blind alleys: DxOMark quotes Engineering DR (ie: to the standard SNR=1 cut-off), whereas photonstophotos uses its own threshold, so again there's no reason to expect the numbers to match one another.

The discussion about camera histograms I've seen isn't about whether or not they accurately convey the entirity of a sensor's DR, they're just about you claiming to have dismissed as "myth" that they're based on JPEG data. This is a false claim, readily disproved using the simple test Jim Kasson outlined.
you can set sony zebras to near identically match Fast raw viewers.
We still come back to the fact that you claim to prove that there's no major difference in DR between the D30 and a GFX and yet have provided no plausible, coherent or comprehensible evidence to support it.
i have put up a discussion and no images/evidence have been posted in response.
Your evidence was a side-by-side screen grab of two OOC JPEGs of very different subjects in different lighting (one quite high contrast, one low contrast), with indeterminate in-camera settings (noise reduction in particular). Both JPEGs pushed by you to lift the very different shadowed areas. Instead of attending to the patient efforts expended by Richard to educate you on the limitations of your "evidence", your response is that you've offered "evidence" and nobody else has...

...well, here's some counter-evidence for you, selected and prepared and presented the same way you did but at least utilizing considerably more similar scenic and lighting conditions:

Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)
Left=GFX100 OOC JPEG (from Imaging Resource); Right= D30 OOC JPEG (from the DPR review)

The D30 shot is ISO 100. Guess what ISO the GFX100 shot is? (Hint: it has something to do with your supposed missing six-stop difference...).

[Apologies to Richard Butler for adopting Donald's flawed methodology for DR comparisons!]
Richard - DPReview.com
interesting finding but. so recovering highlights from a jpeg test image in ACR is way more effective than from PS itself ,in fact i was very supprised at the difference, it wasnt even close.
This is a different topic probably more suited for the Retouching Forum, but please share your test JPEG and results. I am not aware of any insurmountable advantage that ACR has over PS's internal tone controls when ACR is used as a filter in PS (or to otherwise directly edit a JPEG). The real difference is that ACR gives you one targeted tool (the Highlights slider) vs PS giving you multiple generic tools and dozens of different ways to go about taming highlights. Regardless, it's still just the same RGB (or Lab, CMYK, etc.) data (clipped or nearly-so) that you're constrained by.
so i took my over exposed Jpeg image into ACR and pulled back the exposure and detail was recovered. in PS i did the same with exposure and it just made the image hazy grey.

but i just took the image into PS and used Levels to pul back the exposure and got the exact results as ACR 🤔I never liked exposure slider in PS and i know why now 😊
Yes, the Exposure slider in ACR does not operate in the same way as the Exposure slider in PS. The PS slider is a brute force one and the ACR slider tapers the adjustment as it approaches clipping.
 

Keyboard shortcuts

Back
Top