ID 423544 - The wrong Viewer Process is applied when setting a default OCIO in the init or menu.py.

Follow

Problem summary
The wrong Viewer Process is applied when setting a default OCIO in the init or menu.py.


Customer reported version
nuke.n/a


Customer reported platform


Steps to reproduce

1) In the init.py, create and save the following snippet:

nuke.knobDefault('Root.colorManagement', 'OCIO')

nuke.knobDefault('Root.OCIO_config', 'aces_1.0.3')

nuke.knobDefault('Viewer.viewerProcess', 'Rec.2020 (ACES)')

2) Launch Nuke and press S in the Node Graph to view the Project Settings > Color settings.

3) Ensure Color Management is set to OCIO.

4) Delete the Viewer node and create a new one, observing the viewerProcess setting.


Expected behavior
The correct OCIO Viewer Process should be displayed per settings made in the init.py.


Actual behavior
An incorrect OCIO Viewer Process is displayed when launching Nuke with a specific OCIO setting.


Workaround

Adding the following snippet to the bottom of the initial code in the init.py will allow the correct OCIO Viewer Process to be used:

def setViewerProcess():

    nuke.thisNode()["viewerProcess"].setValue('Rec.2020 (ACES)')

nuke.addOnUserCreate(setViewerProcess, nodeClass='Viewer')

Reproduced by Support in

Nuke 12.0v4 - Windows 10, CentOS 7, macOS 10.13

Nuke 12.0v3 - Windows 10

Nuke 12.0v1 - Windows 10

Nuke 11.3v5 - Windows 10

Nuke 11.3v1 - Windows 10

Nuke 11.2v1 - Windows 10

Nuke 11.1v1 - Windows 10

Nuke 11.0v1 - Windows 10

Nuke 10.5v1 - Windows 10

Nuke 10.0v1 - Windows 10

Nuke  9.0v1 - Windows 10

Nuke  8.0v1 - Windows 10, CentOS 7, macOS 10.13


Earliest version tested
Nuke8.0v1 - This issue appears to be in all versions of the product


    We're sorry to hear that

    Please tell us why