Bug #9770

switching to spot white balance doesn't change WB sometimes

Added by Igor Kuzmin about 6 years ago. Updated over 1 year ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
git development version
hardware architecture:


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).

Related issues

Has duplicate darktable - Bug #10751: Manual white balance does not work on the first clickDuplicate12/03/2015

Associated revisions

Revision 4edd1ab1 (diff)
Added by Peter Budai about 2 years ago

Reset static picked color when spot WB has been selected. Fixes #9770

Revision 4603e237
Added by Pascal Obry over 1 year ago

Merge pull request #1608 from peterbud/bugfix-9770

Reset static picked color when spot WB has been selected. Fixes #9770


#1 Updated by Roman Lebedev over 4 years ago

  • Has duplicate Bug #10751: Manual white balance does not work on the first click added

#2 Updated by Richard Wonka almost 4 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.

#3 Updated by Tobias Ellinghaus almost 4 years ago

  • Affected Version changed from 1.4 to git development version
  • % Done changed from 0 to 20
  • Status changed from New to Triaged

#4 Updated by Mikołaj Milej over 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

#5 Updated by Peter Budai about 2 years ago

It looks to me that when you first select sport WB it correctly calculates WB values, but if you switch to another WB and back to spot WB you get back your original camera WB values

#6 Updated by Peter Budai over 1 year ago

  • % Done changed from 20 to 100
  • Status changed from Triaged to Fixed

#7 Updated by Roman Lebedev over 1 year ago

  • Target version set to 2.6.0

Also available in: Atom PDF

Go to top