Summary: | Adjusting 16-bit curves requires 32-bit precision | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Dik Takken <kde> |
Component: | Plugin-Editor-Curves | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 2.6.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Attachments: | Hairy output histogram |
Description
Dik Takken
2012-11-16 14:07:57 UTC
Created attachment 75295 [details]
Hairy output histogram
I just bumped into an older report, Bug #170169, which is basically the same problem. The current work around for Bug #170169 is to convert the image to higher bit depth before performing the operation. For 16-bit images this is not an option, because there is no bit depth greater than 16 bits in DigiKam (CinePaint did have it if I remember correctly). Both problems *should* be fixed when 1. Operations on 8-bit images are always done in 16-bit precision 2. Operations on 16-bit images are always done in 32-bit precision This applies not only to curve correction, but to any operation on pixel values. Curve adjustment is very sensitive to precision though, which makes that the problem really shows in this plugin. Merge both bugzilla files to an unique entry please... Gilles Caulier Main entry for this problem is now Bug #170169. *** This bug has been marked as a duplicate of bug 170169 *** Fixed with https://bugs.kde.org/show_bug.cgi?id=170169 |