Summary: | wavelets NR tool confuses red and blue | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | S. Burmeister <sven.burmeister> |
Component: | Plugin-Editor-NoiseReduction | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.1.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.1.0 | |
Sentry Crash Report: |
Description
S. Burmeister
2010-01-26 09:27:50 UTC
I agree, sound like something is inverted somewhere. To be sure, can you test with this gimp tool if problem is the same, because it's the same algorithm used (in YCbCr color space) http://registry.gimp.org/node/4235 Thanks in advance Gilles Caulier Ok, I think I got it. Gimp shopws some tooltips and explains that the treshold is the value below which everything is considered noise. I think it might be useful to add this to digikam as well. Further. If I set Y and Cb to 0 I get the full blue noise. Increasing the treshold for Cr does not change anything about that so it seems that digikam has a bug. Increasing Cb gets rid of the blue noise. SVN commit 1080460 by cgilles: CRed and CBlue parameters are inverted BUGS: 224293 M +20 -20 noisereductionsettings.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1080460 |