I’ve only noticed this very recently. I’m not 100% sure it’s all photos, but it seems that picking “Daylight” gives the same results as “As shot”.
For example I have a photo I’m working on now which has 5270, -4 as the “As shot” values and picking daylight leaves both numbers unchanged. If I pick “Cloudy” it goes to 6000, 0 and then I pick “Daylight” and it goes back to 5270, -4.
There appears to be quite a difference in rendering if you look at the whole image.
But, if you look at a crop of just the seat back…
… it is very difficult to tell which is which.
The PL manual is both wrong and right at the same time. 5200°K is at the lower/warmer end of “daylight” but could be accounted for if the manual writer lives in the middle of Paris when the air pollution affects the light colour
If you are using auto WB on your camera, my guess is that PL will try to match whatever that temperature is at the time of shooting.
Not for me, using a Canon 90D with the camera set to ‘Auto White Balance’.
In PL (3) and using ‘As Shot’, the temperature and tint varies from image to image, which is what I’d expect because using AWB will mean the camera will write a different temp. and tint to the EXIF on each shot and in turn PL reads those varying data and uses them.
If though I set PL to use ‘Daylight’, the temperature is always 5200K and the tint is always zero. Again, that’s what I’d expect. PL is ignoring the (variable / AWB) temp. and tint data in the EXIF and applying its own, fixed, values.
It might be “hard coded” from PL’s point of view but 5200°K is not the normally accepted temperature for daylight.
If a camera has been set to automatic WB, the image will already have been adjusted, in camera, to what the camera thinks daylight should look like. What that temperature is will depend on the camera manufacturer. Then PL has its own idea of what daylight is.
According to this chart, daylight can be anything between that produced by a low sun (5000°K) and that produced by the sun being directly overhead (5500 - 6000°K). The generally accepted definition of daylight for photographic colour integrity has been 5600°K for many decades.
My guess is that DxO, along with some camera manufacturers, have chosen 5200°K because it produces a slightly warm rendering, which psychologically makes people feel “happier”.
The truth is, you are free to choose whatever temperature suits the mood you wish to convey in any particular image.
But to return to @zkarj 's original subject, if the “as shot” automatic WB temperature is near enough to what DxO calls daylight, then you won’t see any obvious change. The difference between 5200 and 5270 isn’t worth worrying about.
That table goes further. It also mentions 6500 daylight overcast. So the daylight range is between 5000 and 6500.
I think you misread the post of @zkarj. PL doesn’t show the right value, whatever that value might be. If PL uses 5200,0 for daylight, than that value must be shown when daylight has been selected. It doesn’t.
Beside that, calculating can be done only with a fixed number. As long as it is between 5000 and 6500 for daylight according to that article. If you don’t like the result you can to correct that.
Daylight is divided in 3 subgroups: direct sunlight 5200, clouded 6000, shadow 8000.
The files in question are RAW files and thus the camera’s interpretation of the light at the time is just a pair of numbers recorded into the metadata at the time the file was written. By default, PL uses these numbers on the RAW data to come up with an interpretation in the RGB space and it marks this behaviour by showing those numbers and listing “As shot” in the drop down list. The user is then free to choose whatever values they wish according to better knowledge than the camera and/or artistic desire.
The WB palette in PL is a pair of sliders/numeric entries to set those values numerically, or a short list of “standard” values as determined by DxO which can be used as a form of preset. In testing, I can choose “Cloudy” from the preset list on any number of photos and it always sets the numbers to 6000, 0. Without fail. If I pick “Shady” I get 8000, 0 without fail. I would expect, per the manual, to get 5200, 0 without fail when picking “Daylight”, as these numbers have nothing to do with the camera or the photograph in question. They are pre-chosen values baked into the software.
But that’s not what happens. Sometimes I get 5200, 0 and sometimes I get the very same numbers that the camera chose.
The ‘as shot’ or ‘camera’ is always calculated by the converter based on the image itself.
I’ve been trying to find out how that happens.
Google on ‘raw demosaic algorithm’ and look for the more technical sources. Also with ‘raw color temperature algorithm’.There’re more ways leading to Rome. Dutch expression.
I think that’s also a mistake. The statement 5200 is colder than 5600 is right. The way how it is used in photography is wrong.
You watch an image with color temperature 7000. What do you see??? You don’t see an image with 7000K, you see an image that’s corrected for 7000K. If you change the coler temperature to 10000 you’ll see the color is getting reddish. This is NOT for 10000 is more reddish but for the overcorrection you use.
You use a color temperature of 5600 fixed. Let’s say 5600 is neutral white, no correction. You’ll get the image without correction, more as you see it yourself. I believe PL is using 5400 for that purpose, being the initial value. Not sure, but it is around there.
I could touch white hot iron for a moment, I couldn’t touch red hot iron. White hot is so hot that the moisture in your hands is evaporates so quick that it creates a vacuum between your hand and the iron. A molding lesson.