Question / Help NDI™ Runtime not found

mrvwman

New Member
If you're just trying to get rid of that message and NDI entirely here's what worked for me:
1/ Uninstall OBS, and all NDI tools
2/ rm -rf ~/Library/Receipts/net.tt2468.obs-ndi.*
3/ rm -rf ~/Library/Application Support/obs-studio
4/ Reinstall OBS
 

san_drino

New Member
"NDI™ Runtime not found.
Download the installer here: https://ndi.palakis.fr/runtime/ndi-runtime-4.5.1-macOS.pkg"

Recurring message every time I open OBS and, of course, no NDI source available. I've downloaded and tried to install, re-install, erase OBS and abs-studio in LIBRARY>>Application Support, tried previous versions and multiple NDI installs - all to no avail.

Here are the specs :

MacBook Pro (15-inch, 2019)
Mojave 10.14.6
OBS : 25.0.8
obs-ndi-4.9.0
ndi-runtime-4.5.1-macOS

I haven't sound other threads with an answer, so starting this in hopes of a solution. This seems straight forward, yet it's not working. I've even custom reinstalled obs-nid-4.9 and de-selected "NDI Runtime".

Anyone else had this issue or know a work around?

Thanks in advance,

Jon
Hi Jon, check to see if there is a file called libndi.4.dylib in the /usr/local/lib folder, you can get to it from the Finder's “go” and ‘go to folder" menu. If it's not there, download it again from here: https://github.com/obs-ndi/obs-ndi/releases/tag/4.8.0 and install it. If the filename does not have .4, simply rename it. Also, note that you can download the latest runtime and rename it. If for any reason it does not work, download Suspicious Package from here: https://www.mothersruin.com/softwar...load-update&utm_medium=suspicious-package-app , open the .pkg file and drag the dylib file directly into the folder. I hope this helps.
 

Sam waters

New Member
Ive the exact same issue. However nothing seems to be working. Im on mac-os big sur Version 11.6, ive tried re-instaling and downloading older versions but it still wont work.
 

DJClientel

New Member
I found a solution!

The problem is obs-ndi-4.9.0-macOS.pkg does not come with the needed https://ndi.palakis.fr/runtime/ndi-runtime-4.5.1-macOS.pkg. I figured this out when I went into advanced details during the install. The install said it was installing runtime, but it had a 0kb beside it. After some further looking on https://github.com/Palakis/obs-ndi/releases I found in their old release of obs-ndi 4.8.0 a runtime package that works, https://ndi.palakis.fr/runtime/ndi-runtime-4.5.1-macOS.pkg. Download that runtime package, go through the install and that should fix your runtime error.
I tried this fix but it did not work... What did I miss?
 

wjack

New Member
(*fixed*)
Apparently I'm able to send a signal from my m1 macbook to my windows PC (including audio) no problem, but I can't to do the opposite (which is what i need).
I've tried everything I could find online, but still my arm64 OBS (or my NDI video monitor) can't see the PC NDI signal being broadcasted.
Since one way works but not the other, might it be a network issue?
Anybody has any clue?
Thanks a lot.

UPDATE: for anybody having the same issue:
I used NDI Access Manager and set the IP of the windows PC as an external source. Now it works perfectly.
 
Last edited:

Matt

New Member
I've had to work out a solution for this problem a couple times now and my results have been consistent. You don't need to grab downloads from the Internet Archive or from unofficial sources (websites that aren't ndi.video). I've provided all of the steps anyone needs in a similar thread. The thread is specific to Apple Silicon Macs, but the steps should work for Intel Macs as well (in theory).
 

jake.gilbert

New Member
SOLUTION:

Running MacOS. I had this exact issue and tried everything that people suggested — to no avail. Then I changed the permissions so that OBS had access to the folder storing the NDI Runtime file to allow all access. Then everything worked perfectly!

Just went into my Computer's drive (shift+cmd+H), then hit shift+cmd+. and chose the greyed out folder "usr". Then, "local" and finally right-clicked on the folder "lib" and chose "Get Info". Then, adjusted the permissions to allow Read + Write, restarted OBS and everything worked perfectly!
 
Top