If the problem shows even up on studio monitor this must be a lack of resources. vMix is using full NDI as outputs. They are high bandwidth. Maybe take a look at the network utilization.

Hi Mavik,
It is unlikely a lack of resources as the specs of the computer are quite high (see original posts for specs) and this happens with only 1 input to the computer. Using the same network-switch-cable combination on a much lower specked computer the NDI feed has no problem, so it is not a network issue as far as I can tell. Also, non vMix NDI sources (Birddog, Kiloview etc.) work perfectly well, it is only vMix NDI sources that exhibit this issue. The problem exists on any vMix source from any computer on the network, so it is not from 1 source or 1 specific computer. So long as it is a vMix souce the drops are very high. I have tried Birddog Dynamo to view the traffic, and I can see all the drops on the vMix souces while every other NDI source is perfect.

Maxi

Have you tried updating the vMix NDI files manually to the latest available?

Unfortunaey I do not have a resolution to this as yet, but I am continuing to test when time allows. Should I find a solution, I will be sure to update this post

Maxi

I have manually updated to the latest NDI in vMix to no avail.

I can use NDI without problem in my network. We have 12 PTZ NDI cameras in network and can work with all of them without drops but cant receive any NDI from another Vmix.
Vmix NDI works good for long time but now it´s a big problem... Vmix Doesn´t work anymore.

I know this is about 3 months old but i'm pretty sure this is due to the Windows scheduler with P and E cores on 13/14 gen processors. A simple way of testing this without having to say change the affinity mask in windows task manager or power script every time is to do it in BIOS. Depending on your MB it can be called Gamer Mode where you turn off E cores during gaming and then set vmix to the gaming list. Some even allow you to hit Scroll Lock to disable e-cores on the fly which is what i have done for a quick fix and when vmix loads the scroll lock button is triggered using a PowerToys and or my keyboard comes with a way to do this as i have many keys remapped but you can do something like this using any tool.

It's (in my opinion) an ugly fix and since this was my first attempt to troubleshoot\fix this issue i haven't really dug deeper into it. I'm still mostly on windows 10 for production and or using xeons for big productions (xeons and large NDI workflows like each other) so i run into this problem (or did) once or twice a quarter where i'm using laptops on small gigs that run the 13gen and windows 11. Disabling E cores (or parking) has no negative effect due to these shows not being all that big. So definitely test it but i'm 90% sure that's the problem you are running into.

Perhaps @admin can shed some light on how the inputs\outputs for NDI within vmix use the cores or if it just lets windows handle them and if they can force the threads to only run on performance cores for those ndi inputs threads to insure they don't get caught up in the windows scheduling madness causing these drops.

-King