ID 502637 - View knob cannot be set pythonically when creating OCIO Display Soft Effects when using non default OCIO configs

Follow

Problem summary
View knob cannot be set pythonically when creating OCIO Display Soft Effects when using non default OCIO configs
By non default OCIO config, that means the projects is using a different OCIO config than the preferences default
Testing the other OCIO Soft effects, all their colorspace type knobs seem to be set correctly, and even the colorspace knob on the OCIO DIsplay works correctly.
Creating a OCIODisplay node in the Nuke node graph and setting the knob value on creation pythonically works as expected

Customer reported version
hieroplayer.13.1v2

Customer reported platform
centos7

Steps to reproduce

1) Open Nuke Studio/Hiero/HireoPlayer

2) In Project>Edit Settings>Color Management, set the OpenColorIO Config to aces_1.2

3) Import any footage and add it to the timeline

4) Select the clip in the timeline, then run the following code in the Script Editor:
selection = hiero.ui.getTimelineEditor(hiero.ui.activeSequence()).getSelection()for track_item in selection:    track_effect = track_item.parentTrack().createEffect('OCIODisplay', trackItem=track_item)    track_effect.node()['colorspace'].setValue(2)    track_effect.node()['view'].setValue(2)
5) Double click the OCIODisplay Soft Effect to open it's properties and check the view (view transform) knob

Expected behaviour
For the view knob to be changed form the default value to 2 (DCDM P3D60 Limited), like the colorspace knob does
​​

Actual behaviour
The view knob always uses the first value, in this case sRGB:
​​

Workaround
Don't use different OCIO configs in your project compared to the preferences default.
If using Hiero or Nuke Studio, you can run another python script to update the value

Reproduced by support
This bug has been reproduced in:
Hiero 13.1v2 - Windows 10, CentOS 7, macOS Big Sur
Hiero 12.0v1 - Windows 10
Nuke Studio 9.0v1 - Windows 10, macOS Big Sur

Earliest version tested
Nuke Studio 9.0v1 - This issue appears to be in all versions of the product

    We're sorry to hear that

    Please tell us why