The Canon EOS 5D Mark III should be supported since digiKam 2.7.0, but in 2.9.0 it is still _not_ working. If you open a image it gets a very strong pink color and the image is just completely unusable. When i click on Color --> Auto-Correction --> Equalize, that helps on some photos but not on all and the colors are not always correct.
Any screenshots and files to test with?
Sure sure, but i will send you rather this studio shot from dpreview as this was taken under controlled studio environment with color checker and lot of stuff http://movies.dpreview.com.s3.amazonaws.com/canon_eos5dmkiii/5D3_5199.CR2.zip The embedded JPEG shows fine and correct, but as soon you go to [F4] (the edit function or you just use showFoto) all is pink This is how it looks like to me after opening with showFoto http://img6.imagebanana.com/img/caij747j/pink.jpg
Even libraw 14.6 from the current digikam git seems to not handle this correctly. I do not have colour management available hence it cannot be the cause. dcraw -v -w 5D3_5199.CR2 produces a correct ppm image. dcraw 9.16
So is this a bug in libraw? As it works with the current RawTherapee, maybe the Color Profile can be taken from them?
Digikam does not decode RAW on its own. And since dcraw works I'd guess that libraw is a good candidate. And indeed, libraw only supports the Mark III only with 0.14.7 and not 0.14.6 which is what digikam ships. Thus you will have to wait until the Help menu > Components information shows at least 0.14.7 for libraw. http://www.libraw.org/download#changelog LibRaw 0.14.7 (27-06-2012) Imported dcraw 9.15 (1.449): New cameras supported: Canon 5D Mark III, G1 X, 1D X and Powershot SX200; Nikon D4,D800/D800E and D3200; Fuji X-S1 and HS30EXR; Casio EX-Z8; Olympus E-M5; Panasonic GF5; Sony NEX-F3, SLT-A37 and SLT-A57; Samsung NX20 and NX210; Support for updated Samsung NX200 firmware. Makefile.msvc: easy additional compiler flag editing.
a few days in the past the raw conversion on my digikam version was switch to 'bilinear' and results where awful with a 7d image. switching back to 'amaze' restored the good colors. may be you have the same problem
With digiKam 3.0.0, no problem : http://www.flickr.com/photos/digikam/8059884310/sizes/o/in/photostream/ Gilles Caulier
What Version oft libraw do you use?
Just saw it in the Screenshot. Current gibt only has 0.14.6 while you already use 0.15. This just confirms my findings.
Im a bit confused The Homepage of digikam tells for Release 2.7.0 In this release, for a better RAW files processing support, Libraw library have been imported to libkdcraw with last 0.14.7 release. New cameras are now supported: Canon 5D Mark III, G1 X, 1D X and Powershot SX200; Nikon D4,D800/D800E and D3200; Fuji X-S1 and HS30EXR; Casio EX-Z8; Olympus E-M5; Panasonic GF5; Sony NEX-F3, SLT-A37 and SLT-A57; Samsung NX20 and NX210. Doesnt that mean that in 2.7.0 it should be included now i have digiKam 2.9.0, so it should be defently there here are my version: libraw 0.14.7 libkdcraw 4.9.2 dcraw 9.16 digikam 2.9.0 Why is the support not there? Is it a wrong information in the News?
Ok if i use the Version Information in the digiKam application itself it shows the following: Version of KDcraw: 2.1.0 Version of LibRaw: 0.14.6 5D Mark III is not listet there. Can anyone tell why digiKam 2.9.0 have libraw 0.14.6 when it should have 0.14.7 since 2.7.0?
libraw is included in libkdcraw, published with KDEGraphics components. Libkdcraw is managed by digiKam team. When we updated libkdcraw, it appears in digiKam log. digiKam tarbal include libkdcraw but pckager prefert to use official release from KDE. This is why you have an old release of libraw. Gilles Caulier