From 66e2690a96af3a521a047f97bbd6184bb7001fdb Mon Sep 17 00:00:00 2001 From: Bean <98428255+bean-mhm@users.noreply.github.com> Date: Fri, 26 May 2023 20:24:24 +0000 Subject: [PATCH] Update README.md --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f8c10da..c5533e5 100644 --- a/README.md +++ b/README.md @@ -74,16 +74,19 @@ colorspaces: from_scene_reference: ! children: - ! {src: Linear CIE-XYZ I-E, dst: Linear BT.709 I-D65} + - ! {min_in_value: 0., min_out_value: 0.} - ! {allocation: lg2, vars: [-11, 11, 0.00048828125]} - ! {src: flim.spi3d, interpolation: linear} ... ``` -Paying attention to the transforms, you will notice a `ColorSpaceTransform` from CIE-XYZ I-E to Linear BT.709 I-D65. This is because the example OCIO config has its reference color space (the `reference` role) set to CIE-XYZ I-E. If your config already uses Linear BT.709 I-D65 as its reference this is not needed. If your config uses another color space as its reference, you should manually do a conversion to Linear BT.709 I-D65. You can get the conversion matrices using the [Colour](https://www.colour-science.org/) library. +1. Paying attention to the transforms, you will notice a `ColorSpaceTransform` from CIE-XYZ I-E to Linear BT.709 I-D65. This is because the example OCIO config has its reference color space (the `reference` role) set to CIE-XYZ I-E. If your config already uses Linear BT.709 I-D65 as its reference this is not needed. If your config uses another color space as its reference, you should manually do a conversion to Linear BT.709 I-D65. You can get the conversion matrices using the [Colour](https://www.colour-science.org/) library. -Next, we have an `AllocationTransform` which can be directly copied from the LUT comments. The `AllocationTransform` here takes the log2 of the tristimulus (RGB) values and maps them from a specified range (the first two values after `vars`) to the [0, 1] range. The third value in `vars` is the offset applied to the values before mapping. This is done to keep the blacks. +2. Then, we have a `RangeTransform` which is there to eliminate negative values (out-of-gamut). -Finally, a `FileTransform` references the 3D LUT. +3. Next, we have an `AllocationTransform` which can be directly copied from the LUT comments. The `AllocationTransform` here takes the log2 of the tristimulus (RGB) values and maps them from a specified range (the first two values after `vars`) to the [0, 1] range. The third value in `vars` is the offset applied to the values before mapping. This is done to keep the blacks. + +4. Finally, a `FileTransform` references the 3D LUT. Here's an example of how you can add flim as a view transform to an OCIO config: