ID 453334 - Loading disk cached stereo footage into a monitor output gives a black screen when using a stereo mode

Follow

Problem summary
When playing stereo footage into a monitor output stream, if the stereo footage is disk cached on the timeline and the output is set to a stereo mode (eg Full Resolution Stereo), the output will be a black screen on the monitor output stream.

Note: This only occurs in stereo modes and when the stereo footage is disk cached.

Customer reported version
nuke.12.0v3

Customer reported platform
10.14

Steps to reproduce

1) Import stereo footage in Nuke Studio/Hiero, and 'replace views' when prompted.

2) Drop and drag the footage into the timeline (to create a new sequence)

3) Above the timeline, select the 'Timeline Disk Cache' button, and then select 'Cache Sequence Range'


4) After the timeline is disk cached (yellow line), open the 'Monitor Output' tab within the 'Windows' menu.

5) In this new tab, set the monitor output knob to 'floating window'. This will create a monitor output using the contents of the sequence.

6) Within the monitor output tab, change the mode from 'Single' to 'Full Resolution Stereo'
Result: Black monitor output

Expected behaviour
Monitor output should show the stereo output when disk cached

Actual behaviour
Monitor output does not show the stereo output when disk cached and gives a black screen

Workaround
No known workaround, we would suggest clearing the timeline disk cache if using the monitor output stereo modes with stereo footage.

Reproduced by support
This bug has been reproduced in:
Nuke Studio 12.2v3 - Windows 10 - MacOS 10.15.3 - CentOS 7
Nuke Studio 12.2v1 - Windows 10
Nuke Studio 12.1v1 - Windows 10
Nuke Studio 12.0v1 - Windows 10
Nuke Studio 11.3v1 - Windows 10
Nuke Studio 11.2v1 - Windows 10
Nuke Studio 11.1v1 - Windows 10
Nuke Studio 11.0v1 - Windows 10 - MacOS 10.15.3 - CentOS 7

Unable to reproduce bug in:
Nuke 10.5v8 - Windows 10 - MacOS 10.15.3 - CentOS 7

Earliest version tested
Nuke Studio 11.0v1
- Timeline disk caching was introduced in Nuke 11.0v1

    We're sorry to hear that

    Please tell us why