Forum Discussion
NDI is not supported - error message
- Nov 17, 2020
Thomsch I got mine to work by disabling GPU acceleration in the General settings and then restarting Teams. On my system with an Intel GPU, NDI would be selectable after a reboot but would then turn off with the "NDI is not supported" error as soon as I started a meeting. Interestingly enough, after I disabled GPU and enabled NDI, I was then able to turn GPU acceleration back on and NDI continued to work (at least for now.)
Hopefully this works for other people - we'll see how it goes over the next few events.
Sorry for not being active here for a couple of days. Just to contribute with my input and some answers to questions since my last post:
- I use a Dell workstation with an Intel Xeon W-2145 CPU (16 logical processors) base clock @3.7GHz, 64GB, SSD, NVIDIA GeForce RTX 2080 TI (11GB), 1Gbit LAN.
- I've been using Teams 1.4.00.4167 for a while now which I consider rather stable.
- On a 2 hours long live-conference last week I had 9 NDI-sources from Teams into vMix (24.0.0.51) without any noticeable delays - and no crashes at all 🙂 During that session my CPU was around 55%, but worth mentioning is that in addition to the 9 NDI Teams-sources, I had 4 NDI-HX sources connected as well via the LAN, 1 HDMI in and 1 HDMI out from a BMD card, as well as both recording and streaming active in vMix (H264, 20 respective 6 Mbps with HW-encoder).
- As TechSavvy says, and I have posted here before, NDI is not available at all after re-boot in Teams. After killing Teams as a process completely and re-launch Teams, it's normally possible to enable NDI. I would say that prior the 1.4.00.4167 release it happened randomly that you had to restart Teams several times before it was even possible to enable NDI. As I have posted here earlier I can't understand why this setting isn't stored like all other settings...
🙂
/Peter
- frtbkrMar 27, 2021Copper Contributor
Thank you for the reply. Well, I plan to use the NDI If I can make it work 🙂
Currently, I cannot turn on the switch. Also, NDI has to be reliable. I read few people had crashes. In a live show, if teams crashed it is over. So I plan to have 16 people conference 2 different laptops with teams running 9 NDI outputs each going into a gigabit switch which then ingested by 16 NDI monitors in another laptop which HDMI outs to Wirecast with a Capture card.
All this has to rely on teams not crashing :). Any tips?- PhilipG1815May 07, 2021Copper Contributor
frtbkr How did this go? I find the maximum 9 NDI feeds from Teams into Wirecast a real issue for large events. This could be a solution - did it work OK?