DR testing results

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.
post a link of the raw file, i have fast raw viewer. richard said his image was 13 stops but when i took the raw image into fast raw viewer , the true color inform ation was unrecoveable from my point of view, i suppose we all have different standards. i took horsshack post as a win for the canon sensor and took some images from my k100d , you want to see shadow recovery of skin tone from a jpeg 🤔 i doubt any current camera could do the same, but im going to test my sony a7iv now as it holds the record for the best DR from any camera via dustins review.
 
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.
friend has always used curves, but ive never really used it much, is it any better than levels ?
 
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.
post a link of the raw file, i have fast raw viewer.
You do not need the raw file it is shown to you in the raw histogram of raw viewer

8410607a40ff4dfcb6e40236c925aa99.jpg

Here is the what was pulled out of the raw file.
richard said his image was 13 stops but when i took the raw image into fast raw viewer , the true color inform ation was unrecoveable
FRV is not for processing images it only tell you how the data is distributed, so I don't know what you are trying to say.
from my point of view, i suppose we all have different standards.
Could it be that the noise is what is limiting the DR you are able to pull?
i took horsshack post as a win for the canon sensor and took some images from my k100d , you want to see shadow recovery of skin tone from a jpeg 🤔 i doubt any current camera could do the same, but im going to test my sony a7iv now as it holds the record for the best DR from any camera via dustins review.
--
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
 
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.
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.
friend has always used curves, but ive never really used it much, is it any better than levels ?
Curves is much more granular and controllable. Think of Levels as Curves restricted to three points of controlling the curve and no way to refine the slope of the curve between those three anchoring points (black, gray and white). Levels is the quick and dirty and often sufficient tool for tone adjustments. Curves is just much more controllable and appropriate for tackling multiple varying amounts of adjusting along the tonal spectrum. I rarely bother with Levels...
 
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.
Here is your problem and your misunderstandings, if the way you are processing your images requires you to take images with different exposures, then this should tell you that there is more DR being captured with that single image raw.

It is greater than the container you are trying to fill ( color space)
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
 
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.
friend has always used curves, but ive never really used it much, is it any better than levels ?
Curves is much more granular and controllable. Think of Levels as Curves restricted to three points of controlling the curve and no way to refine the slope of the curve between those three anchoring points (black, gray and white). Levels is the quick and dirty and often sufficient tool for tone adjustments. Curves is just much more controllable and appropriate for tackling multiple varying amounts of adjusting along the tonal spectrum. I rarely bother with Levels...
thanks for that i just had a quick play. i might have to use it more often. im a quick and dirty PP person 😊
 
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.
Here is your problem and your misunderstandings, if the way you are processing your images requires you to take images with different exposures, then this should tell you that there is more DR being captured with that single image raw.

It is greater than the container you are trying to fill ( color space)
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
i just took a pentax k100 image into PS i had to use 2 images and layers to get the wide DR of that sensor in 1 image.
 
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
 
Last edited:
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
Unless you are directly comparing the deep shadows of Raw images shot under identical conditions with comparable exposures, you cannot, with any confidence, assess whether the DR numbers are correct.

There are two possibilities:

1) DxO and Photons to Photos DR numbers (and our images, which are consistent with them) are wrong, despite being independent of one another and very comparable with one another, given the slightly different things they show.

2) You've misunderstood what the numbers mean

Every time you try to manipulate JPEGs, it points towards answer 2. I don't know what more any of us can do to help.

Richard - DPReview.com
 
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
Unless you are directly comparing the deep shadows of Raw images shot under identical conditions with comparable exposures, you cannot, with any confidence, assess whether the DR numbers are correct.

There are two possibilities:

1) DxO and Photons to Photos DR numbers (and our images, which are consistent with them) are wrong, despite being independent of one another and very comparable with one another, given the slightly different things they show.

2) You've misunderstood what the numbers mean

Every time you try to manipulate JPEGs, it points towards answer 2. I don't know what more any of us can do to help.

Richard - DPReview.com
i manipulated the RAW a6700 image as a comparrision.
 
Last edited:
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
Yep, same with my D40. Btw, not sure about the K100 but the D40 uses its CCD's global shutter rather than mechanical shutter at faster shutter speeds, which means it doesn't exhibit the rolling shutter light banding in artificial lighting that modern CMOS sensors exhibit for both their electronic and mechanical shutter modes.
 
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
Yep, same with my D40. Btw, not sure about the K100 but the D40 uses its CCD's global shutter rather than mechanical shutter at faster shutter speeds, which means it doesn't exhibit the rolling shutter light banding in artificial lighting that modern CMOS sensors exhibit for both their electronic and mechanical shutter modes.
I aways thought that maybe i should have shot raw back then just for future editing, but after this little exercise it makes no difference to me as i can lift dark shadow detail perfectly 😊is your raw files on the d40 any better than the jpegs for manipulation ?. funny thing is i love the jpeg output of both my a6700 and a7iv and dont use raw for my event shoots ,but i do for my studio work just in case.
 

Attachments

  • d6ba93a70b2742b498c47e92db041712.jpg
    d6ba93a70b2742b498c47e92db041712.jpg
    462.6 KB · Views: 0
Last edited:
+/- half a stop in the raw data.

Jack

PS I am not familiar with the camera but it appears to be in a 13-bit recording mode.
 
Last edited:
+/- half a stop in the raw data.
Bearing in mind that there's a very small amount of specular highlights (reflections on the girl's picture and a screw-head) and then a gap of about a 1/2 stop until the meaningful green channel highlights in the white blouse begin. Thus, depending on what you prioritize and your raw conversion/processing skill and care, the shot could have been exposed by another half stop or so to gain a corresponding increase in the shadow end with no meaningful decrease in the highlight end. The effective visible image DR would be expanded accordingly.
Jack

PS I am not familiar with the camera but it appears to be in a 13-bit recording mode.
The exif data indicates use of compressed raw mode. The effect of this appears to be visible in the raw histogram's highlight combing above 7500 DN. Like Jack, I'm not familiar with this mode on the camera and don't know how much the use of this mode will jeopardize control and editing of the affected highlights. When testing the camera's DR capabilities, it's probably best to stick with uncompressed raw.
 
Last edited:
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
Unless you are directly comparing the deep shadows of Raw images shot under identical conditions with comparable exposures, you cannot, with any confidence, assess whether the DR numbers are correct.

There are two possibilities:

1) DxO and Photons to Photos DR numbers (and our images, which are consistent with them) are wrong, despite being independent of one another and very comparable with one another, given the slightly different things they show.

2) You've misunderstood what the numbers mean

Every time you try to manipulate JPEGs, it points towards answer 2. I don't know what more any of us can do to help.

Richard - DPReview.com
i manipulated the RAW a6700 image as a comparrision.
This appears to be your standard operating procedure. First, you post questionable evidence to support a dubious claim. Then, next, when the problems associated with your original evidence are exposed, you abandon that part of the discussion and move on and post another round of questionable evidence. Rinse and repeat.

You've not replied yet to my presentation of counter-evidence to your originally submitted evidence based on the D30 vs GFX100 (see here). Instead, ignoring the admonitions of Richard Butler and others here, you leap forward (sideways?) into another self-produced and self-attested JPEG vs raw comparison. Do you really expect anyone in the PST Forum to take your "evidence" and conclusions you draw from them seriously? What are you trying to accomplish here?
 
this is a joke right 🤨so i have used the k100d for years long ago and only ever shot jpeg with it ,so after horseshacks comment i deceided to go into my studio and simulate the exposure and lighting from a past pentax image and shoot it with my a6700. these were shot at base iso , the pentax k100 image lifted is nothing short of amazing, bigger pixels win and its just a fact period. i love my a6700 but as far as lifted shadowed skin tones with indoor ambiant lighting and sunny day in a window behind subjects the k100 plays a hard game, how these DR measurments are anywhere near correct is beyond me which is what this thread is about.

991043ab36684d248b603797986950c6.jpg
Unless you are directly comparing the deep shadows of Raw images shot under identical conditions with comparable exposures, you cannot, with any confidence, assess whether the DR numbers are correct.

There are two possibilities:

1) DxO and Photons to Photos DR numbers (and our images, which are consistent with them) are wrong, despite being independent of one another and very comparable with one another, given the slightly different things they show.

2) You've misunderstood what the numbers mean

Every time you try to manipulate JPEGs, it points towards answer 2. I don't know what more any of us can do to help.

Richard - DPReview.com
i manipulated the RAW a6700 image as a comparrision.
This appears to be your standard operating procedure. First, you post questionable evidence to support a dubious claim. Then, next, when the problems associated with your original evidence are exposed, you abandon that part of the discussion and move on and post another round of questionable evidence. Rinse and repeat.

You've not replied yet to my presentation of counter-evidence to your originally submitted evidence based on the D30 vs GFX100 (see here). Instead, ignoring the admonitions of Richard Butler and others here, you leap forward (sideways?) into another self-produced and self-attested JPEG vs raw comparison. Do you really expect anyone in the PST Forum to take your "evidence" and conclusions you draw from them seriously? What are you trying to accomplish here?
which part did you not understand, my images have the exif data in tack you provide nothing more than a screen grab, my 2 images are crops from the test images from DPR.

accomplish ! its in the thread title. best part of having a studio is now im going to actually take an image of a very detailed doll and vary the lighting 14 stops and see how both my a6700and a7iv perform.
 
Last edited:
+/- half a stop in the raw data.
Bearing in mind that there's a very small amount of specular highlights (reflections on the girl's picture and a screw-head) and then a gap of about a 1/2 stop until the meaningful green channel highlights in the white blouse begin. Thus, depending on what you prioritize and your raw conversion/processing skill and care, the shot could have been exposed by another half stop or so to gain a corresponding increase in the shadow end with no meaningful decrease in the highlight end. The effective visible image DR would be expanded accordingly.
Jack

PS I am not familiar with the camera but it appears to be in a 13-bit recording mode.
The exif data indicates use of compressed raw mode. The effect of this appears to be visible in the raw histogram's highlight combing above 7500 DN. Like Jack, I'm not familiar with this mode on the camera and don't know how much the use of this mode will jeopardize control and editing of the affected highlights. When testing the camera's DR capabilities, it's probably best to stick with uncompressed raw.
i will change to uncompressed even though compressed is suppose to be 14 stops on the a7iv. im a bit confussed as bit depth has no correlation to DR.
 
+/- half a stop in the raw data.
Bearing in mind that there's a very small amount of specular highlights (reflections on the girl's picture and a screw-head) and then a gap of about a 1/2 stop until the meaningful green channel highlights in the white blouse begin. Thus, depending on what you prioritize and your raw conversion/processing skill and care, the shot could have been exposed by another half stop or so to gain a corresponding increase in the shadow end with no meaningful decrease in the highlight end. The effective visible image DR would be expanded accordingly.
Jack

PS I am not familiar with the camera but it appears to be in a 13-bit recording mode.
The exif data indicates use of compressed raw mode. The effect of this appears to be visible in the raw histogram's highlight combing above 7500 DN. Like Jack, I'm not familiar with this mode on the camera and don't know how much the use of this mode will jeopardize control and editing of the affected highlights. When testing the camera's DR capabilities, it's probably best to stick with uncompressed raw.
i will change to uncompressed even though compressed is suppose to be 14 stops on the a7iv. im a bit confussed as bit depth has no correlation to DR.
Craw precision is at best 13 bits.
 
+/- half a stop in the raw data.
Bearing in mind that there's a very small amount of specular highlights (reflections on the girl's picture and a screw-head) and then a gap of about a 1/2 stop until the meaningful green channel highlights in the white blouse begin. Thus, depending on what you prioritize and your raw conversion/processing skill and care, the shot could have been exposed by another half stop or so to gain a corresponding increase in the shadow end with no meaningful decrease in the highlight end. The effective visible image DR would be expanded accordingly.
Jack

PS I am not familiar with the camera but it appears to be in a 13-bit recording mode.
The exif data indicates use of compressed raw mode. The effect of this appears to be visible in the raw histogram's highlight combing above 7500 DN. Like Jack, I'm not familiar with this mode on the camera and don't know how much the use of this mode will jeopardize control and editing of the affected highlights. When testing the camera's DR capabilities, it's probably best to stick with uncompressed raw.
i will change to uncompressed even though compressed is suppose to be 14 stops on the a7iv. im a bit confussed as bit depth has no correlation to DR.
Craw precision is at best 13 bits.
Hi Jim, just shot some images in uncompressed and all it did was slide the histogram along to "0" it didn actually expand the range . i just processed compressed raw and uncompressed and it only gave me an extra 1/2 stop more in the highlights when over exposing an image by 3 stops and exact noise in the deep shadows when lifting an image 7 stops.
 

Keyboard shortcuts

Back
Top