Bug 334160

Summary: Wrong colors when importing CR2 with custom camera profile
Product: [Applications] digikam Reporter: Matthias Welwarsky <matze>
Component: Plugin-RawImport-NativeAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles
Priority: NOR    
Version First Reported In: 4.0.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
URL: https://drive.google.com/folderview?id=0B-2EzyUZBAHmb1d5VlJwNEtPSFk&usp=sharing
Latest Commit: Version Fixed/Implemented In: 5.1.0
Sentry Crash Report:

Description Matthias Welwarsky 2014-04-30 21:25:46 UTC 
Importing a CR2 file using a custom camera profile creates an image with strong color tint (red'ish). The same image converted to tiff using draw_emu from libraw-tools appears correct.

The profile was generated using argyllcms scanin/colprof.

Reproducible: Always

Steps to Reproduce:
1. In digikam raw import dialog, set camera profile to "custom" and use the ICC profile _MG_2289.icc from the demo URL and workspace color profile to the actual workspace color profile
2. import the file _MG_2289.CR2 from the demo URL
3. compare result with the same file converted with dcraw_emu using the following command:
dcraw_emu -w -q 8 -o 2 -M -T -p _MG_2289.icc _MG_2289.CR2
Actual Results:  
The images don't match. The file created in digikam has a strong red'ish color tint

Expected Results:  
digikam generated image is expected to look identical to the image created on the commandline
Comment 1 caulier.gilles 2015-05-10 08:20:43 UTC 
Matthias,

It's reproducible using last digiKam 4.9.0 with last libraw and last lcms2 ?

Gilles Caulier
Comment 2 caulier.gilles 2015-05-16 10:22:02 UTC 
Mathias,

Did you seen my previous message ? digiKam 4.10.0 is just release...

Gilles Caulier
Comment 3 caulier.gilles 2015-06-25 08:56:05 UTC 
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?
Comment 4 caulier.gilles 2015-08-17 11:26:19 UTC 
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier
Comment 5 caulier.gilles 2016-07-15 13:12:26 UTC 
With digiKam 5.0.0, this problem is not reproducible.
I close this file now. Don't hesitate to re-open if necessary.
Gilles Caulier