Quantcast
Channel: LinuxMusicians
Viewing all articles
Browse latest Browse all 2391

System Tuning and Configuration • What's the purpose of PipeWire's dynamic quantum setting?

$
0
0

I see that PipeWire can change the buffer size for applications dynamically, and you can set the minimum and maximum as well as the default quantum as mentioned here.

My question is, when does this dynamic change actually happen? My understanding is that when the default quantum is set and a JACK application is started, the application uses that buffer size as long as it is running. So, does PipeWire change the buffer size only for non-JACK applications?

This thread is what prompted me to ask this question. (I thought it would be better to start a separate thread.) In that thread, I noticed that default.clock.quantum was used in ~/.config/pipewire/pipewire.conf.d, while in my own configuration, I've been using node.latency = 1024/48000 and node.lock-quantum = true in ~/.config/pipewire/jack.conf.d. So, I'm wondering if there's any benefit for me to use the setting default.clock.quantum instead, and to also set default.clock.min-quantum and default.clock.max-quantum.

Statistics: Posted by mcord — Mon Jan 01, 2024 8:59 am



Viewing all articles
Browse latest Browse all 2391

Trending Articles