@Joanna
Probably PL initiates the variable with a number 5400 to be sure it’s numerical. I think. That should be replaced with the actual temp. It’s just not done in a elegant way.
The difference between the manual in-camera wb and the wb in PL I can’t explain. I just didn’t investigate that. I don’t know what is written in the exif. Probably PL is just calculating it by itself and means “as shot” based on the raw data and not camera setting. Try an extreme different manual wb in your camera, let’s say 10000, and see what PL does.
On further investigation, using Exif Editor, in the advanced camera data, the WB is simply marked as 1, which appears to be the equivalent of “Daylight” or 5400.
Using Apple’s own Preview app shows Nikon specific data of 5600K, but this is obviously not read in either Exif Editor or DxO.
But nowhere can I see any reference to 5510, which is what DxO ends up showing.
In PhotoLab and in other photo softwares temperature displayed in user interface doesn’t correspond to setting of cameras.
Reasons of that are:
it’s not possible to get precise temperature/tint applied by a camera at shoot when a white balance preset is selected because cameras adapt WB even with preset and in litterature only range of temperature are given.
different models of cameras (especially with different brands) won’t give the exact same temperature/tint for a shoot of the same scene with the same light
About White balance presets:
In photo softwares temperature and tint displayed are just a scale to help adjustment. So, in PhotoLab, temperature/tint have been fixed for presets displayed. So when processing images from different cameras there will be no discrepancies.
About temperature and tint:
PhotoLab, as any other rawconverter, use White Balance given in Exif. To be accurate it uses White Balance scales (coefficient to apply in rawconversion to get same white balance as camera).
In camera profile we have white balance scale for all preset given previously (cloudy, tungsten, …).
So when a photo is put in PhotoLab it looks to white balance scales, apply them and do a calculation to estimate temperature and tint associated compared to scales in camera profile. This calculation is specific to any rawconverter that’s why every converter from different company will provide different temperature / tint associated to an image.
Just tried. D750, set the temp manual on 10000.
In PL opening first time temp 5400, enabling raw temp 10014. Small difference.
Difference between Johanna and me is that I set the wb to manual. IView mentions manual in the exif.
@Marie
And what about the discussion about the initial value of the wb when raw is disabled?
@Marie, as far as I’ve understood @George, the pain lies in the fact that the default value of 5400 does not go away when images are switched.
Maybe it’s also about language, many of us are not native English speakers…
For translations, I have found that deepl.com did a fairly good job when I used it.
I can understand that for the presets but, what about when you select a temperature manually? Which is what I do, to the extent of not just choosing one of the “steps”, but dialling in the exact temperature. I use 5600°K and would have hoped, since it is written in the EXIF, that it would be read.
Given that this exact temperature is available in the manufacturer’s data, couldn’t/shouldn’t it be part of the camera profile?
The main problem of this discussion is that PL suggests that Raw wb can be disabled. It just can’t. Trying to do that is something as going up the ladder without a ladder.
The picture I see when I open it the first time is a picture with a color temp “as shot” but the info tells 5400. The 5400 is not used.
From what I understood from Platypus the value is overwritten with the used color temp on a Mac. I can’t check that, but that would be the right way. And it isn’t on the win pc.
In the example of Guentherm on a win pc PL shows the image with a color temp of 3381K but the info says 5400K. Only when enabling, whatever is meant with that, the value is updated to 3381 and stays like that, also when disabling again. The picture doesn’t change, the histogram doesn’t change. Only the info changes ones from wrong to right.
The shown value isn’t updated in the beginning where it should be updated. On a win pc anyway.
That is because the palette is not enabled and the auto calculation is not forced. This is the same for example like Contrast - when you enable the palette the auto value is calculated:
You just see the default value of the slider but it does not mean it’s applied when the palette is disabled.
The same behaviour as with me although we may disagree about what should be.
May I conclude that on a Mac the 5400k is updated to the actual used temp at initialization but not on the win pc.
And that when I see a temp of 5400 then that’s for nearly 100% a wrong number?
Hello, the video of Svetlana shows exactly what I’ve tried to describe with my 1 to5 steps.
So maybe platypus can also describe with steps or film what is wrong.
Regards
Guenter
Playing with the tool.
Opening an image as before.
Raw disabled. Shown setting: as shot. Temp 5400. This is a wrong combination.
Raw enabled. Setting as shot, temp, temp 5138. This is the right combination.
Change setting to tungsten, temp 2850. Picture shows this temp of 2850
4.Raw disabled. Picture shows image as as shot,5138. Setting tungsten, temp 2850
Raw enabled. Picture shown with temp 2850.
This tool shows the image always as as shot when disabled. When enabled and you change the temp the setting changes to one of the other possibilities and the corresponding temp. When disabling the image is shown as as shot but the setting and temp in de window doesn’t change and are related to each other. And that is not the situation at opening. The 5400 should be overwritten with the as shot value.
For Step 1 maybe its not nice, but isn’t incorrect…because
If something is disabled, all subvalues are defined wit whatever parameters (default values DXO developers decide to take.)
This behaviour you will find also in software nothing has to do with photos
Only my opinion
WB is announced almost immediately and the value displayed is whatever DPL makes of whatever is in the image and its metadata
When I go from one image to the next in rapid succession, WB is displayed to be 5400, DPL’s default value - so be it. When I stop fast forwarding, the value of the currently selected image is displayed.
With the WB tool enabled and set to Camera Settings
Behaviour is exactly as described above.
Comment
In an earlier test, 5400 showed up briefly and then was replaced with whatever DPL makes of whatever is in the image and its metadata
I’ve meanwhile deleted the database and cache files and now, the WB value changes so quickly that I cannot see the 5400 any more - unless I fast forward through the film strip.
While it is an interesting thing to know how DXO works under the hood, I don‘t understand why anyone wants to disable the WB panel instead of having it enabled and set to camera default when when working on RAWs. I tend to tweak WB a bit on most pictures and never would disable this panel. For me it is as fundamental as exposure.
It is interesting to be able to disable the WB tool for partial presets. This allows partial presets to work an image while leaving WB alone. This means that you can set WB early in your workflow and later apply a (partial) preset that will not disrupt that early step.
