Package Details: obs-ndi 4.11.0-1

Git Clone URL: (read-only, click to copy)
Package Base: obs-ndi
Description: Network A/V in OBS Studio with NewTek's NDI technology
Upstream URL:
Licenses: GPL2
Conflicts: obs-ndi-bin, obs-ndi-git
Provides: obs-ndi
Submitter: emileet
Maintainer: emileet
Last Packager: emileet
Votes: 9
Popularity: 0.034831
First Submitted: 2020-04-19 03:06 (UTC)
Last Updated: 2023-03-10 14:26 (UTC)

Latest Comments

1 2 Next › Last »

emileet commented on 2023-01-05 08:49 (UTC) (edited on 2023-01-05 08:50 (UTC) by emileet)

@dhtseany you should install ndi-sdk as your libndi dependency. i believe libndi-bin is outdated and only supports ndi4.

dhtseany commented on 2023-01-04 22:38 (UTC) (edited on 2023-01-04 22:42 (UTC) by dhtseany)

OBS 28 is throwing a message that the NDI 5 runtime can't be found. Anyone else see this? Btw I have libndi-bin installed.

NDI™ 5 Runtime not found. Please install libndi on your system. You can find a copy of libndi for Linux on obs-ndi's

Edit: More of the error from OBS' side:

info: [obs-ndi] [obs_module_load] Hello! (Plugin Version: 5.0.0 | Linked NDI Version: 5.0.10) info: [obs-ndi] [load_ndilib] Trying library path: '/usr/lib' info: [obs-ndi] [load_ndilib] Trying library path: '/usr/lib64' info: [obs-ndi] [load_ndilib] Trying library path: '/usr/lib/x86_64-linux-gnu' info: [obs-ndi] [load_ndilib] Trying library path: '/usr/local/lib' info: [obs-ndi] [load_ndilib] Trying library path: '/usr/local/lib64' error: [obs-ndi] [load_ndilib] Can't find the NDI 5 library!

dhtseany commented on 2021-10-31 19:25 (UTC) (edited on 2021-10-31 19:29 (UTC) by dhtseany)

This took up way too much of my Sunday to not at least leave myself the installation notes for next time...

1. Clean install of normal OBS Studio

$ sudo pacman -S obs-studio

2. Install sndio from Community repos. (this needs added as a dependency, by the way.)

$ sudo pacman -S sndio

2. Install obs-ndi, pick both -bin's to satisfy both of the dependencies, the -git's seem to break stuff.

$ sudo pacman -S obs-ndi

3. Enable the Avahi service

$ sudo systemctl enable avahi-daemon.service --now

lwilletts commented on 2021-02-21 16:49 (UTC)

Hey would it be possible to make sure avahi is enabled so that the plugin works as expected without having to track down a github issue saying to check that it's loaded.

celilo commented on 2020-05-16 00:56 (UTC)

Thanks for the info. I added another comment at ndi-sdk requesting the change.

emileet commented on 2020-05-16 00:50 (UTC) (edited on 2020-05-16 00:50 (UTC) by emileet)

@celilo agreed, several requests were put forward to the maintainer however it appears they fell on deaf ears

celilo commented on 2020-05-16 00:32 (UTC)

Thanks, I can now compile both ndi-sdk and obs-ndi without manually modifying the PKGBUILDs. I still believe, per my comment in ShayBox's build that we should simply communicate with other package maintainers and have the ndi-sdk maintainer add a versioned provides, such as "provides=('libndi=4.9.1')". In doing so, the user installing any of the packages will know if manual intervention is required and can notify the maintainer of the issue.

Currently Shaybox's build prevents installing two completely compatible programs, and this build allows a small possibility of breaking another package if compatibility is broken.

emileet commented on 2020-05-07 12:11 (UTC)

@Fresco thank you for the suggestion, i believe upstream is already aware of the issue

Freso commented on 2020-05-07 11:29 (UTC)

Re: 1: I’m not sure what you mean, ShayBox? The "obs-ndi-4.9.0.tar.gz" file is an archive of the plugin’s sources, not a binary build of the module. This is perfectly as it should be.

Re: 2: Agreed, but until ndi-sdk provides libndi, no reason to make a change here.

Re: 3: Have you considered filing an issue at (or maybe it’s an upstream issue?) emileet? Seems like something other OBS plugins would need to compile too, and it is a bit heavy to download the complete OBS source code when what is needed should already be available. However, it is not an issue with this package as-is, but an issue that needs fixing either in the Arch Linux package and/or with upstream.