- This topic has 63 replies, 5 voices, and was last updated 9 months, 3 weeks ago by
.
-
Posts
-
Every time I mentioned any kind of LUT i was referring to the XYZ LUT, I may have used the wrong terminology.
= mesh-like description of display, on both ways, ok. I assumed the other since it is the common “wrong labeling” for new users in this forum. my fault.
The RGB2RGB 3DLUT display profile I’m describing doesn’t need to know the source color space, because it doesn’t map RGB pixels from the input TIFF directly. These first get converted to XYZ via the input ICC profile (sRGB, AdobeRGB, complex profile of a scanner, …) then to a fixed RGB space via a matrix.
Then is not a lut3D rgb 2 rgb. it not the full pipeline from RGB colorspace A to RGB colorspace B. It is just 1/2 half of any color management pipeline, it is missing the source or the destination, depending on which part are you reading.
Summary: a display profile or printer profile does not and cannot store a lut3d for colorspace transformations because it is only a description of a device. The TO or the FROM.
That’s why it is easier to explain to newcomers this table/lut profiles as a mesh (XYZ<->RGB) rather than use LUT because most of them will link this name to “LUT3D” seen somewhere else.
… but you’ll need desperately want to start a discussion about this obvious statement. Me not.
