CR2 and other RAW processing

[Simon_Arnold]

Hi can someone explain to me the process of linearization steps RV applies to any camera raw files such as cr2, NEF etc. Does the OCIO configuration have any effect on this and when exporting from RVIO?

any help would be appreciated.

[alexaz]

Hey @Simon_Arnold,

Thank you for engaging with the forums!

We currently support LibRaw 0.18 library in RV, which means that some of the newer camera cr2s might not play properly in RV. You can see what cameras are supported via 0.18:
https://www.libraw.org/news/libraw-0-18-released

A good place to start is to see what RV color pipeline looks like, since RAW format follows the same color pipe as other formats:

What is the tl;dr on the RV color pipeline?

Hey, first of all thank you for the write ups, they are really informative! I managed to put together something that works quite quickly, based on the example you gave in the other thread. Now items in the OCIO menu are not disabled, and the correct ones are selected. All items were disabled, previously, when configuring only through the environment ($OCIO, $SHOT). Next we are going to look into creating a new package, in order to load the necessary scripts when needed. We are just getting …

OCIO offers more of a control over RV’s standard pipeline so you can skip linearization or do whatever transforms please you and RV will replace the internal pipe with OCIO config instead:

Getting started with OCIO in RV

RV has a couple of nodes that can be used instead of or complimentary to the RV’s color pipeline. You can get some info about OCIO in RV here: OpenColorIO Integration If you check out the OCIO package info in the Package manager RV -> Preferences -> Packages -> OpenColorIO Basic Color Management , there’s a bit of a description about how OCIO can be auto-setup via a script. You can create rv_ocio_setup.py file in your support path under the Python directory to have your own script auto-determi…

Please let us know if you have further questions.

Thanks,
Alexa