- Joined
- Jun 27, 2019
- Messages
- 344
- Reactions
- 181
I read the OP again and I certainly misunderstood. That’s my bad.
On the issue of luminance, the camera records brightness on a linear scale but we perceive brightness on a logarithmic scale. Yes the camera records differences in brightness obviously but not the same way our eyes perceive it. It’s up to the raw file reader to convert the data from the sensor to brightness levels as we perceive it or the artist wants the photo to be perceived.
If we just took the the middle value from the camera sensor and used that as the gamma it would be all messed up. For example if the camera has 5 brightness levels it can record 1 2 3 4 5 and we made 3 the gamma value the photo would be all messed up because 2 would be appear twice as bright as 1 but 3 would only be 50% brighter than 2 and 5 would only appear 25% brighter than 4. The raw file converter must apply a tone curve to make it so that the luminosity is evenly distributed throughout the photo. This tone curve or luminosity curve is not contained within the raw data and will vary between raw photo processors and even with different profiles within the raw file reader.
Sure DNGs can come with embedded profiles which contain a LUT to try and produce the same tone curve used by the camera but this is a side car file separate from the raw data from the camera sensor which is the “RAW” file.
"this is a side car file separate from the raw data from the camera sensor which is the “RAW” file."
I suggested in an earlier response that the Sidecar file is perhaps absent or incorrect. I could be wrong of course, but I believe it is the sidecar file that can preserve adjustments in the raw reader. If my client adjusts settings on a raw file, and includes the sidecar, when I open the file in raw reader the client settings are present. Similarly, when I snap a frame on my Canon 7D, the raw file it typically fairly close to what I viewed on screen at capture.