Arch Linux User Repository

Happy to co-maintain by the way

Hey there!

I have 2 unrelated machines failing to produce the build correctly and after a bit of digging I found that Arch's obs-studio package has moved to 32.1+, which deprecated obs_properties_add_button in favor of obs_properties_add_button2, and DistroAV 6.2.1's build treats that deprecation warning as a hard error via -Werror, erroring out the build process.

Until upstream resolves this I have a patch that fixes src/ndi-filter.cpp to use the new function (passing the filter's data pointer as the required extra argument) and it wires that patch into the PKGBUILD via a prepare() step, unblocking the build without waiting on an upstream release.

To apply the fix first edit the PKGBUILD as follows:

diff PKGBUILD PKGBUILD-temp 
6c6
< pkgrel=1
---
> pkgrel=2
16,17c16,26
< source=("${pkgname}-${pkgver}.tar.gz::${url}/archive/${pkgver}.tar.gz")
< sha256sums=('d40dbada1185fb1cdd1b9bb03a5d0641cfa0690aec08e53822e7bcdc5883190f')
---
> source=("${pkgname}-${pkgver}.tar.gz::${url}/archive/${pkgver}.tar.gz"
>   "distroav-obs_properties_add_button2.patch")
> 
> sha256sums=("d40dbada1185fb1cdd1b9bb03a5d0641cfa0690aec08e53822e7bcdc5883190f"
>       "66645baf5efadde85e48936593d6111db3c5e7d51cc6a370a98c797ff007d5da")
> 
> prepare(){
>   cd "$srcdir/DistroAV-$pkgver"
>   patch -p1 < "$srcdir/distroav-obs_properties_add_button2.patch"
> 
> }

Then make the file distroav-obs_properties_add_button2.patch at the same level as the PKGBUILD and paste the following:

--- a/src/ndi-filter.cpp
+++ b/src/ndi-filter.cpp
@@ -105,7 +105,7 @@
    }
 }

-obs_properties_t *ndi_filter_getproperties(void *)
+obs_properties_t *ndi_filter_getproperties(void *data)
 {
    obs_log(LOG_DEBUG, "+ndi_filter_getproperties(...)");
    obs_properties_t *props = obs_properties_create();
@@ -119,14 +119,15 @@
    obs_properties_add_text(props, FLT_PROP_GROUPS, obs_module_text("NDIPlugin.FilterProps.NDIGroups"),
                OBS_TEXT_DEFAULT);

-   obs_properties_add_button(props, "ndi_apply", obs_module_text("NDIPlugin.FilterProps.ApplySettings"),
+   obs_properties_add_button2(props, "ndi_apply", obs_module_text("NDIPlugin.FilterProps.ApplySettings"),
                  [](obs_properties_t *, obs_property_t *, void *private_data) {
                      auto s = (ndi_filter_t *)private_data;
                      auto settings = obs_source_get_settings(s->obs_source);
                      ndi_filter_update(s, settings);
                      obs_data_release(settings);
                      return true;
-                 });
+                 },
+                 data);

    obs_log(LOG_DEBUG, "-ndi_filter_getproperties(...)");
    return props;

If you're hung up with decoder errors try to install ffmpeg7.1 from the aur.

And this just got worse, as now ffmpeg7.1 can no longer be built against svt-av1 v4

Looks like we're broken again with the recent upgrade of svt-av1 from major version 3 to 4; I was able to workaround by extracting the version 3 .so files from my last cached package back into /usr/lib, that's not great...

Has anyone used this since the update to ffmpeg 8.x? It seems they (ndi team?) are now built against ffmpeg 7.x? Anyone got a solution to get functional again?

For those getting the "video decoder not found" message, you simply need to install the ffmpeg4.4 package and should be good to go.

Ok, I wanted to come back and provide an update for anyone else that encounters the same thing I did: It wasn't the GPU, I borrowed my RTX5500 from the working system and the problem persisted so that proved it wasn't driver related.

I dug deeper into all of the output of OBS when launched from the terminal and I noticed a complaint about a missing VLC module. This confused me as I never needed to install VLC for OBS Studio to work in the past but I realized that all of my other working systems had VLC present so I thought I'd give it a shot. Sure enough, after I installed VLC media player the message finally cleared up and I can see my cameras again directly. I'm not 100% sure why this fixed my problem though I assume there's some decoder that it includes that, once installed, provided other apps with the missing decoder module that in turn made the NDI streams work again.

Additionally, I'm not sure if obs-studio or obs-ndi needs to add VLC as a required dependency but now that I know how to resolve the issue I wanted to at least share my knowledge with others who might be in the same boat I was in.

To provide an update on my last reported issued, I'm even more stumped than when I posted my original message. I have another working system who can see the output from any of my 3 different NDI cameras and it works perfectly. Bound and determined to identify why this fresh, newly installed system from scratch is producing this oddball "Video decoder not found" error I decided to compare the installed packages between what's installed on the working system vs. what's installed on the fresh but not-working system.

These are the related packages from the working system:

local/libindi 2.0.4-1
local/libndi-bin 5.5.3-2
local/obs-ndi 4.11.1-1
local/sndio 1.9.0-1
local/obs-studio 29.1.3-1

Here are the packages on the brand new system:

local/libindi 2.0.4-1
local/libndi-bin 5.5.3-2
local/obs-ndi 4.11.1-1
local/sndio 1.9.0-1
local/obs-studio 29.1.3-1

As you can see I have identical package versions. I then got the idea of testing NDI's core functionality on the new system by enabling the NDI Output from the working system and setting it as a source on the new system and I can see the output of my test camera however when I go back to the view test camera on the new system I'm right back to that error message. This tells me that NDI seems to be mostly working on the new system as well but I can't find any logs that tell me there's a problem with the NDI source, including when I run OBS from the terminal and review the output.

In regards to the PC hardware the motherboards are identical, both are recent AMD chipsets. The only difference I can deduce between the working and not-working PCs is that I have an AMD video card in the working PC and an NVIDIA card in the not-working PC. Can anyone comment if the GPU drivers can produce a result such as this?

Any tips? Am I really the only one dealing with this?

More details: I've tried the following packages to look for changes:

- Replaced libndi-bin with libndi-git (broke NDI support entirely)
- Replaced libndi-git with ndi-sdk (restored NDI support but the message persists)
- Replaced ndi-sdk with ndi-advanced-sdk (same result, message persists)

I've verified that this is happening with NDI SDK 5.5.3 as well as NDI SDK 5.6.0.

Next up I'm going to see if borrowing the AMD video card helps here as I think decoding is handled by the GPU drivers.

I'm on a clean install and while everything installs fine I'm getting an error in OBS with a graphical message that says "NDI(R) Video decoder not found. Please visit ndi.tv/formats for help and information." Have we seen this already?