Hi Peter,


Were you running Teams on the same machine? Teams itself is a huge resource hog. I run it on an i7 / 2080 laptop and it usually hit 70% CPU just on its own with 8 callers.

Sounds to me more like a load issue. If you tested stand alone and all went well and during the event the same setup goes crazy it's to me an indication that the load would have made the difference

Hello people,

I have an event where the client would like to use Teams as a platform. The option, I like it, because I will need to place some participants, inside an art (3 people per screen). And when using Teams, the image quality is much superior to Zoom, where the work is much higher, as it will be necessary to pin people at the moment they will be placed live, and you will also need to zoom in on the capture, and with this, loses a little quality, unlike Teams that already comes in 720p (as far as I researched).

My problem today, is that the event will have 140 people in this room, and 50 who will make presentations (in groups of 3).

Today, I have an i7 9750 / GTX 1660Ti 6GB, and I don't know the load of Teams' NDI in relation to that number of participants that I will have to capture and separate into groups. In this case, I even thought of creating 3 to 5 ready-made groups, and gradually making changes, but the work will be very complex and may end up with even greater processing on the machine's GPU and CPU.

Does anyone happen to know what the approximate consumption of each Microsoft Teams NDI is? I think that because it is direct via their APP, network consumption is lower or is it like being on my local network?

Thanks!

@Peter

had a similar issue just yesterday. I was running a show with 3 MS Teams presenters in vMix, one of them had a screenshare presentation prepared - so 4 NDI sources total. Having all 1-3 presenters in a side by side multiview source with no issues at all. I asked the presenter with the screenshare to activate it well in advance so that I could prepare the Picture-in-Picture. As soon as he activated it all other video feeds changed to the beautiful purple placeholer animation. As soon as he stopped the screenshare all sources popped back in. Even weirder: the other camera sources seemed to activate whenever one of the presenters was speaking (kinda like the 'active speaker' NDI source, even though it definitely was a unique presenter NDI source I pulled into vMix).

A day before I tested all this with the presenters with no issues, on live-day however this got my blood pressure up a good bit :D

Also: fingers crossed for MS to implement unique audio streams instead of the fullmix. This would eliminate the need for muting speakers manually in teams or relying on them to mute themselves - which is never a good idea ;)

Hi All,

Just coming along to my first teams heavy show.

I can't see a definitive answer online, do you need the paid for version of teams to utilise NDI?

Cheers!

In our testing we found that Teams halved the resolution for each NDI source added. One source got 1080, two got 720, 4-8 got 360.