Project

General

Profile

Bug #8501

Incorrectly stored white balance in style

Added by tetaberta - about 8 years ago. Updated about 7 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
General
Target version:
Start date:
Due date:
% Done:

100%

Affected Version:
System:
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Steps to reproduce:
  • open an image in darkroom
  • adjust white balance (temperature in)
  • create new style from history stack and check "white balance (off)"
  • Now the Ticket #8499 kicks in - I cannot switch to a different image - I have to restart darktable
  • open some image in darkroom
  • apply the style
    The applied white balance (temperature in) has some huge value ~9000 K which seems to be unrelated to the desired temperature ~4800 K.

I suspect there might be a problem with some configuration files. This problem didn't happen until yesterday, when I was processing a folder with ~200 images.

Reinstalling darktable didn't help
It is reproducible in Natty package from pmjdebruijn ppa
and in the git version 0.8+469~g78ed19f
Ubuntu Natty

History

#1 Updated by tetaberta - about 8 years ago

I tried removing ~/.config/darktable/ but it didnt help

#2 Updated by tetaberta - about 8 years ago

So I have found out, that the problem is most prominent, when then profile is created on an image taken with flash and applied to an image without flash. Is it related to the camera white balance?

#3 Updated by Pascal de Bruijn about 7 years ago

  • Status changed from New to Fixed

Check "white balance (off) can't be done. White balance can't be turned off (at least not in recent versions).

When I take a new image, go into darkroom mode, changing "temperature in" to a lower value (making the image blue), then creating a style only checking the "white balance (on)" box. Then going back to lighttable mode, and applying the style to another image, it turns blueish too.

Testing using 1.0+50~g3ac07d4 (darktable-1.0.x branch).

Feel free to re-open this bug if you can reproduce this issue using a recent version of darktable.

#4 Updated by tetaberta - about 7 years ago

Indeed, this is fixed. Thanks

Also available in: Atom PDF