Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB

2015-02-27 Thread Kai-Uwe Behrmann
Am 27.02.2015 um 15:44 schrieb Elle Stone: On 02/23/2015 02:42 PM, Kai-Uwe Behrmann wrote: LCMS is just one CMM, with its prefered set of min and maximal values for certain colour spaces. I could never find it convincing to have CIE*L expressed in % in LCMS, the same goes for Cmyk - a printing

Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB

2015-02-27 Thread Chris Cox
No, 32 bit float is 32 bit float. And TIFF supports 16 (half, same as EXR), 24, and 96 bit float formats as well. Chris On 2/27/15 6:44 AM, Elle Stone ellest...@ninedegreesbelow.com wrote: Are there differences in the number of stops that can be held in 32-bit floating point tiffs vs

Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB

2015-02-27 Thread Elle Stone
On 02/27/2015 03:24 PM, Chris Cox wrote: No, 32 bit float is 32 bit float. And TIFF supports 16 (half, same as EXR), 24, and 96 bit float formats as well. Chris, thanks! I've been wondering about that for a while, whether 32-bit floating point OpenEXR somehow was able to accomodate more stops

Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB

2015-02-27 Thread Larry Gritz
TIFF spec addenda may support fp16, but Nuke (among many other apps) doesn't read it correctly, which makes it nearly useless on a VFX pipeline. On February 27, 2015 12:24:44 PM PST, Chris Cox c...@adobe.com wrote: No, 32 bit float is 32 bit float. And TIFF supports 16 (half, same as EXR),

Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB

2015-02-27 Thread Chris Cox
Well, that's a bug that only Nuke can fix. Chris From: Larry Gritz l...@larrygritz.commailto:l...@larrygritz.com Date: Friday, February 27, 2015 1:10 PM To: Chris Cox c...@adobe.commailto:c...@adobe.com, openexr-devel@nongnu.orgmailto:openexr-devel@nongnu.org