Re: New to OCIO, and viewer processes in Nuke
Jeremy Selan <jeremy...@...>
The other issue is that the nuke-default ocio config is intended totoggle quoted messageShow quoted text
work in other applications other than nuke. And many of these other
apps dont automatically include a 'none' option by default, the same
way Nuke does.
Do you have concerns about removing the default Nuke 'None' option?
As ben mentions, register_viewers() should be removing all of the
Alternatively, as a compromise we could place the None option at the
bottom of the list. Thus, while it would be duplicated in your case
at least the second copy wouldn't be getting in the way of the real
I should also note that at Imageworks, while we of course use
OCIODisplay for our viewer, we dont rely on the public
register_viewers() call to register the nodes. I forget the exact
reason but it relates to splitting up the registration into two parts
(init.py vs. menu.py) so knob defaults can be appropriate set on
startup. I'll ping our nuke guru to add further details.
On Wed, Aug 3, 2011 at 9:29 AM, dbr/Ben <dbr....@...> wrote:
The ocionuke.viewer.register_viewers() should have an argument which will