From: <ma...@li...> - 2001-11-13 15:58:16
|
Hi, > So if I undrestand well : > in the first case the result color is the result of a transform between > input and monitor or a specific color (if I use cmsSetAlarmCodes(int r, int > g, int b) if the color is out of gamut of the printer device. > (What I want) > in the second case the the result is the same except the color seen on the > monitor is the same as the one seen on the paper > Yes, that is. It works in such way assuming then you would need only one transform.If you don't give those flags, then the result is the image viewed on monitor. If you give flags and printer profile, you can check the gamut of printer or emulate printer output. Giving no flags and printer profile = NULL is same that cmsCreateTransform(). cmsCreateProofingTransform() is somehow a "superset" of cmsCreateTransform() Regards, Marti. ----- Original Message ----- From: "Armindo Da Silva" <tec...@wa...> To: "Martí Maria" <ma...@li...> Sent: Tuesday, November 13, 2001 12:20 PM Subject: Re: [Lcms-user] Profing > > > - Check gamut to see if a color is reproducible by a device. This always > works > > - Emulate a device. For example: See how will look a image when printed > > whithout printing. Printer profiles has gamut remapping, and thus, could > > change colors. This works only if adequate tag is present. > > So if I undrestand well : > in the first case the result color is the result of a transform between > input and monitor or a specific color (if I use cmsSetAlarmCodes(int r, int > g, int b) if the color is out of gamut of the printer device. > (What I want) > in the second case the the result is the same except the color seen on the > monitor is the same as the one seen on the paper > > > > > > |