Created attachment 57378 [details] screenshot Version: 2.0.0 (using KDE 4.6.0) OS: Linux After importing a raw file (cr2), a greenish grid appears in the imported image. screenshot attached. Reproducible: Didn't try OS: Linux (x86_64) release 2.6.35-26-generic Compiler: cc
Can you provide the original file somewhere? If you dont have webspace, send it to me by private mail, I can upload to our test collection. Then we can try to reproduce. Just as well, assuming this is a libraw problem, Alex may want to have the image.
Alex, I CC you for info... Gandalf, Got to Help/Components Info and copy and paste here the contents... Gilles Caulier
Here is the components info: digiKam version 2.0.0-beta3 Exiv2 kann in JP2 speichern: Ja Exiv2 kann in JPEG speichern: Ja Exiv2 kann in PGF speichern: Ja Exiv2 kann in PNG speichern: Ja Exiv2 kann in TIFF speichern: Ja Exiv2 unterstützt XMP-Metadaten: Ja LibCImg: 130 LibClapack: internal library LibExiv2: 0.21 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.6.00 (4.6.0) LibKExiv2: 2.0.0 LibKMap: 2.0.0 LibKdcraw: 2.0.0 LibLCMS: 118 LibPGF: 6.09.44 - internal library LibPNG: 1.2.44 LibQt: 4.7.0 LibRaw: 0.13.0-Beta3 LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble Widget: 0.11.0 (Stable Release) Parallelisiertes Entfernen von Mosaikmustern: Ja Datenbanktreiber: QSQLITE LibGphoto2: 2.4.8 LibKface: 2.0.0 LibKipi: 2.0.0 LibOpenCV: 2.1.0 Libface: 0.1 I'll post a link to the raw file in a couple of minutes when it finished uploading. Gandalf
Here's the link: http://db.tt/bDwe1AX I tried several files, and they all showed the same grid effect. Gandalf
Gandalf, dcraw_emu (LibRaw's test front-end) does not show any grid with default settings. What processing options do you use? To be precise, I've tested with current LibRaw 0.13.1, not with -Beta3, but is should be no sifnificant difference
I decoded the file in rawtherapee, no grid there. Then I played a little with the parameters in digikam and it seems that switching "interpolate RGB as four colors" (or similar, I'm guessing from the German translation here) on creates the effect. If that option is switched off the grid disappears.
You dont need 'four color RGB' on cameras with equal green channels (e.g. Canons). It *may* be useful if green channels are different and you have 4x3 matrix profile for your camera (either built-in in LibRaw or external profile)
(In reply to comment #7) > You dont need 'four color RGB' on cameras with equal green channels (e.g. > Canons). I see, so I'll just switch that off. Even if four color RGB is not needed, the grid was a little unexpected, though.
Yes, this is definitely a bug. Anyway, four-color-rgb itself cannot produce this kind of grid. The problem is due to incorrect interaction between four-channel-rgb and one of new noise correction routines. Could you please specify what noise suppression settings do you use?
> Could you please specify what noise suppression settings do you use? I now tried all available noise reduction routines (none, wavelets, fbdd, cfa line denoise, impulse denoise), and saw the gird with all settings. with fdbb the whole image turns flashy pink, so the grid is pink as well. However, playing with the chromatic aberration option, I got the impression that it is this one which causes the grid when combined with four color RGB.
Alex, anything we need to do here from the digikam side?
Marcel, since LibRaw 0.13.1 the fbdd denoising is disabled if four-color-rgb is turned on because of algorithm incompatibility. So, problem is closed on 2011-02-15. So, you may close this bug.
Thanks Alex for the feedback. Gilles Caulier