Forum Discussion
NDI is not supported - error message
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.
- My workaround in Teams for computers that gives me "NDI is not supported" (currently 3 of 4) is to log out of Teams and then log back in. Then, I can activate NDI. After a restart or a shutdown, I have to do the process over again.
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
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?
- Hi,
As I have been complaining in this thread before, I just want to say that things move forward and improves! Teams has never worked as good with NDI as it does right now (1.4.00.4167). That is together with vMix anyway (last version of vMix 23, but also the new v24.0.0.51). Thanks Microsoft for whatever you have done. It's unclear what kind of fixes MS have done as nothing is documented in their release notes as far as I have found. Anyway, it just works better, significantly lower CPU load, better audio, better video and more stable if you ask me.
I use Teams with NDI connection to vMix on a daily basis and often sessions for several hours. I have just experienced one (1) disconnection during the last couple of weeks and that happened during the test phase before the actually broadcast session. One finding there was that I still had to restart Teams several times to get NDI to kick in. After the first restart NDI was not available under the settings menu in Teams. After the second restart I was able to enable NDI and then I could connect to a meeting and enable NDI broadcast in the dropdown menu.
First I don't understand why NDI just stops to work suddenly. Even if it has happened only once since the last update, I don't like it and I want to understand why. Secondly I would like to have some kind of "reset" solution that could be activated DURING the call if it happens - either an automatic reset or a manual controlled solution. It's really frustrating and time consuming during a live session to have to leave the call, restart Teams, enable NDI, restart the meeting, reconnecting to all Teams NDI-sources in vMix... Thirdly I can't understand why the enable NDI setting is reset to disable every time you close Teams. Why is not this setting stored? And why is not NDI available at all sometime? Really look forward to a fix!
Long story short: Things can be even better, but it works quite well now after all.
Top of my wish list are:
1. The above mentioned fix and the "reset NDI" function.
2. Have separate audio for each NDI feed.
3. HD quality.
4. I have never got the Gallery NDI feed to work, so that would also be a nice-to-have function. Must be some bug as it's not a visible NDI feed, not in my system anyway.
🙂
/Peter- Hello Peter, How many ndi feed have you got out of one machine? how long was it? were there any delays? what kind of PC do you have?
- Hello, I have now found out what is wrong with me. For this project, we use a connection at the customer's premises. This apparently runs through a proxy or something similar that blocks the communication of NDI in teams. When I try to activate NDI in the same setup via an LTE router, it works immediately. Even without restarting teams. Then I can reconnect the PC to the home network and use it.
But now I have the problem that I can see the users via NDI in VMix. BUT now I only get a black picture in VMix and no audio signal. If I switch back to the LTE connection, I immediately have picture and sound again.
Funny is that I have no problem with NDI via MAC (OSX 10.15.7. Teams version 1.4.00.4971). There I can activate NDI in the company network and also get picture and sound in VMix.
hello we have same Problem at the moment here.
On a W10 PC that usualy runs NDI and Teams at the moment there is no way to get it work.
Microsoft Teams Version 1.4.00.4167 (64-Bit). Sie wurde zuletzt am 15.03.21 geupdatet
W10 System, latest updates, Intel CPU i7
Any ideas what could the problem?
We try to enable ndi on about 5pcs where it usualy work. We just get it work an a mac PC with teams
- It just doesn't work. I contacted Microsoft, they are looking into it but even if it would work, I can not trust the software. As the guy above mentioned. It does crash and I can not accept that. Looking for a stable option.
