Dear Maintainer,

Starting with pipewire 1.6.3-1, external plugins fail to load. There are no
relevant errors or warnings in journalctl, nor in the pipewire or wireplumber
logs when started with PIPEWIRE_DEBUG=D and WIREPLUMBER_DEBUG=D.

After downgrading pipewire to 1.6.2-1 and rebooting (simply restarting the
pipewire/wireplumber services is not sufficient), the issue disappears and the
plugin loads correctly.

The affected plugin is DeepFilterNet:
https://github.com/Rikorose/DeepFilterNet

Please let me know if you need any additional information, logs, or testing.

Previously, I had the plugin installed in:

/home/myuser/.ladspa/

With pipewire 1.6.3 the plugin was not loaded, but after moving it to:

/usr/lib/ladspa/

it works correctly again.

Would it make sense to include a user plugin directory (e.g. ~/.ladspa or
~/.local/lib/ladspa) in the search path?

Please let me know if further information or testing would be helpful.

Hi,
I have just uploaded pipewire 1.6.4-1 to deb/unstable, this version
fixes an issue relating to the loading of LADSPA plugins.
Once it’s available, could you try it out to see if it solves your problem?

Best regards,
Dylan

Hi Dylan,
problem?

I've tested pipewire 1.6.4-1, and the issue still persists.

I also reviewed the 1.6.4 changelog, and it seems that the fixes related to
LADSPA plugin loading do not address this specific problem.

As mentioned earlier, the behavior still appears tied to the restriction
introduced in 1.6.3 regarding loading plugins from absolute paths outside
the search path. Plugins located in a user directory (e.g. ~/.ladspa) are
still not picked up, while moving them to /usr/lib/ladspa/ works as
expected.

Since this behavior is intentional, it shouldn't be considered a bug. That
said, if you think it would make sense to allow this use case by including
a user plugin directory (e.g. ~/.ladspa or ~/.local/lib/ladspa) in the
search path, I'd be happy to test it. However, I would stick with the
upstream behavior, I shouldn't have opened this report in the first place,
and it should be closed as wontfix/invalid.

Thanks and best regards.