On Wed, Jun 5, 2013 at 11:45 PM, Andy Jones <[email protected]> wrote:
> 3) Wait for Nuke to release a version that lets us opt into native > OCIO support for the Read and Write nodes. > > Option #3 seems particularly compelling, and seems like it should be > coming soon, given that Hiero already relies entirely on OCIO for its > colorspaces, and it would obviously behoove The Foundry to have their > color management consistent across their own apps. > > If option 3 is going to happen, but not right away, I suppose I'd opt > for option 1, just to avoid complexity and proprietary nodes that get > deprecated within the year. > > But if it's going to be a long time or maybe never happen, option 2 > would make sense. We're in agreement that using OCIO should be as seamless as using Nuke's original LUT color management and we intend to get there. However, Jon W did some experiments to get a feel for how big a job that will be and uncovered some complications internally, so given the dev load we already had scheduled I think you shouldn't count on seeing it yet this year. Although that's not great news, hopefully it's also not terrible. If anyone has strong feelings about how any of this should work, or particular requirements you worry about, please feel free to contact me directly if you want, and I'll also check in on this thread again to see if anything more comes up here. Matt -- Matt Plec Senior Product Designer The Foundry Web: www.thefoundry.co.uk The Foundry Visionmongers Ltd. Registered in England and Wales No: 4642027
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
