Hi,

We have a customer who insists on using "approved" Windows builds. VMix runs up fine and can generate NDI, but it cannot receive it. The same machine with a standard Windows build works fine in the same environment.

NDI tools on the same locked-down machine will receive the NDI fine - including outputs of the local vMix installation. VMix creates thumbnails when selecting the NDI source, but just displays black when you add one as a source (either a remote source or even its own output).

We've found this Knowledgebase article (https://www.vmix.com/knowledgebase/article.aspx/129/diagnosing-blank-ndi-inputs) and it isn't any of those things - network is "private", firewall is allowing all UDP and TCP both in and out (it can't be entirely disabled annoyingly) and there are exclusions for the vMix executables that match the ones for NDI tools, and though in the real world it will be dual-homed, we have tried it on only a single network with no change in behaviour.

We've tried running it as a local admin on the machine - no change.

Can anyone think of any Windows security settings or other options which we can check, which could cause this behaviour?

Thanks in advance for any ideas.

Chris

I am confused. What constitutes an "approved" Windows build?

That sounds much too reasonable. My head was facing towards Microsoft and not vMix.

Actually what threw me off is it says '"approved" Windows builds' and not '"approved" vMix builds'

Thanks!