Arch Linux

7643 readers

16 users here now

The beloved lightweight distro

founded 4 years ago

MODERATORS

[email protected]

Constant audio stuttering/cutting with Pipewire (iusearchlinux.fyi)

submitted 11 months ago* (last edited 11 months ago) by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

This isn't so much an Arch issue (For what it's worth, this also happened on Nobara) but rather a Pipewire issue but I wonder if anyone's had this issue as well as me...

Running Arch on linux-zen (to fulfill Waydroid's binder requirement), on a Ryzen 7950X, motherboard has a Realtek ALC4080, connected via USB (yes it's still an internal sound chip).

Basically, after any prolonged use, I would get a lot of stuttering. It got particularly bad when I was running MusicBrainz Picard while listening to something in VLC, but it will happen often, and constantly.

I've tried setting my default output to the headphones, no dice. Also tried some workarounds from the Arch Wiki, specifically disabling suspend. Still happens. Adding headroom errored out Wireplumber.

Anyone had this and if so, have they been able to fix it?

Edit: I'll probably have to check if it's a kernel thing. I've just done some intensive tasks (i.e. installing Gentoo in a virtual machine) and the cutoffs come back. I remember Arch having something on the Wiki about that.

top 5 comments

sorted by: hot top controversial new old

[–] Chais 4 points 11 months ago

Hey. I'm an unhappy owner of an ALC4080, too. I have issues with the microphone on mine. I don't recall output issues. But I vaguely remember having issues with the sample rate. 48k was iffy, no matter what but once I told pipewire to use 44.1k that resolved itself.

[–] [email protected] 1 points 11 months ago

Can't really help you but it might be worth it to bug it in pipewire gitlab.

[–] [email protected] 1 points 11 months ago (1 children)

if it also happen in nobara, isn't it a hardware issue?

[–] Chais 2 points 11 months ago (1 children)

If it happened on Windows it would be. Currently it's a driver issue.

[–] [email protected] 1 points 11 months ago

This. Could be a driver issue, could be Pipewire. It's not occurred on Windows at all, AFAIK.