[Digikam-devel] [Bug 144155] wrong(?) histogram y-axis when blown-out over/underexposure

Arnd Baecker arnd.baecker at web.de
Wed Jun 13 17:46:53 CEST 2007


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=144155         




------- Additional Comments From arnd.baecker web de  2007-06-13 17:46 -------
Created an attachment (id=20849)
 --> (http://bugs.kde.org/attachment.cgi?id=20849&action=view)
example images and their histograms

I did a more thorough check of the patch, and find quite
a few cases, where it does not work optimally:
(A) too much is cut-off
(B) not enough is cut-off to the right
(C) too much is cut-off
(D) too much is cut-off

Maybe one should only use the largest 10% and lowest 10%
to detect blown out high-lights and shadows and
regard everything else as normal contents?

Unless there are any values which are being clipped, I would
suggest to always leave 2-3% of the height just blank,
so that it is clear, when something is clipped.

If you revise the patch, I am perfectly happy to test it again
(maybe we can still sneak it into the release candidate for 0.9.2 ;-)


More information about the Digikam-devel mailing list