AcademySoftwareFoundation / AcademySoftwareFoundation/OpenColorIO

Resolve cube reader fails on new VIDEO_RANGE tags

Open
#1,767 0 comments 0 reactions 0 assignees View on GitHub
good first issue help wanted
Dominant language
C++
Stars
2.1k
Forks
503
PR merge metrics
No merged PRs in 30d

Description

Recently DaVinci Resolve added the following keyworks to their .cube spec.
LUT_IN_VIDEO_RANGE
LUT_OUT_VIDEO_RANGE
With the following description:
- In Resolve, LUTs are applied in data range (0.0 to 1.0). The input data is
in data range, and the LUT is expected to output in data range. However,
there may be LUTs that are designed to operate on and/or output video range
data (64 - 940 in 10-bit scale). To handle these cases, there are two
properties which can be used to notify Resolve that the input/output is in
video range. Based on this, Resolve will handle the input/output values so
that it works correctly in a data range processing pipeline. Depending on
the LUT, one or both of these properties can be specified by having the
keywords below on a new line.

Using OpenColorIO
2.3.0dev
OpenColorIO Error: The specified transform file ......
At line (11): 'LUT_IN_VIDEO_RANGE'. Malformed color triples specified.

The actual spec for DaVinci .cube in included with the Resolve installation. File location depends on the platform but is found under the developer info.
DaVinci Resolve/Developer/LUT/README.txt

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.