That is true, though I would consider that to be a quick workaround - a plaster on a cut. The proper, permanent fix is to set the correct white levels in camconst.json
This raw files comes from a Nikon D200. It has no camconst.json entry, but the white levels used from dcraw are almost correct.*
The red channel is not clipped in the sky or skin in this raw photo, only the green and blue channels are clipped. There is no need to lower the raw white points - highlights can be cleanly recovered using color propagation:
The image tones and colors look horrible and the histogram spikes when the ICC profile is applied:
Examining the ICC file shows that it does bad things near white:
![](https://discuss.pixls.us/images/transparent.png)
Setting white point correction to -0.3 does lead to an improvement in colors:
But the whole way of going about this seems counter-productive: using this bad ICC profile creates the problem, then you use raw white points to hack around it. Solution: Ditch the bad ICC profile and use curves.
Lowering the raw white points could lead to other issues I haven’t looked into here, such as demosaicing artifacts, problems with flat-fields, etc.
* I measured the white levels to be R=4095 G1=4095 B=3999 G2=4092, while dcraw uses 4028 for all.
{
"make_model": "Nikon D200",
"dcraw_matrix": [ 8367,-2248,-763,-8758,16447,2422,-1527,1550,8053 ],
"ranges": { "black": 0, "white": [ 16383, 16383, 15999, 16370 ] } // WL typical 16383 set to 16300 for safety
},