|
From: | Elle Stone |
Subject: | Re: [Openexr-devel] OpenEXR files with nonlinearly encoded RGB |
Date: | Mon, 23 Feb 2015 11:40:58 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
On 02/23/2015 11:16 AM, Kai-Uwe Behrmann wrote:
Am 20.02.2015 um 21:45 schrieb Elle Stone:* OpenEXR is a data container. * Nothing in the OpenEXR specifications forbids reading or writing non-linearly encoded RGB data. * After opening the file in an ICC profile color managed editing application, it should be up to the user to assign the correct ICC profile to interpret the data.What speaks against Tiff as a container? By convention Tiff is already heavily ICC biased. So best changes to find many readers, which interprete the ICC profile correctly including the desired TRC. A different option is to use PPM, the high bit depth version, and compress and add meta data, ICC Profiles, outside. So it is well useable inside other containers, say OpenRaster and so simple to implement.
Floating point tiff doesn't seem to be as well supported as OpenEXR in the various free/libre editing applications. For example at present Krita 2.9 can't read or write a floating point tiff but reads and writes OpenEXR images with no problems.
Apparently the tiff specs encompass many different ways of writing an image.From a user perspective, if tiff (or PPM) doesn't work for sharing high bit depth RGB data between ICC profile color managed editing applications, maybe the applications can read and write OpenEXR.
[Prev in Thread] | Current Thread | [Next in Thread] |