|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
In a message dated 10/25/00 9:23:19 PM, firstname.lastname@example.org writes: >Thanks for that explanation, it's finally made the problem with > >scanner based profiling clear to me. My Agfa T-2500 software does > >allow specing the source space, and here the profiles are *much* > >better than with any other setting. Profiles made any other way > >suffer from inaccuracies, cyan skies being the most serious and > >offensive of the color problems. How many of the Cyan Sky Sufferers are on Windows? I have been looking at sRGB's abilities (thats too kind; lets say inabilities) to convert via LAB recently, and it sounds suspiciously similar to this issue. I have proposed previously that any type of "sRGB keyhole" in a workflow would limit color range to the sRGB gamut; to that I would now add that any clipping to an sRGB gamut or any assumed sRGB source space would be likely to cause catastrophic color changes when using profile conversions. Perhaps the name of this phenomenon should not be Matchlock Cyan Skies, but ICM2 Cyan Skies... C. David Tobie Design Cooperative CDTobie@designcoop.com - Turn off HTML mail features. Keep quoted material short. Use accurate subject lines. http://www.leben.com/lists for list instructions.
[Photo] [Yosemite News] [Yosemite Photos] [Scanner] [Gimp] [Gimp] Users