-
2018.05.09 13:05 "Re: [Tiff] Question about transfer function", by Bob Friesenhahn
-
2018.05.09 14:51 "Re: [Tiff] Question about transfer function", by Larry Gritz
-
2018.05.09 23:39 "Re: [Tiff] Question about transfer function", by Graeme Gill
-
2018.05.11 05:01 "Re: [Tiff] Question about transfer function", by Larry Gritz
-
2018.05.11 09:22 "Re: [Tiff] Question about transfer function", by Graeme Gill
- 2018.05.11 15:51 "Re: [Tiff] Question about transfer function", by Larry Gritz
-
2018.05.11 09:22 "Re: [Tiff] Question about transfer function", by Graeme Gill
-
2018.05.11 05:01 "Re: [Tiff] Question about transfer function", by Larry Gritz
-
2018.05.09 23:39 "Re: [Tiff] Question about transfer function", by Graeme Gill
-
2018.05.09 14:51 "Re: [Tiff] Question about transfer function", by Larry Gritz
- 2018.05.09 13:33 "Re: [Tiff] Question about transfer function", by Graeme Gill
2018.05.11 16:43 "Re: [Tiff] Question about transfer function", by Olivier Paquet
2018-05-11 11:51 GMT-04:00 Larry Gritz <lg@larrygritz.com>:
My much more modest wish would simply be to have a string ColorSpace tag, that names an externally-referenced color configuration. While I understand the desire to support a fully embedded arbitrary transfer function, for most uses in a closed pipeline it seems wasteful to be required to fully embed what may be many MB of LUTs in every image file separately, especially when most files are either a canonical choice like "ACEScg_linear" or "sRGB", or a name in the facility's OCIO configuration.
That's more or less what we chose to do several years ago but on a smaller scale (only a handful of built-in spaces supported). As there was no tag for it, we stuffed the information in TIFFTAG_IMAGEDESCRIPTION. I'm not saying it's great... but embedding the whole thing into each single image is indeed not great either. I like the idea of a dedicated tag to reference an OCIO color space.
Olivier