Package Details: obs-ndi-bin 4.13.0-1

Git Clone URL: (read-only, click to copy)
Package Base: obs-ndi-bin
Description: Network A/V in OBS Studio with NewTek's NDI technology
Upstream URL:
Keywords: libndi obs-ndi
Licenses: GPL2
Conflicts: obs-ndi-git
Provides: obs-ndi
Submitter: joow
Maintainer: Jat
Last Packager: Jat
Votes: 9
Popularity: 0.000237
First Submitted: 2017-10-10 19:54 (UTC)
Last Updated: 2023-11-17 01:09 (UTC)

Latest Comments

1 2 3 4 Next › Last »

Jat commented on 2020-05-26 03:44 (UTC)

plz remove /usr/lib/x86_64-linux-gnu. arch does not use this location

TomCatT commented on 2020-05-07 23:54 (UTC)

@emileet HA!!!! THANK YOU SO MUCH. I was thinking way to deep for this and it was as simiple as that.

emileet commented on 2020-05-07 05:49 (UTC) (edited on 2020-05-07 05:49 (UTC) by emileet)

@TomCatT remove libndi3-bin and install obs-ndi-bin with libndi-bin as it supersedes libndi3-bin.

TomCatT commented on 2020-05-07 02:52 (UTC)

Has anyone received this error?

error: file owned by 'libndi-bin' and 'libndi3-bin': 'usr/lib/'

shaybox commented on 2020-05-05 01:54 (UTC)

@terodero I notified the developer that their change broke it, they changed the path which only Ubuntu's patched obs reads from, instead of the official path, until they change that i'll implement a fix.

emileet commented on 2020-05-04 11:10 (UTC)

here's a patch to fix the issue

i also provide obs-ndi which doesn't have this issue

terpderp commented on 2020-05-03 23:21 (UTC)

I am curious if this is just me, but I had an issue with the 4.9.0 release. The plugin seemed to disappear from OBS. It seems to install the plugin to /usr/lib/x86_64-linux-gnu/obs-plugins when other obs plugins are installed /usr/lib/obs-plugins. OBS doesn't see it is a plugin (OBS

This is referenced in the 4.9.0 release here as a bugfix for Ubuntu/Debian.

Copying the plugin from /usr/lib/x86_64-linux-gnu/obs-plugins to /usr/lib/obs-plugins fixes it and works as expected.

shaybox commented on 2020-04-29 06:11 (UTC)

@emileet fixed

emileet commented on 2020-04-17 22:04 (UTC)

easy fix for the perms would be to append this to the PKGBUILD

chmod 755 $(find "${pkgdir}" -type d)

Freso commented on 2020-04-17 21:40 (UTC)

Directories (at least some of them) are given 777 permission instead of 755 permissions, meaning that if they get installed by this package they will be world writeable.