Created attachment 52353 [details] Blown out image with USM radius < 1 Version: 1.4.0 (using Devel) OS: Linux When editing a Canon EOS 7D CR2 image and trying to use a radius smaller than 1, the the image "blows out". See the attached screenshot for an example. Because of the size of the 7D RAWs of 20-30 MB I will not attach an image file. In case such a file is needed to reproduce the error I' ll find a way to provide such a file, evt. by creating a small oder medium sized RAW which is supported by the 7D. Reproducible: Always Steps to Reproduce: digikam -> edit Canon 7D RAW image -> Sharpen -> USM -> Select Radius < 1
I did some further testing: - the problem definitively does not exist with RAWs of my 350D, only with the 7D - the problem also exists using S-RAW, M-RAW and even the JPEG files - every time I press the "Try" button when editing M-RAW and S-RAW the image changes from blown out (similar to the screen shot in the attachment) to very dark and back to blown out, this cannot be seen using the RAW and JPEG version of the image - the blow out of the JPEG version has more saturation left over I provided all four types of images on my server at http://www.fietze-home.de/digikam/ The CR2s are S-RAW (#1417), M-RAW (#1418) and RAW (#1420).
The same thing happens using the BQM, so this seems to happen within the plugin, not the editor.
This can be reproduced on other machines as well. This time an openSUSE 11.2 i586.
Update: Still valid for digikam 2.3.0 from the openSUSE 11.4 KDE Updated Apps repository, x86_64 (didn't test it on i586). All radii smaller than 1.00 blow out the image, already starting at a radius of 0.99.
*** Bug 151172 has been marked as a duplicate of this bug. ***
Roman, This file still valid using last digiKam 4.10.0 ? Gilles Caulier
Sorry for the delay, but I had to upgrade to openSUSE 13.2 first. The bug is fixed in digikam 4.10.0