MX Linux Forum

Yes, I got it "usbcore.autosuspend=-1" at startup. But that didn't help with this problem either. In addition, I made a report on the Pipewire issue list, but there they suspect that the problem is with the drivers.

Next, I guess I should install Windows on the machine and AvLinux alongside it, so ...

I did those actions. I also updated Pipewire from the Test repo to the latest one.

I was using the Test Repo version at the time. If it's newer today, I can try that too.

Edit:
Could this be a problem on the ALSA side? Because if I listen to music on e.g. Spotify or some other player via ...

I still haven't found a solution to the problem. I installed Ubuntu studio alongside AvLinux. The glitch problem is smaller, but the DSP load is significantly higher. The same sessions have double the DSP load when I use Ubuntu studio. Do I need to install windows 10 here and see how it works. I ...

Have a nice summer!

linuxmusicians.com the forum has a tip:
In Debian/Ubuntu-like distributions it's editing /etc/default/grub, adding "usbcore.autosuspend=-1" to GRUB_CMDLINE_LINUX_DEFAULT and do a "sudo update-grub".

Can this be applied in this case without worry?

I already completely reinstalled AvLinux.

RME answer why Behringer works smoothly and RME doesn't:
"Come on, you know you can't compare the USB bus load of a 2 channel interface with a 94 channel one. And you are comparing USB 2 and USB 3, right? Which again will behave totally different and ...

So that modprobe.d /usc.conf doesn't work. I should obviously do that lower, kernel option setting. But how to do it?

This seems to work. But making that change permanent creates a problem. How to do it right?

I reinstalled the operating system. I updated Pipewire to the latest version and also the linux firmware.

I tested with another sound card. RME Firefice 802. The problem is similar. I also tested the Behringer U-Phoria UMC202HD, with which everything works fine, no glitches. So these are USB ...

I did those actions. I also updated Pipewire from the Test repo to the latest one. The situation improved a little. But now, when starting up, Mixbus gives a warning as shown in the picture.