Forum Discussion
NDI is not supported - error message
As soon as I want to enable the NDI support within my Teams client, I get the following error message:
What kind of problem do you think that is?
BTW. the meeting policy is adapted to accept NDI.
Thanks
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.
37 Replies
- Have you found a solution? I tried activating skype NDI on the same device and it works. I opened the location of the skype NDI files: "C:\Program Files (x86)\Microsoft\Skype for Desktop\resources\app.asar.unpacked\modules" and the file names are the same with Teams. So clearly they are using the same infrastructure to achieve NDI, and on Skype, it works, on Teams, it doesn't
- 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
- 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?
Still an issue, I have a several systems that are all tied together and a client just gave access to multiple accounts on their teams server. Logging in on a secondary machine, it states "NDI is not supported", I've seen that before and did the toggling of the GPU, but that isn't working this time. We have an event TODAY! The system is not only capable of NDI, it is running it for incoming and we've done other events via Skype from it. Teams, you need to get your self together.
- No multiple accounts
- NDI out contains mixed down audio
- NDI only works sometimes
- Watermark sporadically comes back on NDI (although I haven't seen it recently)
- I have the same issue, I run a lot of remote events and use teams NDI to route it to Wirecast. I installed teams to two PC's which NDI didn't turned on and Two mac's which both worked. Later I had to format one of them and it didn't work. So I have only one Mac which seems NDI is working but I need it to be working on my main PC so that I can reliably stream. I opened a ticket but so far no luck. Are there any solutions for this?
Hi Thomsch,
I'm still having this issue as of February 2, 2021.
Specs:
Microsoft Teams: 1.3.00.34662 (Enterprise 365 License)
Surface Book: Windows 10 Pro 20H2 16GB Intel i7 NVidia GeForce GTX 1050
Issue:
I try both disabling / enabling GPU hardware acceleration. Restart Teams. Enable NDI in Teams. Sometimes it turns on, sometimes it says NDI Not Supported.
If NDI toggles on in Teams, I test within OBS. NDI streams show up for about a second and then suddenly Teams reports that NDI is no longer detected (message at top of screen).
Any guidance or fixes would be appreciated. Other recommendations? Should I use Skype TX with Teams somehow to be able to use this for professional level productions?
mromeo Here's what I would do:
1. Make sure you have the latest Windows update, although your org might not have the latest. We're on 1909.
2. Get the latest nVidia drivers from nVidia.com, or install nVidia GeForce Experience to get automatic updates to keep you current.
3. Update Teams. The current version is 1.4.00.2879 so you're due for an update - https://aka.ms/getteams.
Hopefully having the latest versions of everything will fix your issues.
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.
DeltyZero (or someone else), just curious. How is the performance after disabling the GPU acceleration in Teams? Teams consume a lot of CPU already as it is so disabling the GPU would probably consume a lot more CPU which could jeopardize my vMix streaming productions...
As of today I still have this odd thing going on where I can't enable NDI from time to time. First of all I can't understand why I have to enable NDI under settings every time I start Teams. Why is not this setting stored as all other settings...? Secondly, why is NDI sometimes not available so you can't even enable it? This morning I had to restart Teams seven times before I even could enable NDI...
I run a lot of live streaming with vMix as primary platform and use Teams over NDI to hook up remote guests. It works great when Teams works as it should, but I have had a lot of issues related to NDI. That said NDI works just perfect together with all my other NDI-stuff so it must be something going on under the hood in the integration related to Teams and NDI itself.
I have tried to find more information regarding NDI and Teams, possible workarounds, MS roadmap of further improvement etc., but it's hard to find...
PeterBerglund for me it was hit-or-miss depending on which GPU the PC had. For my machines with on-board Intel GPUs I was able to turn off the GPU setting, enable NDI, then turn it back on and NDI stayed enabled. For my machines with nVidia GPUs, I had to leave the GPU disabled in Teams. I do a lot of streaming via Teams and Wirecast over NDI and haven't noticed any major issues in doing so. You can also turn off animations in the Teams settings to help reduce CPU usage with the GPU disabled.
I hope this helps!
DeltyZero Your solution " disabling GPU" worked for me too. Thnx.
Thomsch I have the same problem! Used NDI for displaying Teams video in OBS. Worked perfect! And then, it stopped working. Do you have any solution yet?
robkuijpers Hi all: There was a tweet offered in another discussion today that may be relevant here: https://twitter.com/john_moore/status/1325878237528993792
I'm aware of this menu and was able to use that, but that's not my issue.
Teams works great on Nov 11th.... didn't reboot or do any updates on my system. On nov 13th NDI wasn't working in teams. The toggle in settings would go green for a second, and the the app would crash "there was a glitch", and then it'd restart.
I've tried restarting the app many times, installing windows updated, checking for updates for teams, uninstalling the app, reinstalling, rebooting windows, nothing seems to work. I've also installed the latest NDI tools for windows from newtek.
This is the 3rd time in one week that NDI has stopped working (mid broadcast!). Very frustrating.
Below is the error that's left in event viewer after trying to toggle the NDI feature.
Teams.exe
1.3.0.26064
5f34aa2e
VCRUNTIME140.dll
14.27.29112.0
5f61068a
c0000005
0000000000001333
2104
01d6ba2026daebfc
C:\Users\xxx\AppData\Local\Microsoft\Teams\current\Teams.exe
C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
521b9237-f7bc-4bcf-aea4-c528a2e56eba
Teams.exe
1.3.0.26064
5f34aa2e
VCRUNTIME140.dll
14.27.29112.0
5f61068a
c0000005
0000000000001330
2120
01d6ba1fff057ff2
C:\Users\xxx\AppData\Local\Microsoft\Teams\current\Teams.exe
C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
933b6a59-a3b6-46a6-9855-8406a7f37290
Teams.exe
1.3.0.26064
5f34aa2e
VCRUNTIME140.dll
14.27.29112.0
5f61068a
c0000005
0000000000001333
4884
01d6ba1fe42110d2
C:\Users\xxx\AppData\Local\Microsoft\Teams\current\Teams.exe
C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
e4d9928b-f4ed-423c-8f51-9b9013808b1c
ThomschI have put in a service request about this. I'm having exactly the same issue. In terms of what it might be, my best guess is that it isn't supported outside the US, as I saw a comment on https://www.youtube.com/watch?v=Px1eEpd7ovw&ab_channel=NewTek saying:
"https://www.youtube.com/channel/UC9SMJZXNauBjb_RNawU0jFwhttps://www.youtube.com/watch?v=Px1eEpd7ovw&lc=UgwRgu1jWbWnF4mvt9d4AaABAg
It may be a bandwith issue?
My NDI was fine but when the network got busy it failed and then I saw that message. A restart solved it.
