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

[S. Burmeister]

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

            Bug ID: 307313
          Severity: normal
           Version: 3.0.0
          Priority: NOR
          Assignee: digikam-devel at kde.org
           Summary: Digikam uses wrong darkness/saturation values
    Classification: Unclassified
                OS: Linux
          Reporter: sven.burmeister at gmx.net
          Hardware: Other
            Status: UNCONFIRMED
         Component: libkdcraw
           Product: digikam

According to bug 279255 there are two ways to use the values darkness and
saturation. Either ones uses them as is, e.g. darkness 15 and saturation 4095,
this is what dcraw reports.

Alternatively (comment 2 bug 279255) darkness can be set to 0 if it is
subtracted from the saturation value, i.e. 4095 becomes 4080. In former
versions digikam did so.

Currently it sets the darkness from 15 to 0 but forgets to subtract it from the
saturation value.

Reproducible: Always

Steps to Reproduce:
Issue dcraw -w -v on a RAW picture and check the values for darkness and
saturation.

Run digikam, open a RAW file in the editor and use the demosaicing tool. 
Actual Results:  
Check digikam's debug output and notice that it uses a darkness of 0 but does
not subtract the darkness value reported by dcraw from the saturation.

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