OCIO environment variable not working on Linux #59016

New Issue

Rainer Trummer · 2018-12-08T13:14:07+01:00

Rainer Trummer commented

2018-12-08 13:14:07 +01:00

System Information
Operating system: Ubuntu Linux, 17.04 - 18.10
Graphics card: nVidia Geforce 650m

Blender Version
Broken: any 2.80 version for now
Worked: 2.79b and before

Short description of error
I am using the following variable in /etc/environment to set a custom OCIO location:

OCIO=/CustomSoftware/OCIO/filmic-blender/config.ocio

When starting Blender 2.80 from the command line, an error is printed into the console window:

Color management: using fallback mode for management
Color management: scene view "Filmic" not found, setting default "Default".
Color management: scene look "Filmic - Base Contrast" not found, setting default "None".

What happens then is that I have only one View Transform ('Default') and no Looks available at all. Nor my custom ones, neither the Default shipped ones.

I'm using this setup because I have a custom OCIO color configuration that is also shared with applications like Resolve and Nuke. The interesting thing is that using environment variables on Windows does work. This seems to be a Linux only issue (cannot test MacOS though). Also, with Blender 2.79b, the OCIO variable is evaluated correctly on the same Linux machine.

**System Information** Operating system: Ubuntu Linux, 17.04 - 18.10 Graphics card: nVidia Geforce 650m **Blender Version** Broken: any 2.80 version for now Worked: 2.79b and before **Short description of error** I am using the following variable in /etc/environment to set a custom OCIO location: ``` OCIO=/CustomSoftware/OCIO/filmic-blender/config.ocio ``` When starting Blender 2.80 from the command line, an error is printed into the console window: ``` Color management: using fallback mode for management Color management: scene view "Filmic" not found, setting default "Default". Color management: scene look "Filmic - Base Contrast" not found, setting default "None". ``` What happens then is that I have only one View Transform ('Default') and no Looks available at all. Nor my custom ones, neither the Default shipped ones. I'm using this setup because I have a custom OCIO color configuration that is also shared with applications like Resolve and Nuke. The interesting thing is that using environment variables on Windows **does** work. This seems to be a Linux only issue (cannot test MacOS though). Also, with Blender 2.79b, the OCIO variable is evaluated correctly on the same Linux machine.

Rainer Trummer commented

2018-12-08 13:14:08 +01:00

Added subscriber: @RainerTrummer

Stephen Swaney commented

2018-12-08 16:39:40 +01:00

Added subscriber: @StephenSwaney

Sebastian Parborg commented

2019-01-23 13:09:20 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-01-23 13:09:20 +01:00

If i clone this git repo: https://github.com/imageworks/OpenColorIO-Configs

And run blender with OCIO=<path-to>/nuke-default/config.ocio ./blender it works as I would expect it to. But I have to admit I'm not 100% sure how this should work.

Do you still have this issue on linux with the latest blender beta?

If i clone this git repo: https://github.com/imageworks/OpenColorIO-Configs And run blender with `OCIO=<path-to>/nuke-default/config.ocio ./blender` it works as I would expect it to. But I have to admit I'm not 100% sure how this should work. Do you still have this issue on linux with the latest blender beta?

Rainer Trummer commented

2019-01-23 20:05:28 +01:00

Yes, for me the problem still persists. Same if I use the provided syntax above: OCIO=/CustomSoftware/OCIO/filmic-blender/config.ocio ./blender throws the same error for me:

Color management: using fallback mode for management
Read prefs: <path_to_prefs>/UserConfigs/Rainer/userpref.blend
Color management: scene view "Filmic" not found, setting default "Default".
Color management: scene look "Filmic - Base Contrast" not found, setting default "None".

Blender 2.79b uses my custom OCIO config just fine.

Yes, for me the problem still persists. Same if I use the provided syntax above: `OCIO=/CustomSoftware/OCIO/filmic-blender/config.ocio ./blender` throws the same error for me: ``` Color management: using fallback mode for management Read prefs: <path_to_prefs>/UserConfigs/Rainer/userpref.blend Color management: scene view "Filmic" not found, setting default "Default". Color management: scene look "Filmic - Base Contrast" not found, setting default "None". ``` Blender 2.79b uses my custom OCIO config just fine.

Rainer Trummer commented

2019-01-23 20:10:18 +01:00

Output of 2.79b:

OCIO=/CustomSoftware/OCIO/filmic-blender/config.ocio ./blender 
Color management: Using /CustomSoftware/OCIO/filmic-blender/config.ocio as a configuration file
Read prefs: <path_to_prefs>/UserConfigs/Rainer/userpref.blend
Color management: scene view "Default" not found, setting default "sRGB OETF".
Color management: sequencer colorspace "sRGB" not found, will use default instead.

which is the expected output. The original implementation of Troy Sobotka calls the Default View Transform "sRGB OETF", so 2.79b finds the settings and sets the defaults as desired.

Output of 2.79b: ``` OCIO=/CustomSoftware/OCIO/filmic-blender/config.ocio ./blender Color management: Using /CustomSoftware/OCIO/filmic-blender/config.ocio as a configuration file Read prefs: <path_to_prefs>/UserConfigs/Rainer/userpref.blend Color management: scene view "Default" not found, setting default "sRGB OETF". Color management: sequencer colorspace "sRGB" not found, will use default instead. ``` which is the expected output. The original implementation of Troy Sobotka calls the Default View Transform "sRGB OETF", so 2.79b finds the settings and sets the defaults as desired.

Brecht Van Lommel commented

2019-01-23 20:20:26 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-01-23 20:20:26 +01:00

Are you perhaps using your own or an unofficial Blender build? If so, does the official daily build work for you?
https://builder.blender.org/download/

It seems like somehow you are using a Blender without OpenColorIO support?

Are you perhaps using your own or an unofficial Blender build? If so, does the official daily build work for you? https://builder.blender.org/download/ It seems like somehow you are using a Blender without OpenColorIO support?

Rainer Trummer commented

2019-01-24 20:31:54 +01:00

@brecht Jesus, that was indeed the issue. My own builds fail to detect OCIO, while the official ones work just fine. Must have messed that up a while ago. Thanks for investigating!

Brecht Van Lommel commented

2019-01-24 20:42:34 +01:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-01-24 20:42:34 +01:00

Brecht Van Lommel self-assigned this 2019-01-24 20:42:34 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

OCIO environment variable not working on Linux #59016