Redshift OCIO issue

[Dutchbird]

@drawer-site
Hi. Even when a default scene is set I get the error when starting a new project.
But only after a restart of the application.

[Dr. Sassi]

Hi Dutchbird,

First, answering that without knowing any version of C4D or OCIO you use is dangerous for your outcome.

The entry for the past few versions should be $OCIO. Since I know you sometimes use older versions, something might have overwritten your older setup. (Wild guess here.) However, if you get a file from someone else, make sure you have that OCIO version.

Please check with tech support to avoid a long search, or follow the wild guesses below in case that error alert appears with your own files, form the same Cinema 4D version.
https://www.maxon.net/en/support-center

The change of OCIO might change all color output, and any continuity in a project may not be provided. A fast (wrong) solution, or wild guesses, might destroy the output continuity. Not OCIO is a framework that will be continuously updated.

Is that working when you right-mouse click on the "OpenColorIO Config" and use the set to Default?

I'm unclear about what version you use, Cinema 4D and OCIO-wise. Have you changed something?

The installation typically provides all the needed data and settings if nothing has changed.

I don't say it often, but either your preferences are in need to be deleted or a new installation is due. As this is a wild guess, try first to reset the default.

The idea is that OCIO is based on a central installation, e.g., in a larger Studio. Everyone uses the same framework; if updated, the whole studio stays in sync. This allows the framework to have settings for any Color Management that is inside of that framework. Those settings rely on a specific version of OCIO, e.g., it could be based on ACES or soon ACES v2 (Whatever "soon" means…)

The error message "Project OCIO settings invalid. Falling back to default" in the context of Cinema 4D and OCIO (OpenColorIO) installation typically means that the application was unable to locate the specified OCIO configuration file. OCIO is a "color management" solution that allows for consistent color transformations and image display across various software applications. Studios use OCIO to set specific color management rules to maintain color consistency across different pipelines.

To address the concept of "falling back", here is a clearer explanation:

When Cinema 4D (or any software using OCIO) cannot find the specified OCIO configuration (which might be centrally installed for studio-wide consistency), it "falls back" to using a default configuration. This default configuration is a predefined OCIO setup that ensures the application can still function with some level of color management, even though it may not conform to the studio's custom rules.

So, in short:

• OCIO (OpenColorIO) allows for centralized and custom color management rules, often used by studios to ensure consistent color handling.
• If Cinema 4D cannot find the specified custom OCIO configuration, it will "fall back" to using a default configuration.
• "Falling back" means reverting to a baseline or default system when the preferred or custom option is unavailable.

This ensures that the application can continue to operate without the specific custom color management settings, albeit with potentially less precision or consistency compared to the studio-defined OCIO setup.

Please note, OCIO is a framework, not the Color Management itself.

All the best

[Dutchbird]

@Dr-Sassi Just as a try out I deleted Cinema4d and Redshift completely, including the prefs folder and reinstalled the latest version.
Got all running , made a new default startup scene and after a restart I got the same error message.
I followed the latest Macon YouTube with Elly about the new PBR material and noticed on her screen she had the same error.

[Dr. Sassi]

Thank you, Dutchbird.

Very nice to explore that option, and yes, I hesitate to suggest those time "eating" tips.

A few moments ago, I chatted with a colleague from the HQ, and he encountered the same. I saw Elly's alert on her screen during my QA/Timestamps session.

There is something that needs a fix. Sorry that you have to endure this!

If you have a moment, would you mind opening a ticket?
https://www.maxon.net/en/support-center
The more data, the faster the fix (typically)

Fingers crossed, it will be fixed quickly.

Cheers

[TeroKotsa_]

Hey, I'm having the same issues with OCIO being invalid? This really needs to be fixed ASAP.

[Dutchbird]

@TeroKotsa_ I have completely disabled OCIO. It sucks.

[TeroKotsa_]

OCIO is crucial in our pipeline so yeah this suck now.

[Dr. Sassi]

Hi there,

I can understand your frustration. But please keep it to facts and don't use this forum here for emotional downloads. Thank you.

Please share your findings with the Tech Support here:
https://www.maxon.net/en/support-center
This is the direct hotline to anything technical and the shortest way to get this fixed.

If you have any problems with Tech Support, please share the tick number with me, and I will get in touch with the people in charge.

Thank you!

All the best

[Dutchbird]

@Dr-Sassi Apologies for that. But since the last update I have a lot of issues with color management.
Renders don’t look the same.
This is my support ticket number (#756858)

[Dr. Sassi]

Thanks for the ticket number, Dutchbird.

I surely understand the frustration. I try to avoid having that social media echo chamber syndrome. Any long-term user like you knows problems happen and typically get sorted out. All of them, sadly not. But I'm sure OCIO as a framework and ACES as a Color Management system will have attention.

The color shifts happen mostly based on color and gamut compression, when large color spaces and high dynamics move into small formats, like REC 709 or sRGB. This will not change; with any new ACES version, new shifts will happen going into smaller formats.

One reason is that the renderings have no IDT (Input Device Transform), and if everyone has his/her outcome from a render, then the Tonmapping and Gamutcompression for smaller formats will have very different outcomes. Think of an S-Curve in Photoshop; while moving the underlying content up and down in exposure, the midtones might move closer to the shoulder or the toe of the S curve, which will change things. This is, in a nutshell, why the REC709 or sRGB RRT/ODT has shifted.

New solutions have been announced, and one of my many ACES trainings (since 2012, I have taken ACES classes all over the place) showed last year a new way to handle this. (color.training is the URL; I'm an alumnus of the Color Academy for Professional Colorists) Dado, the Color Academy owner, trained us with these new tools back then.

In short, things will continue to change. Hence, renderings should be stored in ACES AP-0 and 32bit/channel float.)

All the best

[silver-quit]

I'm getting this as well.
Error messages:
WARNING: Project OCIO settings invalid. Falling back to builtin settings

Then when I look at my color management in Redshift render settings, I have no options.

What gives?!

[Screenshot 2025-05-01 at 12.11.04.png](Image dimensions are too big)

[Dutchbird]

@silver-quit Your screenshot is too big. 500px max.
I know. In this modern superspeed internet world Cineversity is still a little bit behind.

[Dutchbird]

@silver-quit But I found a work around. Sometimes when you import a file and you see the color management is f**ed up and OCIO is set to DEFAULT just go to scene settings/color management (command-D) and change "$(DEFAULT" to "$OCIO"
This worked for me.

[Dr. Sassi]

Hi there,

Remember that OCIO is a framework that is supposed to be installed centrally or in synch with the workflow provided, and OCIO is updated occasionally. This means OCIO, old or newer, is perhaps not the same as the installed one! It can't find the one defined in the file if a different version was used than the installed one.

Please always check the outcome. Typically, the use of ACES causes trouble if the RRT/ODT function is not understood for low dynamic/gamut outputs like REEC 709 or sRGB, which will show up especially with artifacts in 8bit/channel. Typically, the use is connected to wishful thinking about the filmic outcome, which changes if used for higher dynamic and larger Gamuts. Tone mapping or gamut compression is unnecessary, and the "filmic" effect [sic] is gone.

Setting the OCIO to your installation might not create the outcome envisioned by the external creator of the file.

Please check with support if you have a problem with a file created in your unchanged setup.

Cheers