NDI causes online crash

[Add]

I have a PC running WO 6.7.3 with an RTX A4000 graphics card, driver version 551.52, and Windows 10 version 22H2. When I frequently switch between normal programs (.WATCH) and programs containing NDI HX (NEWTEK Connect Spark HDMI), I occasionally experience extended ONLINE times, which eventually lead to a crash and the WATCHPOINT automatically restarts.

I have already tested with Windows 10 1607 + KB patches and also downgraded the driver to the 4XX version (the same as WATCHPAX), but the issue persists.

Has anyone encountered this problem before?

[jfk]

As a general rule, it would seem any live input that is turned on and off excessively eventually crashes. As long as i can remember, any version, any live input type.

And its never been a concern as the workaround in v6 is relatively easy. How to avoid this does impact your programming technique in a small way. 

On the main timeline, create a standby layer. on that standby layer place a live input cue that opens the input from time 0 to the end of the timeline. a layer for each live input you intend to use. Your stability problems will disappear and all your cues work as expected. i.e. the standby layer loads and runs its cues but does not display them (so they are ready to be activated from standby with no advance load time). The main timeline is always active, can not be killed, so it is the only logical choice for the job.

[Add]

On 9/6/2024 at 5:53 PM, jfk said:

As a general rule, it would seem any live input that is turned on and off excessively eventually crashes. As long as i can remember, any version, any live input type.

And its never been a concern as the workaround in v6 is relatively easy. How to avoid this does impact your programming technique in a small way. 

On the main timeline, create a standby layer. on that standby layer place a live input cue that opens the input from time 0 to the end of the timeline. a layer for each live input you intend to use. Your stability problems will disappear and all your cues work as expected. i.e. the standby layer loads and runs its cues but does not display them (so they are ready to be activated from standby with no advance load time). The main timeline is always active, can not be killed, so it is the only logical choice for the job.

First of all, thank you for your reply. However, my situation is not about actual frequent opening and closing, but rather for testing purposes.

Let me explain my client's usual workflow. When opening a program containing NDI inputs, there is no issue under normal circumstances. Then, when switching to another program that only contains video files, there is also no issue. However, my client occasionally switches between these two types of programs, and that's when the disconnection and loss of connection occur.

As part of the test, when I frequently bring the program containing only NDI inputs online and offline, everything works fine. When I frequently bring the program containing only video files online and offline, everything also works fine.

The disconnection issue only occurs when switching between these two types of programs, particularly when switching from an NDI program to a non-NDI program. During that transition, the first time the program goes online, there is a high chance of failing to go online and resulting in disconnection.

[Add]

For testing purposes, I tried removing the NDI HX DRIVER from the display computer, and the program no longer crashes or disconnects when switching (although NDI programs can no longer be displayed). Therefore, I believe the issue lies with the NDI HX DRIVER. I tried installing the latest 6.0 version of the driver found online, but the problem still persists.