Re: OpenEXR files with nonlinearly encoded RGB

Chris Cox <[email protected]> Fri, 27 Feb 2015 21:58:50 +0000
Newsgroups gmane.comp.video.openexr.devel
Message-ID <D1162852.CD8D%[email protected]>
Well, that's a bug that only Nuke can fix.

Chris


From: Larry Gritz <[email protected]<mailto:[email protected]>>
Date: Friday, February 27, 2015 1:10 PM
To: Chris Cox <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]> [email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB

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 <[email protected]<mailto:[email protected]>> 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





On 2/27/15 6:44 AM, "Elle Stone" <[email protected]<mailto:[email protected]>> wrote:

Are there differences in the number of stops that can be held in 32-bit
floating point tiffs vs 32-bit floating point OpenEXR images?


________________________________

Openexr-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.nongnu.org/mailman/listinfo/openexr-devel

--
Larry Gritz
[email protected]<mailto:[email protected]>

_______________________________________________
Openexr-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/openexr-devel