ID 491569 - Looping clips with a Blackmagic Monitor Out device enabled can cause tearing on the Monitor Out display

Problem summary
Looping clips with a Blackmagic Monitor Out device enabled can cause tearing on the Monitor Out display

Customer reported version
13.0::13.0v4 hiero.13.0v4

Customer reported platform
macOS 10.15

Steps to reproduce

1) Download and extract the attached TestFrames.zip

2) Open NukeStudio on a machine with a Blackmagic Monitor Out device

3) Import the test frames, and add it to a sequence/timeline

4) Set your Sequence Resolution to 2048x1080 2K_DCP and the Frame Rate to 24

5) Open the Monitor Out panel and enable monitor out, selecting the Blackmagic device

6) Set the Display Mode to 2K 2048 x 1080 - 24p and the pixel format to 10 bit 4:4:4

7) Playback the sequence, letting it loop several times, depending on the machine you will start seeing tearing artefacts when the sequence loops:

​

8) If you don't see tearing, while the timeline is still playing, try click different frames in the timeline, this can cause tearing. Once you get a couple of tears while clicking, let the playback loop again, and you are more likely to see the tearing when looping. NOTE: This does not happen every time, so it might take a few attempts.

Expected behaviour
For the sequence to loop back seamlessly.

Actual behaviour
Tearing artefacts can appear when the sequence loops:
​

​

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
NukeStudio 13.0v5 - Windows 10 - BlackMagic Decklink 4K Extreme - 11.7 Driver
NukeStudio 13.0v5 - macOS High Sierra - BlackMagic UltraStudio 4K Mini - 12.1 Driver * Much harder to reproduce on
NukeStudio 13.0v4 - Windows 10 - BlackMagic Decklink 4K Extreme - 11.7 Driver

Unable to reproduce bug in:
NukeStudio 13.0v5 - Windows 10 - AJA Kona 4 - 15.5.3.5 Driver
NukeStudio 13.0v5 - macOS High Sierra - AJA IO 4K Plus - 15.5.3.8 Driver
NukeStudio 13.0v3 - Windows 10 - BlackMagic Decklink 4K Extreme - 11.7 Driver

Earliest version tested
NukeStudio 13.0v3 - Previous NukeStudio versions had bug ID 427913 which makes it impossible to see this issue