Get /R/ running on MX Linux, Pipewire, ALSA, Real Time Thread?

Help, Support & Bugs Beginners Questions - Renoise
21

that is each core. it means that it works.

check with

cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor

if it shows performace for each core it’s fine

22

$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
performance

now reboot and check?

23

yes…
but you have to set the governor again to performance after booting

24

every time?
ah, its because it is not a persistent change?

25

Yes.

You can set it in grub according to this website:

Kernel Parameter hinzufügen (Beispiel: Grub)
GRUB_CMDLINE_LINUX_DEFAULT=“quiet cpufreq.default_governor=performance”

Not sure if this works on MX Linux. Be careful when editing GRUB, as incorrect configurations can prevent your PC from booting. You can also change the governor via a script that is started via autostart.

1 Like
26

is not working still stutter audio:

at first i do:

$ sudo cpupower frequency-set --governor performance

$ renoise

Renoise LOG> ============================================================
Renoise LOG> Version : Renoise V3.4.4 (May 7 2024)
Renoise LOG> Date : 2025-06-05
Renoise LOG> Time : 15:50:54
Renoise LOG> OS : Linux version 6.14.9-1-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.14-11~mx23ahs (2025-05-31)
Renoise LOG> ============================================================
Renoise LOG> System: Application path retrieved from /proc/self/exe: ‘/usr/local/bin/renoise-3.4.4’
Renoise LOG> System: Running from ‘/usr/local/bin’…
Renoise LOG> CPU: Found 1 enabled unit(s) with 14 core(s) and 20 logical processor(s) per unit. 14 cores, 20 logical processors are enabled in total.

…
Renoise LOG> MIDI-IO: Adding Output device ‘PipeWire-System: input’…
Renoise LOG> MIDI-IO: Adding Output device ‘PipeWire-RT-Event: input’…
Renoise LOG> ALSA: Successfully created an ALSA RT thread
Renoise LOG> ALSA: Up and running…

ALSA
48000Hz
512 ms

27

What does the rtqs script say?

28

rtcqs

Root User

[ OK ] Not running as root.

Group Limits

[ OK ] User mx is member of a group that has sufficient rtprio (95) and memlock (unlimited) limits set.

CPU Frequency Scaling

[ WARNING ] The scaling governor of one or more CPUs is not set to ‘performance’. You can set the scaling governor to ‘performance’ with ‘cpupower frequency-set -g performance’ or ‘cpufreq-set -r -g performance’ (Debian
/Ubuntu). See also System configuration [Linux-Sound]

Simultaneous Multithreading

[ WARNING ] Simultaneous Multithreading (SMT, also called hyper-threading) is enabled. This can cause spikes in DSP load at higher DSP loads. Consider disabling SMT when experiencing such spikes with ‘echo off | sudo te
e /sys/devices/system/cpu/smt/control’. See also System configuration [Linux-Sound]

Kernel Configuration

[ OK ] Valid kernel configuration found.

High Resolution Timers

[ OK ] High resolution timers are enabled.

Tickless Kernel

[ OK ] System is using a tickless kernel.

Preempt RT

[ WARNING ] Kernel 6.14.10-2-liquorix-amd64 without ‘threadirqs’ parameter or real-time capabilities found. See also System configuration [Linux-Sound]

Spectre/Meltdown Mitigations

[ WARNING ] Kernel with Spectre/Meltdown mitigations found. This could have a negative impact on the performance of your system. See also System configuration [Linux-Sound]
own_mitigations

RT Priorities

[ OK ] Realtime priorities can be set.

Swappiness

[ WARNING ] vm.swappiness is set to 15 which is too high. Set swappiness to a lower value by adding ‘vm.swappiness=10’ to /etc/sysctl.conf and run ‘sysctl --system’. See also wiki:system_conf [Linux-Sound]
iguration#sysctlconf

Filesystems

[ OK ] The following mounts can be used for audio purposes: /

IRQs

[ OK ] Soundcard snd_hda_intel:card1 with IRQ 17 does not share its IRQ.
[ OK ] Soundcard snd_hda_intel:card0 with IRQ 159 does not share its IRQ.
[ OK ] USB port xhci_hcd with IRQ 143 does not share its IRQ.

Power Management

[ WARNING ] Power management can’t be controlled from user space, the device node /dev/cpu_dma_latency can’t be accessed by your user. This prohibits DAWs like Ardour and Reaper to set CPU DMA latency which could help p
revent xruns. For enabling access see System configuration [Linux-Sound]

Back in Renoise:
now, i set buffer to 7 and setup in and out Devices to DEFAULT, now it seems running, lets see how long it goes.
Any ideas are highly appreciated.

29

I guess this could be your problem still.