Re: [Lcms-user] Out of Gamut alarm color

[Marti Maria]

Hi Dave,   Which version are you using? gamut warning is set by default to gray in latests versions, so I'm afraid you are using an old version. And the bug you are reporting seems to belong to an old version too.   If so, please consider to upgrade to 1.11, Gamut checking and softproofing is way better. And you also have new features like black point compensation and postscript generation.   If you are already using 1.11, please tell me... I would then check the gamut warning logic twice.   Best regards, Marti Maria The little cms project http://www.littlecms.com [EMAIL PROTECTED]       ----- Original Message ----- From: Dave Williss To: [EMAIL PROTECTED] Sent: Thursday, November 06, 2003 9:51 PM Subject: [Lcms-user] Out of Gamut alarm color I have a question about the out-of-gamut alarm settings. One of our documenters has been given the task of working up a color illustration that demonstrates color profile support in our software (which we now do thanks to lcms :-)   One of the features that I implemented was the ability to do soft proofing and turn on an out-of-gamut alarm.  The documenter turned the option on and a lot of stuff turned red as expected (maybe more than expected, but that's just the way it is).  However, when she changed to use a different profile, some of the stuff that had been red turned purple instead. Further investigation shows that it's combining the out-of-gamut alarm color with the image color (which was blue).  We found one area that had been bright white where you could see shades of pink with the alarm on. It's as if out-of-gamut isn't a black-and-white state (or black-and-red in this case) but that there are levels of out-of-gamma-ness.   Could somebody please explain this?  We need to know how to explain it to the end users in the documentation.    -- Dave Williss ------ Meddle not in the affairs of dragons,    for you are crunchy and taste good with catsup