pallaswept
commented
1 year ago I altered the path in the config to _/home/leaderofthe00fkins/linux-rnnoise/ladspa/librnnoiseladspa.so
This is not the correct procedure. Refer to the documentation at https://docs.pipewire.org/page_module_filter_chain.html, note that you should not specify the .so extension of the file, as it is automatically appended. Also, you should place the .so file in your existing LADSPA plugin path. To quote the relevant portion of the doc:
plugin is the type specific plugin name.
For LADSPA plugins it will append .so to find the shared object with that name in the LADSPA plugin path.The correct LADSPA plugin path will vary depending on your distro, by default on linux it will be /usr/local/lib/ladspa or /usr/lib/ladspa or /usr/local/lib64/ladspa or /usr/lib64/ladspa... you can get a strong hint if you have installed any by using your package manager, by running listplugins, as it will list all installed plugins and the paths to their files. You could set the path manually by altering your pipewire systemd unit file and setting the environment variable LADSPA_PATH but that would be a pretty intrusive way to go about it. Better to just put the plugin in the right spot.
Perhaps if you could include the conf file you have created it would help to find whatever other errors might be preventing it from working. The path you have specified ( ~/.config/pipewire/pipewire.conf.d/99-input-denoising.conf) should be functional, so something in that file is wrong. At the very least, it's that you've added that ".so" to the plugin path and the file is not in the correct location.
Also, these errors you're seeing are not normal:
Jul 19 20:41:57 pejassupercomputer pipewire[21995]: mod.protocol-native: server 0x55ba80c129f0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
Jul 19 20:41:57 pejassupercomputer pipewire[21995]: pw.conf: 0x55ba80bf7130: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable
Jul 19 20:41:57 pejassupercomputer pipewire[21995]: default: failed to create context: Resource temporarily unavailableIt seems like you've tried to start pipewire while it's already running. It may be a result of your attempts to load the config file manually (with pipewire -c)which you should do as an alternative to, not in addition to, placing the config file as you have and creating a split-file configuration which should already have loaded the conf file with pipewire's daemon.
The same command returned this after manually running pipewire with -c and the config path.
24068 ? S<sl 0:00 /usr/bin/pipewire 26562 ? Sl 0:00 xed /home/leaderofthe00fkins/.config/pipewire/pipewire.conf.d/99-input-denoising.conf 27052 pts/0 S+ 0:00 grep --color=auto pipewire
This just shows that pipewire is running (as before) and also you're presently editing the config file in xed. You can use the command pw-config to ensure that your split-file configuration is effective and the conf file has been loaded with pipewire, and pw-dump to dump the current status of the entire daemon, which should include the modules and nodes you've created with the conf file. pw-dump | grep rnnnoise will give you a quick check if you don't want to read the entire dump.
Hope this helps.
Danie10
I am using Linux Mint 21.2, Kernel version is 5.19.0-46-generic, Desktop Environment is Cinnamon. I will try to provide more info upon request.
Going to describe what I did to install it in case I was being dumb and misunderstood the instructions, causing the issue. I downloaded the .zip, extracted the folder to my Home folder, created /home/leaderofthe00fkins/.config/pipewire/pipewire.conf.d/99-input-denoising.conf and pasted the configuration. I altered the path in the config to _/home/leaderofthe00fkins/linux-rnnoise/ladspa/librnnoiseladspa.so and left the VAD settings as default. I continued with "systemctl restart --user pipewire.service" as instructed. From the text in the guide it seems like, essentially, a new audio input device should have been created with the name "Noise Canceling source".
My issue is that no Input device was created after following the instructions. There was no output in the terminal when using the pipewire restart command. I tried looking at certain things I had seen other users check, like using the command "journalctl -b | grep pipewire" and trying to run the config directly with "pipewire -c ~/.config/pipewire/pipewire.conf.d/99-input-denoising.conf". The outputs of these are the following:
Another command I saw, which was to check the running instances of pipewire I think, "ps ax | grep pipewire". This command returned the following before the config execution.
The same command returned this after manually running pipewire with -c and the config path.
As far as I can tell they are at least running, just not doing what is supposed to be done. Not sure what else to say, I don't really know where to go from here.