ociobakelut

[Zach Tucker]

I'm trying to generate a LUT using ociobakelut to convert scene_linear to AlexaV3LogC.

In nuke I get the same results when converting linear to AlexaV3LogC using either a colorspace node or the OCIO color space node.

However, the output from ociobakelut doesn't match, it doesn't properly recover the values of the linear image that are over 1.0 (ie, values over 1.0 in the original linear image aren't brought into 0-1 range, some are still over 1.0)

I'm using:

ociobakelut --format flame --inputspace linear --outputspace AlexaV3LogC flame_lin2AlexaV3LogC.3dl

also tried

ociobakelut --format flame --inputspace scene_linear --outputspace AlexaV3LogC flame_lin2AlexaV3LogC.3dl


I'm applying the resulting lut either in a vectorfield node directly or in a vectoryfield used as a VIEWER_INPUT, neither matches nukes colorspace nodes.

I'm using opencolorio v1.0.9 on osx and the included nuke-default/config.ocio included with the install.

[za...@zacharytucker.com]

Ok, I managed to get it working using cinespace/csp LUT format (see first ociobakelut command below)


Next ... I'm trying to combine a linear-to-AlexaV3LogC transform with a look LUT, in this case an Arri LUT (from Arri LUT Generator that provides pleasing highlights and rec709 for viewing ... typical on-set or dailies LUT).

Values over 1.0 aren't handled properly.

I'm using:

ociobakelut --format cinespace --inputspace linear --outputspace AlexaV3LogC cinespace_lin2AlexaV3LogC.csp  (this matches nukes colorspace and OCIOcolorspace conversions).

To combine them:

ociobakelut --format (anything, none work) --lut cinespace_lin2AlexaV3LogC.csp --lut AlexaV3_EI0800_LogC2Video_Rec709_EL_nuke3d.cube  output.(whatever)

I've tried converting the lin2Alexa csp and the Alexa_Log2Video cube to other formats (for example, both csp, both cube, etc) but none are working.

How do I combine a linear-to-AlexaV3LogC conversion with a look LUT?

-zach

[Kevin Wheatley]

I get the feeling you might want to look at using a shaperspace as
well, if you have the config with a look something like:

- !<Look>
name: my_Rec709
process_space: AlexaV3LogC
transform: !<FileTransform> {src:
AlexaV3_EI0800_LogC2Video_Rec709_EL_nuke3d.cube, interpolation:
tetrahedral}

ociobakelut --format cinespace --inputspace linear --outputspace

AlexaV3LogC --shaperspace AlexaV3LogC --look my_Rec_709 output.csp

you should probably match the --cubesize to the size of your .cube
file, all you are really doing is adding a shaper 1D to the cube and
storing it as a csp file.

Kevin

> --
> You received this message because you are subscribed to the Google Groups
> "OpenColorIO Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ocio-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Zach Tucker]

thanks for replay. I tried combining the 1D shaper in-line with the application of the look but apparently you can't combine --lut (which I presume you meant with --look) with input/output/shaper-space arguments. That's why I had been trying to first create the 1D shaper LUT, then combining that and the look LUT together in a separate command.

ociobakelut --format cinespace --inputspace linear --outputspace AlexaV3LogC --shaperspace AlexaV3LogC --lut AlexaV3_EI0800_LogC2Video_Rec709_EL_nuke3d.cube output.csp

ERROR: --inputspace is not allowed when using --lut

________________________________________
From: Kevin Wheatley [kevin.j....@gmail.com]
Sent: Tuesday, June 07, 2016 9:13 AM
To: ocio-...@googlegroups.com
Cc: Zach Tucker
Subject: Re: [ocio-users] Re: ociobakelut

[Kevin Wheatley]

Sent on the go...

> On 7 Jun 2016, at 18:04, Zach Tucker <zac...@moving-picture.com> wrote:
>
> thanks for replay. I tried combining the 1D shaper in-line with the application of the look but apparently you can't combine --lut (which I presume you meant with --look) with input/output/shaper-space arguments. That's why I had been trying to first create the 1D shaper LUT, then combining that and the look LUT together in a separate command.

No I meant look, if it is part of the config you can do what I suggested, I do something similar for all our shows.

Kevin

[Zach Tucker]

Got the config up and running and your suggestion worked.  Though combining a linear-to-AlexaV3LogC prelut with a 3D lut only works as a csp.  The cube and 3dl formats don't handle the values >1 correctly.  Maybe I'm missing something when combining them, tried matching cube sizes and am using --shaperspace AlexaV3LogC but no luck.  In my brief research it sounds like cube luts don't support a shaper AND 3D lut together.  I've also got it working w/o having to bake it, straight from the OCIO config, as it separates the pre-lut from the 3D lut i'm able to throw any lut type I want at it.

anything I'm overlooking for the shaper+3D lut in 3dl/cube formats or is it a format limitation?

Thanks again for the help!

.z

--
You received this message because you are subscribed to a topic in the Google Groups "OpenColorIO Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ocio-users/NRuH-HiT4Eo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ocio-users+...@googlegroups.com.

[Kevin Wheatley]

On Thu, Jun 9, 2016 at 7:40 AM, Zach Tucker <za...@zacharytucker.com> wrote:
> Got the config up and running and your suggestion worked. Though combining
> a linear-to-AlexaV3LogC prelut with a 3D lut only works as a csp. The cube
> and 3dl formats don't handle the values >1 correctly. Maybe I'm missing
> something when combining them, tried matching cube sizes and am using
> --shaperspace AlexaV3LogC but no luck. In my brief research it sounds like
> cube luts don't support a shaper AND 3D lut together. I've also got it
> working w/o having to bake it, straight from the OCIO config, as it
> separates the pre-lut from the 3D lut i'm able to throw any lut type I want
> at it.
>
> anything I'm overlooking for the shaper+3D lut in 3dl/cube formats or is it
> a format limitation?

it is typically a limitation of the file format/implementations but
.csp has always supported floating point input, most 3dl
implementations don't handle >1,0

doing it directly in the config and letting OCIO do the concatenation
is the best way to preserve as much as possible.

Kevin

[Zach Tucker]

excellent. thank you again.

.z

________________________________________
From: Kevin Wheatley [kevin.j....@gmail.com]

Sent: Thursday, June 09, 2016 2:52 AM

To: ocio-...@googlegroups.com
Cc: Zach Tucker
Subject: Re: [ocio-users] Re: ociobakelut

On Thu, Jun 9, 2016 at 7:40 AM, Zach Tucker <za...@zacharytucker.com> wrote: