Since upgrading to vMix 20, we can no longer get the NDI output working in vMix.

I can see NDI inputs and view them, and if I run OBS on the machine I can output an NDI feed from that. But vMix never shows up as a source on any other computer.

I'm going to rollback and continue with vMix 19 for the time being as that was working fine.

Anyone else had this issue?

Hi,

Yes, that was the version we were running.

And I can confirm that NDI Output was enabled with "NDI On" under Outputs/NDI for Output 1.

EDIT: I should note that we saw the issue on two separate vMix 20 installations. One was a clean Windows 10 install. The other was an upgrade from 19 to 20.

I had the same experience today. No vMix NDI sources visible. NDI PTZ camera was visible.

- Tom

I just tried the previous version 51 of the and NDI output works NORMALLY.
But with the 52 it stops working.

Could somebody try running .51 on one computer and .52 on a second to see if the .52 can pick up sources from the first and vice versa?

This is to determine if the problem is on the send or receive side of things.

Same exact issue- just updated two machines to 20.53 and lost all NDI output from both machines. Still can pull in inputs from OBS but neither Vmix or OBS are seeing Vmix's NDI outputs.

EDIT: Just found an install from last December for 20.0.0.43... reinstalled with this and NDI is right back to working as expected on all machines. I had previously been on 20.0.0.51. Seems something in the 20.0.0.52 update is the root of the issue. Running Microsoft Windows 10 Pro Version 10.0.16299 Build 16299

Hi guys,

Can those having issues try the following:

1. Go to the start menu type in cmd and press enter
2. Type in ipconfig and press enter
3. Post the results here.

It looks like the problem might be related to how the gateway is configured on those machines.

Regards,

Martin
vMix

Hi Martin,

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : DC-FE-07-D2-A5-44
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::81c5:ef40:c8ff:27fe%14(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Lease Obtained. . . . . . . . . . : 08 February 2018 17:19:51
Lease Expires . . . . . . . . . . : 10 February 2018 05:19:51
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 64814599
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-C7-90-77-DC-FE-07-D2-A5-44
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

@rowby: It's Windows 10 1709, Build 16299.192

@admin: I sent the ipconfig output by email to you.

Investigation is going on...

I did some try and error to get it working. And I had a hit...

As soon as I disable IPV6 on the network adapter, .52/.53 are announcing their NDI sources.

I have only one client available for testing now. Could someone with the same problem test it?

Probably it's not the right solution yet, but it could give a hint to Martin what the underlying problem is.

Regards,
Patrick