can you describe how ColorThink computes the gamut ?
- for instance, if it computes it from the Perceptual A2B table,
it won't see the gamut assumed by the B2A table.
You can try using ArgyllCMS iccgamut -w -f b -ip to get a view of
the gamut assumed by the B2A table.
ColorThink probably shows only the A2B tables, I don't know for sure. I tried
exactly what you suggest here with iccgamut and I can see the gamut is similar
to what I was expecting.
(As noted in the documentation for colprof, gamut compression/expansion
is only applied to the B2A tables.
See<https://www.argyllcms.com/doc/colprof.html#s>
and<https://www.argyllcms.com/doc/iccgamutmapping.html>
ICCV4 PRMG type behavior is different, and is applied to both A2B and
B2A tables.)
Yes I saw that, it's probably the reason why I can see a different gamut with
version 4 profiles.
I probably mist interpreted the use of -nP flags then, I thought it would allow
the gamut mapping to apply to the A2B table as well.
I noticed a difference between the gamut of the sRGB Appearance profile and the
sRGB Preference profile. I use the Appearance version because it bring the
colors more or less inside the standard sRGB gamut without clipping I assume
and I convert it to the standard sRGB after to publish it while the Preference
version is a much larger gamut probably best used for wide gamut printing.
Basically, all my images are in ProPhoto (almost always) and I want to show them on my
wide gamut monitor with minimal clipping or better yet, none at all, would it suffice to
create a cLut profile for my display and can I setup a default rendering intent other
then just perceptual, say lp "Luminance Preserving Perceptual".
If I understand correctly, creating a cLut profile for my display with -t lp
and -Z p will create a luminance preserving perceptual (or any other) and it
will be used by default (-Z p), right?
In a situation like mine, what would you suggest I use as the source profile or
gamut?
Regards,
Yves
