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

[S. Burmeister]

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

--- Comment #6 from S. Burmeister <sven.burmeister at gmx.net> ---
digikam(29476)/KDCRAW KDcrawIface::KDcraw::loadFromLibraw:
-- RAW DECODING SETTINGS --------------------------------
-- autoBrightness:          false
-- sixteenBitsImage:        true
-- brightness:              1
-- RAWQuality:              0
-- inputColorSpace:         0
-- outputColorSpace:        1
-- RGBInterpolate4Colors:   false
-- DontStretchPixels:       false
-- unclipColors:            0
-- whiteBalance:            1
-- customWhiteBalance:      6500
-- customWhiteBalanceGreen: 1
-- halfSizeColorImage:      false
-- enableBlackPoint:        true
-- blackPoint:              0
-- enableWhitePoint:        false
-- whitePoint:              0
-- NoiseReductionType:      2
-- NoiseReductionThreshold: 300
-- enableCACorrection:      false
-- caMultiplier:            0, 0
-- medianFilterPasses:      0
-- inputProfile:            ""
-- outputProfile:           ""
-- deadPixelMap:            ""
-- whiteBalanceArea:        QRect(0,0 0x0)
-- dcbIterations:           -1
-- dcbEnhanceFl:            false
-- eeciRefine:              false
-- esMedPasses:             0
-- NRChrominaceThreshold:   100
-- expoCorrection:          false
-- expoCorrectionShift:     1
-- expoCorrectionHighlight: 0
---------------------------------------------------------

Is the black point the black level? If so digikam does set it to 0 as it seems.

AFAIK there is no GUI element to set the black level to 0 hence it must be
something digikam does internally.

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