I haven't used it in nuke 10 much either except I know you can use it just like in 8 - with dedicated ocio nodes if you really want.
I think the implementation is generally fantastic - being able to download latest aces configs - I never want to go back to normal colour space pipeline . I tend to use with a viewer input process using Ocio display node. Using aces is great - especially when doing dmp work in photoshop or silhouette - using the acescc space N Sent from my iPhone > On 1 Mar 2017, at 10:38, Simon Björk <bjork.si...@gmail.com> wrote: > > I was fairly happy with how OCIO was implemented in previous versions of Nuke > (pre 10). Having the option to use OCIO only for viewer luts was a great > solution in my opinion, and the OCIOColorspace nodes wasn't too much of a > hassle. That being said, I understand why the Read node was redesigned to > work directly with OCIO. > > I've not yet switched to this new method. What's been your experience with > it? Any bugs? Or are people still using OCIO nodes and register viewer luts > the "old way" in your init.py? > > /Simon > > > > ------------------------------- > Simon Björk > Compositor/TD > > +46 (0)70-2859503 > www.bjorkvisuals.com > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
