Just for the record: The node converts colors from a user-selected input color space to an output color space when possible. Expert users could alter the OCIO configuration files (using a text editor).
The node is not designed for production usage, only for testing purposes. If the node would be added I want to have a proper design (user and technical perspective) I would not recommend adding this just as a temporarily solution. Jeroen - At Mind - Original Message: ----------------- From: Troy Sobotka troy.sobo...@gmail.com Date: Tue, 17 Jan 2012 00:05:36 -0800 To: bf-committers@blender.org Subject: [Bf-committers] Tile Branch OCIO node Seeing as how we hit a stalemate with the potential of trying to get a low level implementation of color management into Blender, I am hoping that we can include Jeroen's massively useful OCIO node. It is already written, worked wonderfully, and of tremendous value. Perhaps we could consider this node temporary until we can tackle colour management in earnest at a deeper level? It would be extremely useful to many artists and greatly elevate Blender's viability for some workflows. With respect, TJS _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers -------------------------------------------------------------------- mail2web.com What can On Demand Business Solutions do for you? http://link.mail2web.com/Business/SharePoint _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
