Thanks to all who contributed to this thread, it's been very
educational! As you know, it has spun off another thread about what
tools people are using to build device links, which I'm also very
interested in, but I'd like to bring it back to this thread because
I'm more interested in the mechanics of how these things actually work.
This may be an obvious question, but I have to ask it just so I'm
clear: All this talk of gamut-mapping and gamut compression and color
transforms really only refers to the perceptual rendering intent,
correct? What, if any, advantages do DLPs offer to colorimetric
rendering? Clearly out-of gamut colors have to be dealt with in some
fashion, but do DLPs re-map these better than the 2 profile conversion
method, or is it more a matter of different vendors' "secret sauce"?
On Dec 17, 2007, at 4:40 AM, Jan-Peter Homann wrote:
If your source profile is matrice based RGB-profile like e.g. sRGB,
AdobeRGB, ProPhoteRGB or eci-RGB, the gamut mapping in the
transformation is only depending from the target profile, because
matrice profiles have identical tables for all intents the profile.
I thought matrix based RGB profiles don't have ANY look-up tables,
just sort of a mathematical transform based on the colorants and repro-
curves, which can only give the colorimetric transform. So in that
sense there are identical "tables" (in that there is only the single
transform, which is called on no matter what intent you call for), but
really I actually don't understand how this works, so any illumination
would be greatly appreciated! How do device-links "optimize" RGB-to-
CMYK transforms, considering the above?
Thanks in advance!
–––
Todd Shirley
Urban Studio
New York, NY
212.691.2521
