ID 394801 - Transferring a project to a new OCIO config is causing Mari to break the colorspace channel roles

Problem summary
Transferring a project to a new OCIO config is causing Mari to break the colorspace channel roles

Customer reported version

4.5v1

Customer reported platform

Steps to reproduce

1) Set the environment variable MARI_COLORSPACE_USER_INTERFACE_MODE=2 in order to enable Advanced Color Management

2) Set the OCIO environment variable to point to the attached OCIO profile (1)

3) Create a new project

4) Go to the Channels palette, select the Base Color channel and adjust the colorspaces for the Color Data as it follows:

​

5) Save the project and close Mari 

6) Change the OCIO environment variable to point to the attached OCIO profile (2)

7) Open Mari and the saved project 

8) Go to the Base Color channel and notice the Color Data colorspace

result: Mari breaks the colorspace data: 

​

Expected behaviour
The roles should be set to Automatic (ACES - ACEScg) similar to previous versions of Mari 

Actual behaviour
The roles are converted incorrectly 

Workaround
Change the colorspace roles manually 

Reproduced by support
This bug has been reproduced in:

4.5v1 - CentOS 7 - Windows 10

4.2v2 - CentOS 7 - Windows 10 - regression

Unable to reproduce bug in:
4.2v1 - CentOS 7 - Windows 10 

Earliest version tested
4.2v1 - This issue no longer appears in this version and has regressed