Originally posted by beholder3 Often with photos people mix up input maximum dynamic range, that is what a sensor can detect, and data storage, like bits. And third the output dynamic range like prints or screens.
Add to the mix the color space they are processing the raw files into. So when they output a color into a color space it can fall outside of the 0-255 values of that container and thus think it clips in the raw data
Here you can see the published lab values in ColorcheckerSG target color plotted in a s RGB color space. everyone of those dots that fall outside of that color space would show up as greater than 255 or less than 0 but this does not mean that it somehow has been clipped in a raw file, it has been clipped within the processing of the image
People have to be careful when they say that a tonal value that fall nears the RGB value of 255 is blown out. it is the processing of that data into a color space that can lead someone think it is somehow clipped.
A luminosity value of 95% can be 202,202,202 while in another color space it can be 226,226,226
If I was to show someone this
Looking at where and how these colors falls where within the 0-255 container it would lead you to believe in the wrong assumption as all the pixels fall at 255
while in this color space there is no problems with how it falls within that container as none fall in 255 range.
We really have to be careful when trying to plot a tonal range within a color space as this can mislead someone into thinking something that is not there. And we should really only view raw data from the camera as based on the saturation capacity of that raw container and not into a working color space as raw really has not lightness its just measured values with a filter in front of them..