Henrik and others,
I understand that we have to (shall) print these files (targen/printarg)
with "no" color management that's a given. We feed these numbers
directly to the printer to see what it does with them. That I perfectly
understand. My mistake is unlike tiffgamut that require you to provide a
profile to GIVE MEANING to these number, my program seems to assume this
profile is sRGB by default, that's why it's such a perfect match.
I got carried away for a moment, sorry about that,
Yves
On 7/7/2019 4:12 PM, Henrik Olsen wrote:
Den 7. jul. 2019 kl. 21.02 skrev Yves Gauvreau <gauvreau-yves@xxxxxxxxxxx>:The target does not have a gamut as such. It should not be color managed. It’s
Sorry Graham but I did use -c ProPhoto just to see and used a program like
tiffgamut to see what gamut the target would have (ProPhoto) and it's a perfect
fit with sRGB.
Maybe there is something I didn't see?
device RGB values. Don’t interpret them. Do that with the spectro read and CIE
results of printing the target RGB values as-is, no color management, to learn
how the printer reacts to RGB input with which you can exercise/explore the
available gamut response.
