[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB
From: |
Chris Cox |
Subject: |
Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB |
Date: |
Tue, 3 Mar 2015 21:10:39 +0000 |
User-agent: |
Microsoft-MacOutlook/14.4.7.141117 |
We published TIFF Technote 3 documenting all of that, but our developer
relations group seems to keep losing it on the website.
(LOOONG story behind that)
Chris
On 2/28/15 4:47 PM, "Bob Friesenhahn" <address@hidden> wrote:
>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 <address@hidden>
>> Date: Friday, February 27, 2015 1:10 PM
>> To: Chris Cox <address@hidden>, "address@hidden
>>address@hidden" <address@hidden>
>> 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 <address@hidden> 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" <address@hidden> 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?
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB,
Chris Cox <=