[argyllcms] Re: Gamut mapping?
- From: Graeme Gill <graeme@xxxxxxxxxxxxx>
- To: argyllcms@xxxxxxxxxxxxx
- Date: Mon, 11 May 2020 13:26:17 +1000
Yves Gauvreau wrote:
if I understand correctly, creating a device link profile as per the scenario
"Image
dependent gamut mapping using device links" one can't do much with it beside
printing the
resulting image without color management right?
Yes. The conversion is (typically) between two device colorspaces, and if the
destination space is the printers space, then it only makes sense to send
it directly to the printer.
(Of course the destination could be a pseudo-device-independent space like sRGB
etc.)
Is there another way to create a profile made using the source gamut that
represents the
gamut of the images themselves? I see colprof also as the possibility of
using an image
gamut, would there be an advantage to create an output profile that way
instead? How so?
The advantage is that it is a device profile, and so can be used in workflows
that don't know how to handle device links. Other than that there are several
disadvantages - the precision and smoothness is worse, because the overall
transform is the result of the concatenation of up to two cLUT tables though
a space (PCS) that is much larger than either the source or destination space
(and hence the cLUT is less densely sampled and hence less efficient), and the
source space the gamut mapping is setup for is disconnected with the profile,
which means that there is the possibility of a mix-up where the wrong source
profile gets used with it.
graxx@xxxxxxxxxxxx wrote:
Device-link profiles don't have 'special' or additional capabilities beyond
merging an Input and an Output profiles together.
As explained above, they are smoother and more accurate and avoid the
possibility
of getting the wrong source space encoding.
Cheers,
Graeme Gill.
Other related posts:
