Am 23.11.2012 11:28, schrieb marti.ma...@littlecms.com:
> Kai-Uwe Behrmann escribió:
>
>> However cmsSetAdaptationState() works only globally, which makes not so
>> much sense for displaying multiple documents with different settings at
>> the same time. A API for setting the adaption state per tr
On 23 November 2012 10:32, wrote:
>> cmsUInt32Number intents[2] = { INTENT_ABSOLUTE_COLORIMETRIC,
>>INTENT_ABSOLUTE_COLORIMETRIC };
> Ok, this function allows you to specify intents *per profile*, that means
> you can use relative colorimetric when going from RGB to PC
Hi,
> As an aside, I did wonder about the documentation for
> cmsCreateExtendedTransform.
>
> cmsCreateExtendedTransform(cmsContext ContextID,
>cmsUInt32Number nProfiles, cmsHPROFILE hProfiles[],
>cmsBool BPC[],
>cmsUInt32Number Intents[],
>
Kai-Uwe Behrmann escribió:
> However cmsSetAdaptationState() works only globally, which makes not so
> much sense for displaying multiple documents with different settings at
> the same time. A API for setting the adaption state per transform would
> be very appreciated.
Check cmsCreateExtendedT
On 22 November 2012 22:38, Marti Maria wrote:
> - use cmsSetAdaptationState(0) prior transform. This is very important in
> order to get the white point from CHAD
Ahh, this is the bit I didn't know about.
> Hope that works to you
Using cmsCreateExtendedTransform allows me to do this without set
