Setting PIPEWIRE_LATENCY lower than 1024 no longer works with Qemu Jack driver [regression]
- PipeWire version (
pipewire --version
): >=0.3.71 (including master) - Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
): Gentoo Linux - Desktop Environment: Sway
- Kernel version (
uname -r
): 6.3.2-extra2+
Description of Problem:
Setting a client specific quantum lower than 1024 with Qemu's Jack driver results in no sound and setting >=1024 results in crackling sound (tested up to 4096). With 0.3.70 or earlier I could use a 512 quantum with glitch-free audio.
How Reproducible:
100% of the time when using Qemu 7.2.0 + libvirt 9.3.0 + Qemu jack driver with Windows and Linux guests.
Steps to Reproduce:
- Launch a VM configured to use Qemu's jack driver (https://looking-glass.io/wiki/Using_JACK_and_PipeWire)
- Test audio in guest (e.g. run speaker test etc)
Actual Results:
No audio with PIPEWIRE_LATENCY=512/48000
or lower. Crackling audio with PIPEWIRE_LATENCY=1024
or higher and when not configuring PIPEWIRE_LATENCY.
Expected Results:
Mostly glitch free audio with PIPEWIRE_LATENCY=512
or higher.
Workaround:
Set global quantum with pw-metadata -n settings 0 clock.force-quantum 512
. Must be set before VM is launched. Or revert to pipewire-0.3.70 or earlier.
Additional Info (as attachments):
-
pw-dump > pw-dump.log
: pw_dump.log