On samedi 01 mars 2008, Kai-Uwe Behrmann wrote:
> Hope some ascii is ok:
Yes, nice job!
> [...]
> The first shows the normal displaying of a usual image.
> The second tries to simulate the inkjet colours.
> The thierd does the usual separation into print colours.
Ok.
> I hope this helps in understanding that proofing is almost always bound
> to using a monitor for simulating a different device.
> As always, exceptions belong to real live.
I think I found my error: I just inverted the profiles used in the
cmsCreateProofingTranform() function. The outputProfile is the monitor
profile, and the proofingProfile is the printer one. Is that right?
Then, The intent is the one I would jave used to print (third case), and
the proofingIntent is the intent used to simulate on screen. It seems that
names does not match, that's why I made a mistake.
Let me summurize, to be sure. Say my source profile is sRGB, the
destination profile (press) is ISOcoated, and my monitor profile is
A901HT:
1) cmsCreateTransform(sRGB, RGB, A901HT, RGB, INTENT_PERCEPTUAL)
2) cmsCreateTransform(sRGB, RGB, A901HT, RGB, INTENT_PERCEPTUAL,
ISOCoated, INTENT_ABSOLUTE_COLORIMETRIC)
3) cmsCreateTransform(sRGB, RGB, ISOCoated, CMYK, INTENT_PERCEPTUAL)
Is it OK?
PS: I just received you second e-mail, so I think it is ;o) And yes, I was
confused as you were.
--
Frédéric
http://www.gbiloba.org
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Lcms-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lcms-user
