OCIO Configuration Error (Play in RV)

RV
1

Hey there,
I ran into a quite complicated error.

I needed to adjust the OpenColorIO Basic Color Management package.
My company manages environment variables in rez, but for RV we decided to go a different way. We write the path to the config file in a version shotgun field when we publish from shotgun toolkit. This way we can configure rv without rez.

Therefore I needed to make quite a few changes.
First I listen to the graph-state-change event, to see if the parameter tracking.info is available, then I can reload the ocio config (currently 1.1). Afterwards I can automatically set the colorspace to fit the information given in another shotgun field (rather than in the filename, as suggested by the default implementation).

This works fine in Screening Room, when the browser is launched in RV. But when I start RV from shotgunstudio (Play in RV), I get this Error:

ERROR: OCIOIPNode: Config::GetProcessor failed. Destination colorspace is null.

I guess it is a runtime thing, becauce the error sometimes looks like this:

EERRRROORRE::R ROOOCCRIII:OON IIFOPPOCNN:Ioo OdduIeesP::iN noCCgdoo ennO:ffC iiICggOo::Dn::ifGGsieepgttl:PPa:rryGoo eccfteeoPssrrss ooodcrrie ssffpsaaloiiarlly ee:fdd a…Li GlDD eeeFdssU.ttL iiLDnn eaaHsttDtii ioo(nnn1a )tccio
oollnoo rrcssopplaaoccrees piiassc enn uuillsll …n
ull.

Also, when I added 10 milliseconds of sleep to where I thought the error was caused, the error-message appears more often and in between different debug messages.

This is new in RV 2021 and does not happen in RV 7.8.0. Also it does not happen if I choose Compare in RV

Do any of you know where I can adjust my code to fix this? Whether it be in the shotgun_fields_config.mu, the ocio_source_setup.py or the config.ocio file…

I grateful for any suggestion.
Cheers, Henriette

1 Like
2

Methods to fix-
Method 1: Re-download the installer file.
Method 2: Reinstall the problematic application.
Method 3: Check your Registry.
Method 4: Install the latest Microsoft Visual C++ Redistributable Packages.
Method 5: Perform a System File Checker scan.

This may help you,
Rachel Gomez

1 Like
3

Hello Rachel,
thank you for your ideas.

None of them work and after more than a year I still get this error - with a new RV release, a different OCIO configuration and a different cause of error.

The RV Dev Team is looking into it, since the Support Team got the same error, when I explained what’s causing it now, maybe they’ll be able to fix it.

1 Like