MXLinux Pipewire Defaults seem to set both Rate and Buffer to '0'

[Ace of Bass]

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 pipewire, and it seems MX defaults rate and buffer to '0' for pipewire.

I only say this because

Code: Select all

pw-metadata -n settings 0 clock.force-rate 48000 && pw-metadata -n settings 0 clock.force-quantum 128

at least allows renoise to seem to play properly for the session as long as I match this rate and buffer in its preferences too, but I'm left to wonder how to properly make this change persist, and ideally I should be able to change rate and buffer within the Renoise app and have pipewire respect that change in real-time.

It seems currently that the MX defaults are ignoring the defaults within the various pipewire conf files which ask for a rate of '48000' and a buffer (quantum) of '1024', It seems from pw-top that the defaults are forcing both rate and quantum to '0'.

My only guess is that in the usr/share/pipwire/minimal.conf it initializes some hw devices and forces them to '0' somehow but I'm a bit lost on what to do.

Obviously using that command in a terminal every session is a bit taxing.

Any solutions?

[CharlesV]

Welcome in!

Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )

You *might* be able to set the settings you want, then go into MX User Manager and under Group membership - choose your user and then *uncheck* audio.

This has worked with some other 'resetting issues" in sound... Full caveat, I have been told this will / can cause issues in some other sound adjustments when you get heavily into it. However, I have been running this way for 6 months with no issues that I can see. (I record and edit both sound and video )

[AVLinux]

Hi,

I made some PipeWire tools here: viewtopic.php?p=797593#p797593

The PipeWire tools have a simple GUI to set metadata (per session)

[Ace of Bass]

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?

[AVLinux]

You should be a member of the Pipewire group and set /etc/security/limits.d/25-pw-rlimits.conf like this:

Code: Select all

# 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.
#
@pipewire   - rtprio  95
@pipewire   - nice    -19
@pipewire   - memlock unlimited

[Ace of Bass]

Hi,

I made some PipeWire tools here: 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 have a ridiculous amount of magic tricks going on with that DAW.

[AVLinux]

Hi,

I made some PipeWire tools here: 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 have a ridiculous amount of magic tricks going on with that DAW.

Well in AV Linux (based on MX) my expectation was that the User would only use that to change from the running session defaults (ie change from 48Khz to 44.1Khz) and if they wanted permanent new defaults they would edit the PipeWire systemwide conf files.

Another newer option is 'Cable': https://github.com/magillos/Cable/tree/0.9.0 there is a Deb in it's releases page.

Metadata settings plus Patchbay in one app

[Ace of Bass]

You should be a member of the Pipewire group and set /etc/security/limits.d/25-pw-rlimits.conf like this:

Code: Select all

# 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.
#
@pipewire   - rtprio  95
@pipewire   - nice    -19
@pipewire   - memlock unlimited

I'll give this a try and then see if my pipewire.conf changes are respected. Think I should edit the pipewire.conf in usr/share/pipewire directly as root or should I try to duplicate it in my home in .config/pipewire and edit it? Does that path work currently?

Thank you for taking the time to advise.

[AVLinux]

Hi,

I have not personally ever had need to change the defaults (I avoid PW like the plague for production work) but I would suggest copying to ~/.config/pipewire

Also be aware that the MX Test tab in MX Package Installer has a much newer PipeWire version than the regular MX Repo