I actually get ‘as shot’ by default, at least the values are the same (in this case, 4755 K). Default:
Changing to ‘as shot’ (note the same colour temperature and the classification as ‘daylight’):
The image colours don’t change, either. This is with NEF (Nikon) and RW2 (Panasonic) files.
here :
It is. The default parameters, put in the module when you open it, are the settings defined by your camera and put in EXIF. The real “as shot” option is a redundancy that helps you create presets that will read, at runtime, the actual image EXIF instead of storing the WB of the image on which you made the preset (so it’s a dynamic preset).
Thank you all. The error is located behind the camera. Blown reds result in magenta shifting.
Thank you.
But I don’t have as shot by default, I have Day light as default, and the image is quite yellow.
When I change the illuminant to “as shot in camera” I get it the right color.
I have to retest it with new images (I have tested it with images that were already edited, changing the workflow to modern and resetting their history to get the new workflow with white balance and camera calibration).
@anon41087856 reading is not enough, you need to understand what you are reading to be effective.
I had misunderstood several things in what I had read till now.
Thanks to this thread I think I have a better understanding of what camera calbration does and how to use it to make simple white balance and color interpretation.
Now it is time to re read the documentation slowly as you say with a new perspective.
I had similar problems in sky with zones that are partially blown, with cyan tones.
I think the problem is earlier in the pipeline, as was said here.
There is a light reconstruction algorithm just after white balance.
It clips blown channes by default.
Better results can be get sometimes with color reconstruction or reconstruct LCh (which makes them white).
Some times you can recover llights using exposure and underexposing a bit, as the lights are not really blown in the raw.
Adjusting filmic parameters can help too.
But I don’t know exactly how each parameter in filmic affects blown lights yet.
Reversely, in the shot I posted any highlight reconstruction leads to magenta colors. In the next sunrise-/set photos I will expose to right regarding the sun and see what happens (e.g. shadows).
So it might be a bug in the initialization of the module, maybe the EXIF are not available at the time of init or something. What if you reset the module ? It should give the same settings as “as shot in camera”.
OK, I will double check it to see if after resetting I have the same temperature as when I use as shot for the illuminant.
Well, think about the camera for a bit. Setting the WB to Daylight just forces use of the daylight multipliers. If the camera was set to Auto WB, the as-shot multipliers will probably be a best-effort assessment of the actual scene with regard to WB.
I pretty much keep my camera WB mode on Auto, so I can take advantage of the camera assessment of the scene for my initial batch proofs.
Me too, I use auto WB almost allways, as I shoot raw and allways process afterwards.
Camera makes a good guess most of the times, and when not I change it later witout loss of quality. Any way I most of the times am going to make some color adjustment to my taste, I do not need fidelity in colors most of the times, just a good aproximation.
But when I use the modern workflow and reset the history of a file I had already in darktable (I don’t have recent new files to test) white balance is set to neutral and color calibration is set Day light with a temperature that is not coincidente to what is set in the camera.
The photo seems too yellow.
Let mi put an example of a photo without processing, just reseted history with modern workflow active:
This is the settings under white balance
This under color balance:
As you can see it adjusts the illuminant to Day light and the temperature to a different one that is used in camera (Aureliene has explained that themperatures do not coincide).
And this is the result a bit yellowish
After changing color calibration and selecting illuminant as shot, the colors are more natural and similar to the old workflow without color calibration (and white balance adjusted to as shot).
If I reset the module setting I get the same result with the temperature set to the same value to “as shot” (well not exactly the same it seems there are 2 K diference).
This the result
If I understood well what aureliene has explained, when you import the image (or reset the history) it should use the illuminant taken from the exif in camera, and both images should be the same (if you have not adjusted something).
And for the sake of completion, here is the same image with the old workflow (heritage), the whitte balance and the result (white balance is quite more warm as shot in camera).
You can see these ultimate results are quite similar.
Temperatures of the images are all different.
I’ve never done much with temperature/tint. After the image is captured, the actual color temperature of the scene is less relevant, and the individual channel multipliers become correspondingly more relevant. Even when scooching a temperature slider around, that number is converted to R, G, and B multipliers for actual application.
I haven’t inspected the temp/rgb conversion algorithm recently (I have ufraw’s source code for that), but I recall some shift in how the computation is done at a certain temperature. So, having markedly different temps for a similar effect is not out of the realm of consideration. @anon41087856 might have specific insight based on his recent work.
In that regard, the corresponding channel multipliers would be of more interest to me… 
Interface do not provide that.
Lets see if aureliene sees the images and explains them and whether it is the expected behaviour or not.
I just do the auto picker in color calib…it uses a pretty good guess…then I set it to custom from that so i get the chroma and hue of its color adjustment…the temp stays the same initially when you do this …then I just tweak the chroma of the appiled color cast add or subtract to it…it is a really nice way to fine tune it…so if a bit too yellow just tweak the chroma…I have found I get great results…
Of course you can allways correct the color.
But having a starting point similar to the jpeg is more desirable and what you expect if you come from other sofware.
I just use auto white balance in camera and so expect to have to touch the temperature and tint a bit.
Others adjust white balance in camera and expect a result adapted to the white balance set.
Having not exactly the same result is not a problem either.
But aureliene said that when the image is imported the color calibration temperature should be set to that in the exif file, the same as selecting “as shot” later.
But when I reset the history of a image (that should get the same results as importing it new) the results are different, and only correct if I change the illuminant to “as shot” by hand.
May be it is a bug (by the way I am using windows) or just expected results and I did not understand.
The results I get just after resetting the history of the image seem the same to setting temperature to “detect over surface of image” that is the automatic mode.
Well that might be a bit of an issue if things don’t reset as expect…as for color I was actually talking about WB in the way that it is handled in color calib…selecting Cat and auto gives this or depending on how you get here…If color calibration thinks its a standard illuminant it will give you temp but if you don;t get this selecting custom will pull it up and then esp for skin tones and other subtle wb issues just adjusting the chroma really allows you to achieve a good look …this of course is separate from your reset issue… 
This ‘very yellow’ appearance has happened to me just now as well. It was not just on a file where the history had been reset but on a newly imported file.
I am on 3.4, Windows 10 with ‘modern’ workflow. Actions were:
Image appears very yellow/orange.
One solution I found was to click ‘reset’ on ‘Color Calibration’ and colors are restored.
It is almost like in some instances in the modern workflow that the ‘Color calibration’ module is not being applied.
Clicking ‘reset’ then seems to activate it
Unfortunately this is totally random, I can’t get it to consistently happen even on images where history has been discarded and it doesn’t seem to happen on all newly imported images either.
That is exactly what I get.
The result I get by default is the same as using the automatic temperature (measuring in all the image surface).
I have to reset the illuminant to “as shot” to get a natural color and similar to using white balance without color calibration.
Yes, if you reset color calibration it seems to get the correct temperature from the file.
May be it is a windows problem?
Let’s see what @anon41087856 says about it, may be a minor bug.
