Hello Lucien, The ACES 1.0.1 OCIO config doesn't define a colorspace named 'linear'. Did you start with this? https://github.com/hpd/OpenColorIO-Configs/blob/master/aces_1.0.1/config.ocio
Nuke will use the value of the role 'scene_linear' for the default value for most colorspace operations, I believe. https://github.com/hpd/OpenColorIO-Configs/blob/master/aces_1.0.1/config.ocio#L19 HP On Tue, Jan 19, 2016 at 10:28 AM, lucien fostier <lucienfost...@gmail.com> 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
