[Bug 279255] New: white balance method "camera" does not use the camera's values

[Alex Tutubalin]

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

--- Comment #18 from Alex Tutubalin <[hidden email]> ---
BTW, auto-maximum does not affects 'darknes'. This option auto-corrects
'maximum' only.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[S. Burmeister]

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

--- Comment #19 from S. Burmeister <[hidden email]> ---
Created attachment 74120
  --> https://bugs.kde.org/attachment.cgi?id=74120&action=edit
dcraw settings

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[S. Burmeister]

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

--- Comment #20 from S. Burmeister <[hidden email]> ---
Created attachment 74121
  --> https://bugs.kde.org/attachment.cgi?id=74121&action=edit
raw settings 2

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[S. Burmeister]

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

--- Comment #21 from S. Burmeister <[hidden email]> ---
According to comment 4 using "-w" for dcraw and "-w -c 0" should give the same
values. This is not the case with Correct false colors in highlights disabled.
(see screenshots)

According to comment 2 if a darkness of 15 is set to 0 the value has to be
subtracted form the saturation. Digikam does not do so.

Hence to close this report digikam/"libs it uses" has to decide whether it
wants to use a darkness of 0 if it is actually 15 or not. If it wants to use 0
it should subtract 15 from the saturation, as it did previously.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[S. Burmeister]

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

--- Comment #22 from S. Burmeister <[hidden email]> ---
The first sentence of my previous comment refers to digikam vs. dcraw. not
dcraw emu.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[S. Burmeister]

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

--- Comment #23 from S. Burmeister <[hidden email]> ---
I think I understood now what you meant. This report is about white balance and
using wrong darkness and saturation values has nothing to do with white balance
but needs a new report.

The report that deals with subtracting darkness from saturation is bug 307313.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #24 from Gilles Caulier <[hidden email]> ---
Sven,

This file still valid ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WAITINGFORINFO
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #25 from Gilles Caulier <[hidden email]> ---
Sven,

We need a fresh feedback here, using last digiKam 4.2.0, and Libraw 0.16.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #26 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

--- Comment #27 from Gilles Caulier <[hidden email]> ---
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |FIXED
   Version Fixed In|                            |5.1.0

--- Comment #28 from [hidden email] ---
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel