From: Udi F. <udi...@gm...> - 2007-01-28 23:22:50
|
Hi, I'm trying to implement a proofing profile option into UFRaw, but there seem to be some missing functionality in lcms. At the moment the user can choose an input profile and an output profile. In addition the user can make some luminosity and saturation corrections, which are implemented using an intermediate profile. UFRaw creates a transformation from all these profiles using the cmsCreateMultiprofileTransform() function. The problem is that I don't know how to incooporate a proofing profile into this. The only thing I can do is use cmsCreateProofingTransform() as long as there are no luminosity/saturation corrections. Once the user applies such corrections he will get a warning that proofing is disabled. I seem to be missing a cmsCreateMultiprofileProofingTransform() function in lcms. Is there an indirect way to implement such a functionality? Am I making some wrong assumptions? Any help would be welcome, Udi P.S. I sent an e-mail about this issue to this mailing-list a few month ago and did get any replies. |
From: Kai-Uwe B. <ku...@gm...> - 2007-01-29 13:26:29
|
Hello Udi, you are right a mixing of profiles in a chain together with a proofing profile has not an own function. Nethertheless there are some workarounds possible. You may basically create a cmsCreateMultiprofileTransform, convert to a device link with cmsTransform2DeviceLink and use this in the proofing transform with cmsCreateProofingTransform. For a working example you could look at the CinePaint code. It may help you a bit further: app/cms.c cms_create_transform(). kind regards Kai-Uwe Behrmann -- development for color management www.behrmann.name + www.oyranos.org + www.cinepaint.org Am 29.01.07, 00:22 +0100 schrieb Udi Fuchs: > Hi, > > I'm trying to implement a proofing profile option into UFRaw, but > there seem to be some missing functionality in lcms. > > At the moment the user can choose an input profile and an output > profile. In addition the user can make some luminosity and saturation > corrections, which are implemented using an intermediate profile. > UFRaw creates a transformation from all these profiles using the > cmsCreateMultiprofileTransform() function. > > The problem is that I don't know how to incooporate a proofing profile > into this. The only thing I can do is use cmsCreateProofingTransform() > as long as there are no luminosity/saturation corrections. Once the > user applies such corrections he will get a warning that proofing is > disabled. > > I seem to be missing a cmsCreateMultiprofileProofingTransform() > function in lcms. Is there an indirect way to implement such a > functionality? Am I making some wrong assumptions? > > Any help would be welcome, > Udi > > P.S. I sent an e-mail about this issue to this mailing-list a few > month ago and did get any replies. > |