[Digikam-devel] [Bug 148382] New: overexposure indication already when fully "saturated"
neundorf at kde.org
Tue Jul 31 04:45:41 BST 2007
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Summary: overexposure indication already when fully "saturated"
Platform: Compiled Sources
AssignedTo: digikam-devel kde org
ReportedBy: neundorf kde org
Version: 0.8.2 (using KDE KDE 3.5.5)
Installed from: Compiled From Sources
in the digikam color tools I can enable a "overexposure indicator", which works good so far.
But it is too optimistic, it seems to only consider pixels as overexposed if they really went beyond the 255 count due to some actions in digikam. They should already be marked as overexposed if one channel hits the 255, because this means that this channel had at least 255, so the color has been lost for this pixel.
The images coming from my camera don't go up to 255, they stop at 254 (I think leaving 0xff out as valid pixel value may be the case for many cameras), so I'd say the threshold shouldn't be 255, but 254.
It would also be nice if this would work already in the thumbnail gallery, so that you can see it already in the overview where the bad images are.
More information about the Digikam-devel