Date
1 - 2 of 2
New to OCIO, and viewer processes in Nuke
|
Hugh Macdonald <hugh.ma...@...>
Hi all,
New OCIO user here... Just playing around with it to see how it'll fit into our colour pipeline. Primarily playing with the Nuke side of things so far. One small thing that's cropped up is how, when using the nuke-default config, there are two "None" items in the viewer process drop-down. I'm thinking that None probably should still be left in the menu in ocionuke.viewer.register_viewers(), and the config files should just not re-define a None. I'm thinking that the nuke-default config file should maybe reflect this As I'm quite new to OCIO, I didn't want to start forking and making a pull request for this kind of change, so I thought I'd bring it up on here first. Hugh Macdonald nvizible – VISUAL EFFECTS hugh.ma...@... +44(0) 207 659 2038 +44(0) 7773 764 708 www.nvizible.com |
|
|
|
dbr/Ben <dbr....@...>
The ocionuke.viewer.register_viewers() should have an argument which will removal all viewer processes, including the default "none" proc (it's no different to any other, just applies a no op node) On 03/08/2011, at 11:32, Hugh Macdonald <hugh.ma...@...> wrote:
|
|
|