Page 2 of 3

Re: Burst in sound AvLinux MXe23.2

Posted: Sun May 05, 2024 10:46 am
by CharlesV
What problem does it create?

Re: Burst in sound AvLinux MXe23.2

Posted: Sun May 05, 2024 11:55 am
by SjzstudioMK
So that modprobe.d /usc.conf doesn't work. I should obviously do that lower, kernel option setting. But how to do it?

Re: Burst in sound AvLinux MXe23.2

Posted: Sun May 05, 2024 10:32 pm
by AVLinux
SjzstudioMK wrote: Sat May 04, 2024 8:51 am 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.
When you updated PipeWire it should have asked you to keep an existing configuration file, if you said to replace it then it would overwrite the one in AVL-MXe which was already set for you..

/etc/security/limits.d/25-pw-rlimits.conf should look like this to stop that error:

Code: Select all

# Default limits for users of pipewire
@pipewire - rtprio 95
@pipewire - nice -19
@pipewire - memlock unlimited
I'm afraid I have no experience with RME cards or insights, the fact that one crackles and the other doesn't points to the RME hardware, the performance figures you're getting with the Behringer are quite impressive..

Re: Burst in sound AvLinux MXe23.2

Posted: Mon May 06, 2024 2:02 am
by SjzstudioMK
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 unforseeable. But even if you set the UFX+ to USB 2 mode, that is a 2 to 30 channel difference.

Bottom line - the computer is the problem."

It would be nice to have this resolved. :happy:

Re: Burst in sound AvLinux MXe23.2

Posted: Mon May 06, 2024 5:55 am
by SjzstudioMK
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?

Re: Burst in sound AvLinux MXe23.2

Posted: Thu May 09, 2024 1:41 pm
by SjzstudioMK
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 wouldn't want to get into that

Re: Burst in sound AvLinux MXe23.2

Posted: Thu May 09, 2024 1:53 pm
by CharlesV
The latest pipewire (1.0.4) is out and supposedly has a REALLY large amount of bug fixes, plus some very good enhancements. You might want to read up on it here. and possibly request it in the requests area. (or go after it your self.)

https://linuxiac.com/pipewire-1-0-4-is- ... x-release/

Re: Burst in sound AvLinux MXe23.2

Posted: Thu May 09, 2024 2:32 pm
by Zeke
Pipewire 1.0.4 is already available in MX Pkg. Installer Test Repo. Just type in pipewire in the Search and you will see all the possible upgrades. Check-mark all that are up-gradable and don't forget qpwgraph, wireplumber.
Once the installation is complete, close, and reboot.

Re: Burst in sound AvLinux MXe23.2

Posted: Thu May 09, 2024 3:08 pm
by CharlesV
Thank you @Zeke I quickly looked and didnt see it!

Re: Burst in sound AvLinux MXe23.2

Posted: Thu May 09, 2024 3:23 pm
by SjzstudioMK
SjzstudioMK wrote: Sat May 04, 2024 8:51 am 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 Pipewire, the same noise can be heard from time to time. And also when I use the Ardour/Mixbus ALSA backend option. However, does Ardour/Mixbus connect directly to ALSA or is Pipewire still in between? Or is there some tool that can be used to monitor USB traffic if there is a problem there?