From kde-bugs-dist Wed Apr 30 21:25:46 2014 From: Matthias Welwarsky Date: Wed, 30 Apr 2014 21:25:46 +0000 To: kde-bugs-dist Subject: [digikam] [Bug 334160] New: wrong colors when importing CR2 with custom camera profile Message-Id: X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=139889315032204 https://bugs.kde.org/show_bug.cgi?id=334160 Bug ID: 334160 Summary: wrong colors when importing CR2 with custom camera profile Classification: Unclassified Product: digikam Version: 4.0.0 Platform: Compiled Sources URL: https://drive.google.com/folderview?id=0B-2EzyUZBAHmb1 d5VlJwNEtPSFk&usp=sharing OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Color Management Assignee: digikam-devel@kde.org Reporter: matze@welwarsky.de 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 -- You are receiving this mail because: You are watching all bug changes.