JACK clients ignore `node.lock-quantum = true` and PIPEWIRE_QUANTUM environment variable if pavucontrol started before JACK client
In ~/.config/pipewire/jack.conf I have:
jack.properties = {
node.latency = 128/44100
node.lock-quantum = true
}
On startup, my application calls jack_get_buffer_size
, which returns 128, to allocate the initial buffers. However, before processing starts, sometimes the buffer size callback gets called with a buffer size of 1024 frames. This sometimes also happens when starting with the environment variable PIPEWIRE_QUANTUM=128/44100
set. When this occurs, it occurs repeatedly. Sometimes changing a setting in Pipewire like the audio interface's profile in pavucontrol makes it go away or come back. I haven't figured out how to reliably reproduce this.
Using Pipewire 0.3.49-1 on Fedora 35 x86_64
Edited by Be