Open kmaddock opened 7 years ago
Bug confirmed.
With the current gray auto WB, it is impossible to build a correct WB
2 ways
increase "Blue red equalizer" for example to 1.35, then activate "auto", in this case we get
Or used one of the 2 preset "underwater"
When opening a raw file, the White Balance information is not correctly read. The image was shot underwater with custom white balance, so I would guess that the temperature recorded in the Exif data is out of the expected range.
On the white balance tab, I see: Temperature: 1500 Tint: 0.020 Blue/Red: 1.0
In the Exif metadata: Temperature: 9900
Manually setting the white balance temperature to 9900 and Tint to 1.0 corrects the image. Setting the white balance method to Auto fails (sets Temperature: 1500, Tint: 0.020)
Test Files: https://drive.google.com/open?id=0B3VUZ5xw6XpKZWVPc2RRVlhSY0U
RawTherapee Version: Version: 5.1 Branch: 5.1 Commit: f23d70fd Commit date: 2017-05-15 Compiler: gcc 6.3.0 Processor: generic x86 System: Windows Bit depth: 64 bits Gtkmm: V3.22.0 Build type: release Build flags: -m64 -mwin32 -mthreads -Werror=unused-label -Werror=unknown-pragmas -Wno-aggressive-loop-optimizations -std=c++11 -mtune=generic -Werror=unused-label -fopenmp -Werror=unknown-pragmas -Wall -Wno-unused-result -Wno-deprecated-declarations -mwindows -DNDEBUG -msse2 -O3 Link flags: -m64 -mthreads -static-libgcc -mtune=generic -mwindows -s -O3 OpenMP support: ON MMAP support: ON
Downloaded from: http://www.rawtherapee.com/shared/builds/windows/RawTherapee_5.1_WinVista_64.zip
System: Windows 10 Enterprise 64-bit Intel Xeon E5-2630v4 x2 @2.2GHz 64Gb ram