switching to spot white balance doesn't change WB sometimes
I manage to reproduce it reliably if I start with unmodified image, enable some heavy module like profiled denoise and change WB to spot while image is still being processed ("loading" still displayed). In this case spot white balance preset appears to be selected, but actually multipliers haven't been recomputed and remain the same as in camera WB. Changing to camera WB and back to spot still does nothing after that.
I suspect it has something to do with preview (or main) pipe still running when WB module wants to access its results and unable to do so it just silently gives up and keeps old settings (and this result is cached in mipmap cache, so just toggling it to camera and back doesn't help).
#2 Updated by Richard Wonka about 3 years ago
confirmed here on stable/ubuntu (elementaryOS)
selecting "spot" in the white balance drop down list does not always switch to spot white balance.
It appears that it might be be a race condition (my hardware is great to test for race condidions! ;-) . I have not been able to reliably reproduce it, but it is frequent. Happens well above 50% of the times I want to switch to spot WB.
This has been the case for a very long time, sorry for only reporting today.
#4 Updated by Mikołaj Milej about 2 years ago
Same here, this issue appears quite often.
If set "spot WB" (while issue is triggered) then I go out to light table and go back to darkroom then it says "camera WB".
As far as I realized there are steps to reproduce:
1. run DT
2. open image
3. set "spot WB"
4. set "any other WB preset"
5. set "spot WB"
6. if it's ok, then goto 4 (for the second time it's always broken)
7. you have to restart DT to have "spot WB" working
#6 Updated by Peter Budai 10 months ago
- Status changed from Triaged to Fixed
- % Done changed from 20 to 100
Applied in changeset darktable|4edd1ab10b5c777ac3c5310d6bf530c23c4cf992.