First, I'm not actually sure if this is the best place to raise the issue, but I figured I start here, if only for discussion.
My (very limited) understanding is the sensor saturation threshold (DNG WhiteLevel tag) can vary for the same sensor, if some digital down gain is applied. My example was on a Canon EOS 5D Mark III, with 1/3 stops increments, where the increment closest to the next larger full ISO (eg. 640 closest to 800) may use the ISO 800 analog gain, then a digital down gain. When checking DNG (from Adobe DNG Converter) on this ISO pair, the WhiteLevel tag varies accordingly, LibRaw however returns a fixed / hard coded gain in such case. I'm finding this can be an issue with consequence such as highlight color shifting.
My workaround is currently to use the Canon Exif metadata to manually derive the saturation level and pass that to the Converter's saturation_level setting (Canon:SpecularWhiteLevel - Canon:AverageBlackLevel).
First, I'm not actually sure if this is the best place to raise the issue, but I figured I start here, if only for discussion.
My (very limited) understanding is the sensor saturation threshold (DNG WhiteLevel tag) can vary for the same sensor, if some digital down gain is applied. My example was on a Canon EOS 5D Mark III, with 1/3 stops increments, where the increment closest to the next larger full ISO (eg. 640 closest to 800) may use the ISO 800 analog gain, then a digital down gain. When checking DNG (from Adobe DNG Converter) on this ISO pair, the WhiteLevel tag varies accordingly, LibRaw however returns a fixed / hard coded gain in such case. I'm finding this can be an issue with consequence such as highlight color shifting.
My workaround is currently to use the Canon Exif metadata to manually derive the saturation level and pass that to the Converter's saturation_level setting (
Canon:SpecularWhiteLevel - Canon:AverageBlackLevel).