Bug 187751

Summary:	raw developer gives strange colours when using camera profiles
Product:	[Applications] digikam	Reporter:	Paul Hunt <prhunt>
Component:	ColorManagement-Profiles	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, marcel.wiesweg
Priority:	NOR
Version:	0.9.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:	5.1.0
Sentry Crash Report:

Description Paul Hunt 2009-03-21 00:37:26 UTC

Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    SuSE RPMs

I have colour profiles for my Pentax K10D.  One is "borrowed" from a past Bibble trial, the other is one I made from a colour target, developed in ufraw and profiled using lprof.

Using digikam (0.9.5 stable from Suse builds, Suse 11.0 KDE 3.5.10) I get weird colours from the raw developer tool when using my own profile.  The bibble profile works OK.  My own profile works correctly in ufraw and in rawtherapee.

I will provide a sample PEF with the two profiles on request.

Paul

Comment 1 Paul Hunt 2009-03-28 02:44:41 UTC

It seems that no profiles are working correctly - I am getting colour artefacts eg patches of red where there should be dark shadow.

Is the dcraw colour matrix being used in addition to the colour profiles?  When this was allowed in ufraw, I recall that the combination did not work well.

Paul

Comment 2 Marcel Wiesweg 2009-08-20 23:23:27 UTC

Can you provide me a testcase? It should be clearly visible what is right and what is wrong.

Comment 3 caulier.gilles 2011-12-12 18:35:40 UTC

Paul,

It still valid, with 2.x release ?

Gilles Caulier

Comment 4 caulier.gilles 2013-11-27 13:34:00 UTC

Paul, 

This entry still valid using digiKam 3.5.0 ?
Do you  read Marcel comment #2 ?

Gilles Caulier

Comment 5 caulier.gilles 2015-06-30 08:07:21 UTC

New digiKam 4.11.0 is available :

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

Can you reproduce the problem with this release ?

Comment 6 caulier.gilles 2016-07-15 12:13:00 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