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.
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
- TonphisMar 21, 2021Copper ContributorHello, 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.- SteveK314Apr 05, 2021Copper Contributor
There are two issues I have seen that cause the Black Video.
1) You may need to ensure the Network connection is on PRIVATE network and not Public.
a. Go to Network and Internet Setting control panel
b. Select Ethernet
c. Select the Adaptor you are using
d. Select Private
2) There is a local windows firewall blocking the connection to the Computer running your switcher software. You can confirm this if you go into your firewall settings and see if the IP address of that Switcher computer is showing a blocked communication.
hope this helps
- frtbkrMar 22, 2021Copper ContributorInteresting, I tried to activate NDI on wifi and it didn't work. It is so random. I probably won't use the NDI it is not predictable.
- TonphisMar 22, 2021Copper ContributorToday we had an tweak session with the IT Helpdesk from our Customer. An we figure out that the problem comes from the DNS Service. There was Blocking rules. After disabling the blocking we can start NDI and all works fine