ID 504360 - An error is displayed in the Viewer, when viewing the final frames of a ProRes 422 LT file

Follow

Problem summary
An error is displayed in the Viewer, when viewing the final frames of a ProRes 422 LT file.

If you use an OCIO config, with custom LUTs, the following error will instead occur on the same frames:


 
Customer reported version
N/A
 
Customer reported platform
N/A
 
Steps to reproduce
 
1) Firstly, you will need a custom OCIO config, with a custom LUT. An example OCIO config, along with the corresponding LUTs, is attached.
 

2) Set the OCIO environment variable in a terminal/Command Prompt session so that it points to your custom OCIO config. For example

Linux: export OCIO=/path/to/config.ocio 

Windows: set OCIO=/path/to/config.ocio


3) Then launch Nuke Studio from the same terminal/Command Prompt window.

 
4) Import the attached file (File > Import Files(s)...) then drop it on to the Timeline.
 
5) Scrub to the last frame of the clip, and notice the error in the Viewer:

6) Double click the clip in the Bin, to open its Properties and, if you are using the attached OCIO config, change the Input Transform knob to AlexaToRec709.

7) Scrub to the last frame of the clip and notice that a different error is displayed when scrubbing to the last frame again.

 
Expected behaviour
All frames of the QuickTime should be displayed without any errors.
 
Actual behaviour
The last frame of the file displays the following error: 

If you are using an OCIO config with custom LUTs, then the following error will occur instead:


Workaround
Unknown.
 
Reproduced by support
This bug has been reproduced in:
Nuke Studio 13.1v3 - Linux CentOS 7 - Windows 10
Nuke Studio 12.1v5 - Linux CentOS 7
Nuke Studio 12.1v4 - Linux CentOS 7
Nuke Studio 12.1v3 - Linux CentOS 7
Nuke Studio 12.1v2 - Linux CentOS 7 - Windows 10 - Regression
 
Unable to reproduce bug in:
Nuke Studio 12.1v1 - Linux CentOS 7 - Windows 10
 
Earliest version tested
Nuke Studio 12.1v1
- This issue doesn't appear in this version and has regressed

    We're sorry to hear that

    Please tell us why