Hello everyone,
I am reaching out and ask for your help in solving a big issue.
In a visual radio studio we have:
- 6 PTZ cameras running HX3 NDI outputs on a dedicated NDI network VLAN
- one main vMix PC doing the 16/9 video production
- a secondary vMix set for vertical 9/16 production
- one playout PC that runs video files on NDI output
- all Audio is on AoIP Axia Live wire, on a separate VLAN
All the PCs each have 3 network cards,connected one in the NDI VLAN, one in Axia VLAN and one in the LAN/internet enabled VLAN.

On all the PCs we have installed NDI tools and indicated in the NDI Network Manager the use of the dedicated network card they is connected in the NDI VLAN.

We have also set the metric on the NDI cards to 1, as we have found some advices, and set permanent route for the NDI trafic on that specific network card.

But even we have done all that, each time we enable in vMix one or more NDI outputs, those streams end up being broadcasted through the LAN network card instead of the dedicated NDI card.

And the result is that the PGM from vMix PC1 is not properly "seen" or received on the second vMix PC2, and vice-versa.

So my question is: is there a specific procedure that could indicate to vMix what network interface to use for the NDI trafic and not push it into the same network interface that he is using for internet streaming?

I am looking forward to any advice you may have.
Thank you.

Perhaps you could try the NDI_CONFIG_DIR "trick". Basically this would force the running app to force the sdk it uses for NDI to use the private config. As you know NDI 5 and higher (use the latest and update vmix to use the latest by swapping out the dll's in its folder) allows a exclusive NIC config but that affects the whole system and all apps and you just want vMix to use that particular NIC. So the trick is to run vMix under a private NDI_CONFIG_DIR variable so when it loads its SDK the SDK adheres to the private config that is set within that system variable thats only visible to vMix and no other app keeping everything else as is.

So you would create a directory say C:\MySpecialVMixNDIConfig and create a file in there called "ndi-config.v1.json" The contents of this file should be:

{
"ndi": {
"adapters": {
"allowed": [
"xxx.xxx.xxx.xxx"
]
}
}
}

Where xxx.xxx.xxx.xxx is the IP of the allowed nic. Then and this is important you need to execute vMix via a script that sets the system variable pointing to the config file. the system variable being NDI_CONFIG_DIR. So

.bat file named RunnSpecialvMIX.bat
@echo off
setlocal

set "NDI_CONFIG_DIR=C:\MySpecialVMixNDIConfig"
start "" "C:\Program Files (x86)\vMix\vMix64.exe"

endlocal


Make sure the IP doesn't change and if it does then you need to update the config in your special directory. I have not tested this yet since i'm out but you can find the support for such a setup here:
https://docs.ndi.video/a.../platform-considerations

-King