vmixndihelper.exe crashes about 10 seconds after launch.

This also seems to crash vMix 20 upon exit as well.

Any ideas?

We recently (a few days ago) upgraded to Newtek NDI tools 3.0...could that be the culprit?

Using Scan Converter for screen capture (it has more control over what monitors/windows are made available via NDI than vMix Desktop Capture, which we require for privacy of producers). We were using Scan Converter with no issue prior to that (although, they may have updated Scan Converter...inexplicably Newtek doesn't put version info on any of the NDI Tools applications).

Also now using NDI tools' Studio Monitor for testing output from vMix.

I will do some experiments without those sources/destinations and try some other ones to see if it still gives problems, however I have closed Scan Converter and the Studio Monitor on the other machines on the NDI network

Once vMixNDIhelper crashes, it actually continues to work (you can even add more NDI sources) as long as you click Debug instead of Close Program on the crash dialog box. Close Program crashes vMix.

Also, once vMixNDIhelper crashes, when you later exit vMix it crashes vMix.

Not sure where any logging/debug info is stored or I would send it.

P.S. We've been waiting for NewBlue integration...that's great! Haven't had time to play around with it, but looking forward to it!

Sorry the the triple-post, but I spoke too soon. Popping up with receiving Scan Converter from NDI Tools 2.x clients.

Tried CCleaner complete removal of vMix and re-install, no change.

Anything more I can provide that would provide some insight to you?

NOTE: It will crash even after just loading a blank vMix project and letting it sit there a couple of minutes (not adding sources or doing anything else).

Tom Sinclair suffered an NDI helper crash during part1 of his latest broadcast (saw it on youtube)- not sure what changes he was making at the time.

This is a follow-up to the vmixndihelper.exe crash reported earlier in the thread.

Took me a long time to track this down, but it is related to a Newtek recommendation for assigning NDI traffic to one specific NIC. Apparently this causes vmixndihelper.exe to crash.

In a nutshell, here's the scenario:

We require dual-NIC setups in all our workstations on the production truck. Each machine has 1 20Gbit fiber NIC for LAN data (including NDI) on 192.168.3.x subnet, and one 1Gbit NIC for a separate audio over IP network (WheatNet audio) on 192.168.87.x. 3.x runs through a router and of course uses a default gateway, 87.x runs to a Cisco switch only with no gateway. There should be no cross traffic.

Unfortunately, there's no way to tell NDI to use only a specific NIC. So what happens is some NDI goes over the 20Gbit fiber as we'd like, and some ends up going over the WheatNet audio NIC.

After consulting Newtek, they explained their recommended way to achieve per-NIC routing is to block UDP 5353 (bonjour) on the adapter you don't want it to use, so NDI won't announce its presence. Then using NDI Access Manager, manually setup all the IP's you want to receive from (in our case, the 192.168.3.x addresses of the workstations).

So, this works fine...if vMix only receives NDI from one source. Once you add a second source IP, it crashes vmixndihelper.

Interestingly, you can continue to add the sources just fine, and it does indeed route all NDI traffic to the 192.168.3.x network as desired. It just crashes vmixndihelper in the process, which in turn seems to make vmix itself unstable upon close and other activities.

Sooo...not sure if this is a Newtek issue or vMix issue. Vehicle leaves for 2-week broadcast trip on Friday, would love to see if a resolution could be devised by then.

If I am missing something obvious, or if I can provide further help, please let me know.

Thanks!

Hi,

Just moved this to a new thread as it isn't about 20 per se.
I have emailed Rover some instructions to do some debugging on the error, so hopefully soon we will have a report we can file to NewTek.

Regards,

Martin
vMix

Where can I find "NDI Tools Access Manager" I have similar problem in vMix with newest NDI|HX driver. or can I simply uninstall the newest NDI|HX driver and install the older version ?