RE: Matchlock Cyan Skies

[jowilcox <jowilcox@blue.weeg.uiowa.edu>]

<x-charset ISO-8859-1>>===== Original Message From epson-inkjet@leben.com =====
>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

David,
I am on WinME. I profile with Epson Perfection 1200 and ProfilerRGB. My 
working space is AdobeRGB. Using the twain driver, I can build a profile which 
is OK and I usually tweak sliders for improved saturation and often a little 
push to R. Skies are a little too cyan for my taste, particularly compared to 
what I see on my light table.  I tweak the blues in PS and re-print.  That's 
my life with Profiles.  It's a little hassle, but it allows me to experiment 
with a great many materials.

Vuescan as you may know is now working with Epson flatbeds and has the 
capability of scanning the image into various spaces.  Instead of scanning the 
target with the Epson twain, I used Vuescan with no color balance correction 
to scan the target into AdobeRGB.  The resulting ProfilerRGB profile without 
slider manipulation was in almost all respects *perfect*.  Wonderful color 
balance and saturation.  But the skies looked like a swimming pool.

Where would sRGB impact this scenario?

Joel Wilcox 

-
Turn off HTML mail features. Keep quoted material short. Use accurate
subject lines. http://www.leben.com/lists for list instructions.

</x-charset>