Roger Breton wrote:
I'm not sure I
follow, here. If I activate Out of Gamut Warning on an aRGB
image while my
convesion options are set to SWOPv2 and RelCol, the areas
that are considered
out of gamut do get displayed.
Roger,
I am using the word tone to
distinguish out of gamut values from out of gamut tints and saturations. I am
making the distinction because it appears as though the gamut warning makes it
also. L* 0 would have to be out of
range of every output profile yet gamut warning does not show this. When
comparing the colour spaces in Colorthink I can see clearly where the lower edge
of the space is. These
shades of colour protrude through the lower perimeter of the ouput space
and are considered out of gamut.
I am not sure why gamut
warning clicks in when it does, for example using the same settings that you
describe * swop v2 from Adobe RGB with relative it shows me that L*13 32, -13
is out of gamut, but everything down from L*13 (L*12, 32, -13 to L*0, 32, -13)
is shown to be in gamut.
I can use soft proofing to see
the maximum shadow of the output space, since it occurs visually on the
screen. Without BPC all tonal
distinctions south of the maximum shadow disappear, The info pallet shows
me the data where the first visual distinction occurs, but gamut warning does
not.
I had assumed, because of the
difference in gamut warning while soft proofing with absolute and relative, that
absolute was showing me the out of range tones, but the logic is inconsistent
and appears to function differently with RGB output and CMYK output profiles.
The only way to truly know for sure would be by applying the gamut warning to
grey scale files but this is not possible.
The same L* value? Then, if you used Monaco Proof to
make the two profiles,
this can only mean that, physically, the two scans are
different to begin
with in terms of RGB data in the highlights. I don't see
any other logical
explanations.
Ok I have rescanned the 4x5
transparency on the Eversmart to produce the exact same highlight value (in lab)
as the Epson scan. Both scans now
indicate L*88 with relative configured in colour settings . The RGB data is of
course different because the files are still in their input profiles. If I
change the colour settings to absolute the Epson file remains the same and the
Eversmart file drops to L*68.
«énigme!»
comme dirait Michel Rivard
Thanks for your help.
Eugene Appert.