[Digikam-devel] [Bug 307313] Digikam uses wrong darkness/saturation values

[Gilles Caulier]

https://bugs.kde.org/show_bug.cgi?id=307313

Gilles Caulier <caulier.gilles at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |caulier.gilles at gmail.com

--- Comment #7 from Gilles Caulier <caulier.gilles at gmail.com> ---
Black Point, from libkdcraw Raw Decoding Settings :

https://projects.kde.org/projects/kde/kdegraphics/libs/libkdcraw/repository/revisions/master/entry/libkdcraw/rawdecodingsettings.h#L269

... Can be enabled through the GUI using right checkbox. If it's not turned on,
it still on default value internally, so 0.

But Black Point value is only passed to libraw decoder only if this option is
turned on. Look this code :

https://projects.kde.org/projects/kde/kdegraphics/libs/libkdcraw/repository/revisions/master/entry/libkdcraw/kdcraw_p.cpp#L221

... just to before print all Raw Decoding Settings values on trace. 

SO : 

- If you turned on this settings and let's it to zero, the behavior is normal.
- if you turned off this settings, well, nothing is passed to libraw. So it's
libraw default value which is used instead ! Also in this case trace will
report value (disabled) but set in GUI. zero by default.

Note : 

In case of digiKam Image Editor, black and white levels options are hideen and
DISABLED by default, due to the availability of post processing adjustments.
In case of RAW Converter kipi-plugins; black and white levels options are
there. There is no post processing adjustments.

To resume, IE raw import tool do not use black and white levels options. both
are disabled in background. Default values from libraw are used here instead.

Gilles Caulier

-- 
You are receiving this mail because:
You are the assignee for the bug.