Re: OpenEXR files with nonlinearly encoded RGB
Bob Friesenhahn <[email protected]> Sat, 28 Feb 2015 18:47:21 -0600 (CST)
| Newsgroups | gmane.comp.video.openexr.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 27 Feb 2015, Chris Cox wrote: > Well, that's a bug that only Nuke can fix. I wonder if it would help if Adobe would release an official specification for float in TIFF as well as official sample files? ;-) There are a number of independent interoperable implementations based on the unofficial Adobe draft and sample files. Bob > > Chris > > > From: Larry Gritz <[email protected]> > Date: Friday, February 27, 2015 1:10 PM > To: Chris Cox <[email protected]>, "[email protected] [email protected]" <[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]> 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]> 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] > https://lists.nongnu.org/mailman/listinfo/openexr-devel > > > -- > Larry Gritz > [email protected] > > -- Bob Friesenhahn [email protected], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/