In RV there are two separate ways to configure color:
RV color pipeline or
OCIO color management .
RV color pipeline involves adding and re-arranging nodes throughout the color pipeline. All of the configuration is handled through the source_setup.rvpkg package. You can get more details on it here: Chapter 12 - Automated Color and Viewing Management
You can see the Image Processing graph here: Chapter 2 - Image Processing Graph I think the simplified takeaway from this is the following:
Where SourceGroup is the node where RV tries to parse all the input colorspace and transforms that come from the file (read any of the information from the image format, look pipeline, LUT transforms, etc). Then by the time RV display this information in a
View (Sequence, Stack or Layout) the output of
sourceGroup has to be linear for RV to process the color correctly. Then, after the view there’s one DisplayGroup node per display device. And here you can specify for the
DisplayGroup to convert from linear to sRGB (or any other space you need). RV assumes separation between file look and display space, where
DisplayNode will only contain the colorspace for the
Now, for the
SourceGroup, you can arrange the pipeline nodes in any way that you would like, and whatever order. This is where
source_setup.rvpkg comes in. It’s a package that is installed and enabled by default in RV. You can navigate to the python code under
$RV_INSTALL_PATH/Contents/PlugIns/Python/source_setup.py. Please create your own package that subclasses the original
source_setup.rvpkg. You can specify
DisplayGroup look in your package as well.
We also offer OCIO color management where RV’s color pipeline is entirely bypassed to be replaced by OCIO nodes where appropriate. We do recommend trying RV’s color pipeline first before diving into OCIO.