You are not logged in.
I'm having an issue that's probably best described by what this user posted previously on this forum already (https://bbs.archlinux.org/viewtopic.php?id=265747):
"sound stuttering in the form of short gaps of silence that sound like they are surrounded by fade-out and back in. It sounds as if someone rapidly (but not instantly) turned the volume down to 0 and then slightly less rapidly (over about 300ms) turned it back up to the original level."
A bit more context to my situation and the debugging I've already done
- It only happens on a single device I'm using, the FiiO ka11
- It doesn't happen with any other audio device I've tried (Other USB-C dongles, plugging headphones directly in the 3.5mm output of my laptop, Bluetooth headphones)
- I've tried reproducing this issue with another distro on this laptop (Fedora 41) and the same thing happens there
- I've tried various combinations of settings for PipeWire including Sample Rate, Audio Format, ALSA period size, session.suspend-timeout-seconds = 0)
- It occurs roughly every minute (+/- 5 seconds)
- Also occurs when using aplay directly and bypassing PipeWire
- Nothing suspicious in any logs when the cutout occurs
- Issue doesn't happen when using this DAC on any other devices (Android phone, desktop computer)
I hope anyone can point me in the right direction on how to debug this.
Offline
I just got a KA11 too and have the same issue. Music cuts out every 61s then fades back in. I only have that issue on my Framework 13 (12th gen Intel), but not on my desktop (Ryzen 5000).
A curious thing I noticed: If I unplug the KA11 while music is playing (PW switching the stream back to the fallback, onboard output) and replug it (and switch the stream back via pavucontrol), the 1 minute interval does not reset, which makes it basically certain that it's a bug in Pipewire. I could imagine that the same happens for other audio outputs as well but the KA11 is the only one that does the fading in effect (which is honestly nice since it prevents crackling) and thus makes it noticable.
A list of differences between both systems that I wrote before discovering the above (Laptop not working - Desktop working):
- Kernel: 6.12.29-1-lts - 6.12.25-2-lts
- Pipewire/Wireplumber: 1:1.4.2-1 / 0.5.10-1 - 1:1.4.2-1 / 0.5.8-1
- USB connection: USB-C - USB-A to C adapter + USB-C extension cord
- USB chip: Intel Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01)/Intel Alder Lake-P Thunderbolt 4 Controller (rev 02) - AMD Matisse USB 3.0 Host Controller
- Second USB DAC plugged in: No - Yes
- Pipewire setup: OOTB - A bunch of stuff configured, but nothing that should affect this
Offline