You can set your nodes to use any default you want, is that not
sufficient? Is the issue then that the default is not being managed by
your ocio config?
Could you call your colorspace "reference space" and then pick that, and
then what reference space is would be managed by OCIO?
./c.t
On 01/19/2016 01:28 PM, lucien fostier wrote:
Hey guys,
I'm doing the color management setup for a show that is using Aces CG
as the reference space.
Anyone has experience with it.
I found a very problematic point in Nuke's implementation:
- if you were to not define a colorspace "linear" in you OCIO config,
Nuke would just seg fault on startup.
- Nuke always pick "linear" as the default colorspace even if it's not
the reference space.
So if you create an OCIO colorspace node, linear is selected by
default even if it's not the first one in the list.
I understand that reference space is a not defined well entity in OCIO
architecture ( implicitly the first colorspace in the list).
Should I just have AcesCG to be named "linear"? I think that's even
more outrageous.
Cheers
--
lucien FOSTIER
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
