Hey, thanks for this OCIO post. Despite this post being clear and well written, I’m still struggling to get this set up.
I have an OCIO config that I want put in a central location and connect everyone to it.
Getting tripped up at the off with adding a path to the RV_SUPPORT_PATH.
Tried in a shell 'rvpkg -include ’ but received an error.
Had a look at the python scripts on this page and although I know some python (artist’s python!) I couldn’t work out where to add the path to the ocio config file.
The config is set in the function ocio_config_from_media, which should return a Config object, e.g. by OCIO.Config().CreateFromFile(config_path). ocio_node_from_media then returns a configuration dict, which describes the corresponding node to be created, depending on the stage.
Here is our custom rv package.
It derives from the built-in ocio source setup.
It is installed using rvpkg (the steps are described in the manual).
Again the key functions are ocio_config_from_media and ocio_node_from_media.
In this package, we read a mapping from project to ocio config, and return this from the former function.
The latter decides which color spaces to use depending on the input file format, etc.