Page 1 of 1
Burst in sound AvLinux MXe23.2
Posted: Wed May 01, 2024 12:54 pm
by SjzstudioMK
My new machine with an AMD Ryzen 7900X and TUF GAMING B650-PLUS configuration has nasty symptoms. The sound card is RME UFX+. It appears with Mixbus 10 Pro DAW and Ardour and Reaper, fairly reasonable buffer size of 512 and below. What could be wrong here.
DSP is not high.
The machine runs cool. I am confused. Or is this configuration too new for Linux? So do I have to wait for the drivers etc. to be updated?
Bios has power savings off, as well as multi threading off. No overclocking enabled.
This is using ALSA.
If I change the PipeWire, the situation is better, but there is a quiet crackle in the sound every now and then.
Below is a link where you can hear what is happening.
https://e.pcloud.link/publink/show?code ... 9lfybHauX7
EDIT:
Someone has had similar problems with the MOTU inteface. With Manjaro Linux. I don't know if the root cause could be the same
https://linuxmusicians.com/viewtopic.php?t=26865
Re: Burst in sound AvLinux MXe23.2
Posted: Thu May 02, 2024 11:26 am
by CharlesV
Please post your QSI. ( MX Menu, Quick System Info, Copy for Forum, Paste here )
Re: Burst in sound AvLinux MXe23.2
Posted: Thu May 02, 2024 12:34 pm
by SjzstudioMK
Code: Select all
Snapshot created on: 20240218_1856
System:
Kernel: 6.8.7-2-liquorix-amd64 [6.8-8~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.8.7-2-liquorix-amd64
root=UUID=<filter> ro threadirqs quiet init=/lib/systemd/systemd
Desktop: Enlightenment v: 0.25.4 vt: 7 dm: LightDM v: 1.26.0 Distro: AVL_MXE-23.1-20240115_x64
Enlightened January 15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING B650-PLUS v: Rev 1.xx serial: <superuser required>
UEFI: American Megatrends v: 2413 date: 02/04/2024
CPU:
Info: model: AMD Ryzen 9 7900X bits: 64 type: MCP arch: Zen 4 gen: 5 level: v4 note: check
built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
microcode: 0xA601206
Topology: cpus: 1x cores: 12 smt: <unsupported> cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32
KiB L2: 12 MiB desc: 12x1024 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 400 min/max: 400/5733 scaling: driver: amd-pstate-epp governor: performance
cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
bogomips: 112584
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional; STIBP: disabled;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
active: HDMI-A-1 empty: DP-1,Writeback-1 bus-ID: 0c:00.0 chip-ID: 1002:164e class-ID: 0300
temp: 28.0 C
Display: x11 server: X.Org v: 1.21.1.7 compositor: enlightenment driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22") s-diag: 582mm (22.9")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: AOC Q3279WG5B serial: <filter> built: 2017
res: 1920x1080 hz: 60 dpi: 67 gamma: 1.2 size: 725x428mm (28.54x16.85") diag: 842mm (33.1")
ratio: 15:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (raphael_mendocino LLVM
15.0.6 DRM 3.57 6.8.7-2-liquorix-amd64) direct-render: Yes
Audio:
Device-1: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 1-2:2 pcie: chip-ID: 2a39:3fd1 class-ID: 0103 gen: 4 serial: <filter>
speed: 16 GT/s lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0c:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-3: RME Fireface UFX+ type: USB driver: snd-usb-audio
API: ALSA v: k6.8.7-2-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 3.47 TiB used: 138.49 GiB (3.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Kingston model: SNV2S1000G size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
rev: SBM02103 temp: 16.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 2B2QEXM7 temp: 21.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 1TB size: 931.51 GiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: MBR
ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q
scheme: MBR
ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD3200AAKS-75L9A0 size: 298.09 GiB
block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: <filter> rev: 3E01
scheme: MBR
Partition:
ID-1: / raw-size: 493.57 GiB size: 484.75 GiB (98.21%) used: 28.6 GiB (5.9%) fs: ext4
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 437.69 GiB size: 429.75 GiB (98.19%) used: 12.94 GiB (3.0%) fs: ext4
dev: /dev/sda3 maj-min: 8:3
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 32.6 C mobo: N/A gpu: amdgpu temp: 29.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2511 pm: dpkg pkgs: 2505 libs: 1468 tools: apt,apt-get,aptitude,synaptic pm: rpm
pkgs: 0 pm: flatpak pkgs: 6
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/helineva-net.list
1: deb http://helineva.net/deb xenial main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://mirror.one.com/mx-packages/mx/repo/ bookworm main non-free
2: deb https://mirror.one.com/mx-packages/mx/repo/ bookworm ahs
Info:
Processes: 418 Uptime: 1m wakeups: 0 Memory: 62.03 GiB used: 2 GiB (3.2%) Init: systemd v: 252
target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Burst in sound AvLinux MXe23.2
Posted: Thu May 02, 2024 1:38 pm
by CharlesV
Yes, you might try getting the very latest linux-firmware.
https://git.kernel.org/pub/scm/linux/ke ... mware.git/
If you need / want instructions on doing it. You can :
1)
Save a copy of your current /lib/firmware/ just in case..
and then
2)
Code: Select all
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20240410.tar.gz ; tar -xf linux-firmware-20240410.tar.gz ; cd linux-firmware-20240410.tar.gz ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all
Re: Burst in sound AvLinux MXe23.2
Posted: Thu May 02, 2024 2:14 pm
by SjzstudioMK
I tried updating the firmware for this old home computer. Seemed work. Probably, the update can also be done on the studio machine, so I'll do the same on the studio machine tomorrow.
Asus has also released a new Bios update. Is it of any use?
Re: Burst in sound AvLinux MXe23.2
Posted: Thu May 02, 2024 2:26 pm
by CharlesV
IDK about that. This post seems to have some people saying it has helped them with various issues (none are sound), but then some saying that they are now BSOD . so.. mixed bag
https://www.reddit.com/r/ASUS/comments/ ... os_thread/
And I dont see any release notes other than the ones on the link you provided - which says about zip
"Update AGESA version to Combo 1.1.7.0 patch A to support next generation AMD Ryzen™ processors"
Re: Burst in sound AvLinux MXe23.2
Posted: Sat May 04, 2024 8:51 am
by SjzstudioMK
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.
Re: Burst in sound AvLinux MXe23.2
Posted: Sat May 04, 2024 2:40 pm
by SjzstudioMK
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 devices. UFX+ is a USB3 device that works in Class compliant mode as a USB2 device. 802 when connecting USB3 the situation became worse and noises start to be heard. Behringer U-Phoria UMC202HD when connecting to the USB3 port there is no noises.
In conclusion, I wonder why with RME sound cards this problem occurs? And why there are no problems with Behringer. It remains stable even with settings of 64 samples, even in this session with over 30 tracks. Probably the PC is fine. But can something be done about it on the Linux side?
Re: Burst in sound AvLinux MXe23.2
Posted: Sat May 04, 2024 5:01 pm
by CharlesV
Re: Burst in sound AvLinux MXe23.2
Posted: Sun May 05, 2024 4:43 am
by SjzstudioMK
This seems to work. But making that change permanent creates a problem. How to do it right?
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.
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?
Re: Burst in sound AvLinux MXe23.2
Posted: Fri May 10, 2024 11:35 am
by AVLinux
Did you try the Kernel boot code above? You don't have to directly edit /etc/default/grub you can also use MX Tools-->Boot Options to add the code to your existing Boot line.. If you get it wrong the worst that would likely happen is the console telling you about an unrecognized Boot code..
Re: Burst in sound AvLinux MXe23.2
Posted: Fri May 10, 2024 12:28 pm
by SjzstudioMK
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 can see if everything works with RME's Windows drivers.