Sep 07 2020 01:12 AM
Sep 07 2020 01:12 AM
Hi, we just turned on NDI for our organization, and I see it in my Settings>Permissions panel.
When I try to activate it i get the message saying "There was a problem downloading the file
Sep 07 2020 09:21 AM
Hi @DanielWM ,
It sound like you must have followed or the following had already been done for your account with the fact that you have the option:
Not sure it would be required for activating the setting itself within your Profile settings but would be interesting to see if this is allowed within Meeting Policies in the Teams Admin Centre. But like I say I would expect this to just impact you at the point of making use of it within a Meeting.
I would do a right click on the Teams icon in the system tray and do get logs. See if there is anyone more meaningful error message wise in there.
Sep 07 2020 10:30 PMSolution
Oct 06 2020 11:05 PM
@EA-2020 I am on Windows on both of my computers.
I've just formated and reinstalled windows on my desktop, this didn't help either.
The interesting thing is that it works for all of my colleagues except me.
I've also tried logging on to users in other tenants where I have activated the NDI policy in Teams admin center, this did not help.
Oct 06 2020 11:10 PM
Oct 06 2020 11:27 PM
@HenryPhillipsNimbitech We all use the Surface series computers, mainly Surface books.
I have a desktop computers as well for video editing and streaming, hence why I want NDI to work :D
We have not tried to log into my computer with their credentials, but I have tried to log into other users in other tenants where I have activated NDI policy, this does not work either.
As mentioned in the previous post, I just formated my computer without it helping.
Oct 07 2020 12:15 AM
Oct 23 2020 01:31 AM
I have the same issue... I reviewed the error logs in teams (~/Library/Application Support/Microsoft/Teams/Logs.txt and found the following:
PluginDownloader::downloadAsync - Failed to download and install ndi bundle due to reason=DIR_MOVE_FAILURE, details=Message: EACCES: permission denied, rename '/Users/ben/Library/Application Support/Microsoft/Teams/plugins-tmp/ndi-2020.20.01.11/extracted/libndi.4.dylib' -> '/Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/slimcore/bin/libndi.4.dylib'
This indicated that there was a permission issue here: /Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/slimcore/bin which is inside the package contents of the application. Mine had system 'read/write access' and everyone 'read'. After updating the folder and its contents to grant read and write for my user the NDI package downloaded and installed into the folder.
I now have another issue in that when I download the NDI package I get a new error saying 'NDI is not supported.'
slimcoreVersion: 2020.20.11, isSlimCoreHotSwapped: false, reason: NDI not present yet, reasonCMD: NDI not present yet, ndiVersion: 2020.20.01.11, status: success, scenario: 6f6b728c-e35a-4bf8-b1b2-637125d6c133, scenarioName: intialize_ndi, name: intialize_ndi, step: stop, sequence: 1, delta: 262, scenarioDelta: 262, elapsed: 12645, stepDelta: 262, vdiMode: 0, eventpdclevel: 2, Scenario.Name: intialize_ndi, Scenario.Step: stop, Scenario.Status: success,
Nov 04 2020 11:53 PM
I have exactly the same issue. Had to change the permissions in the Application in order for the NDI libraries to be copied over and now it says "NDI not supported" with the same error message in the logs.
Nov 05 2020 06:40 AM
@DanielWM I changed the permissions of the bin folder inside the Microsoft Teams application at /Applications/Microsoft Teams.app/Contents/Resources/app.asar.unpacked/node_modules/slimcore, so that the libraries could be moved during activation of NDI. But as I wrote, still not working.
Feb 24 2021 03:27 AM
@micudaj I found a workaround for the "NDI is not supported" issue:
Mar 02 2021 06:55 AM
Yo tengo el mismo problema, cada tanto me sucede lo mismo. Lo soluciono cerrando sesión, luego cierro la aplicación y vuelvo a iniciar sesión y ahi consigo que ande, pero a veces trabajando en vivo es un poco arriesgado, espero encontremos una solución mas solida @DanielWM