Nuke colorconfig - View "None" is "raw" in OCIO


mikael....@...
 

I'm doing automated slap-comps to check render output in sRGB/Cineon and scene-linear, if I use the nuke profile and "None" as the view for the default display the profile returns "raw". It should be linear to match Nuke, right?
Mikael


Mark Boorer <mark...@...>
 

Hi Mikael,

Just trying to see if I'm understanding your issue correctly. When using the OCIO Display node inside of Nuke (with the OCIO environment variable pointing to the nuke-default/config.ocio and the viewer transform set to "None") You are getting "raw" as the default input colorspace?

Would you mind letting me know the versions of Nuke / OCIO / OpenColorIO-Configs you are using?

At the moment, I can't seem to replicate the issue on Nuke8.0v5, with libOpenColorIO.so.1.0.7, and using the master branch of OpenColorIO-Configs. I see "linear" by default as expected.

Cheers,
Mark




On Tue, Jul 22, 2014 at 10:21 AM, <mikael....@...> wrote:
I'm doing automated slap-comps to check render output in sRGB/Cineon and scene-linear, if I use the nuke profile and "None" as the view for the default display the profile returns "raw". It should be linear to match Nuke, right?
Mikael

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


mikael....@...
 

Not really - it happens outside Nuke using the ocio GPU support:

OCIO::DisplayTransform::create()
displayTransform->setInputColorSpace( "sRGB" )
displayTransform->setDisplay( "display" )
displayTransform->setView( "None" )
+ LUT data and GPU shader generation

This applies only to non-linear input colorspaces, if None is set as view then the input colorspace will not transformed to linear, right?

I modified the Nuke profile:

displays:
  default:
    - !<View> {name: None, colorspace: linear} <= instead of raw

To match the viewerProcess drop-down in nuke. With this setup you'll get a linear representation if None is used as view (in this example sRGB => linear).

I may not be right here :-) but I hope so. Guess it's more of a question about when the actual color transformation happens in nuke and ocio.

Mikael


Den onsdagen den 23:e juli 2014 kl. 01:33:31 UTC+2 skrev Mark Boorer:

Hi Mikael,

Just trying to see if I'm understanding your issue correctly. When using the OCIO Display node inside of Nuke (with the OCIO environment variable pointing to the nuke-default/config.ocio and the viewer transform set to "None") You are getting "raw" as the default input colorspace?

Would you mind letting me know the versions of Nuke / OCIO / OpenColorIO-Configs you are using?

At the moment, I can't seem to replicate the issue on Nuke8.0v5, with libOpenColorIO.so.1.0.7, and using the master branch of OpenColorIO-Configs. I see "linear" by default as expected.

Cheers,
Mark




On Tue, Jul 22, 2014 at 10:21 AM, <mikae...@...> wrote:
I'm doing automated slap-comps to check render output in sRGB/Cineon and scene-linear, if I use the nuke profile and "None" as the view for the default display the profile returns "raw". It should be linear to match Nuke, right?
Mikael

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


mikael....@...
 

"This applies only to non-linear input colorspaces" => not non-linear, all colorspaces except Linear.

Den onsdagen den 23:e juli 2014 kl. 09:07:28 UTC+2 skrev mikae...@...:

Not really - it happens outside Nuke using the ocio GPU support:

OCIO::DisplayTransform::create()
displayTransform->setInputColorSpace( "sRGB" )
displayTransform->setDisplay( "display" )
displayTransform->setView( "None" )
+ LUT data and GPU shader generation

This applies only to non-linear input colorspaces, if None is set as view then the input colorspace will not transformed to linear, right?

I modified the Nuke profile:

displays:
  default:
    - !<View> {name: None, colorspace: linear} <= instead of raw

To match the viewerProcess drop-down in nuke. With this setup you'll get a linear representation if None is used as view (in this example sRGB => linear).

I may not be right here :-) but I hope so. Guess it's more of a question about when the actual color transformation happens in nuke and ocio.

Mikael


Den onsdagen den 23:e juli 2014 kl. 01:33:31 UTC+2 skrev Mark Boorer:
Hi Mikael,

Just trying to see if I'm understanding your issue correctly. When using the OCIO Display node inside of Nuke (with the OCIO environment variable pointing to the nuke-default/config.ocio and the viewer transform set to "None") You are getting "raw" as the default input colorspace?

Would you mind letting me know the versions of Nuke / OCIO / OpenColorIO-Configs you are using?

At the moment, I can't seem to replicate the issue on Nuke8.0v5, with libOpenColorIO.so.1.0.7, and using the master branch of OpenColorIO-Configs. I see "linear" by default as expected.

Cheers,
Mark




On Tue, Jul 22, 2014 at 10:21 AM, <mikae...@...> wrote:
I'm doing automated slap-comps to check render output in sRGB/Cineon and scene-linear, if I use the nuke profile and "None" as the view for the default display the profile returns "raw". It should be linear to match Nuke, right?
Mikael

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