MX Linux Forum

You should be a member of the Pipewire group and set /etc/security/limits.d/25-pw-rlimits.conf like this: # This file was installed by PipeWire project for its libpipewire-module-rt.so # It's believed to be acceptable to have match rules that will never be true # i.e. a group that does not exist ...

Hi, I made some PipeWire tools here: https://forum.mxlinux.org/viewtopic.php?p=797593#p797593 The PipeWire tools have a simple GUI to set metadata (per session) I see so manual session management is to be expected for this currently. It's shocking Reaper can do whatever it likes though Justin does ...

So you are thinking when I set realtime user priviledges following a guide that suggested I create an audio.conf in the limits.d folder, and add myself to the 'audio' group, that it likely put my root user outside of the pipewire defaults?

I've been running Reaper on an updated regular install of MX using Liquorix, and while I've ran Reaper through it's ALSA dialog with no issue whatsoever (even though I soon added RT privledges and addressed memlock limits), Renoise has been a different story because it tries to run alsa through ...