Pipewire seems to be stack at periods/buffer of 2 and setting it to 3 through ["api.alsa.period-num"] = 3, in wireplumber config doesn't seem to be effective. But I'm not sure if it's the right place to set it or even if it's possible. There is very little on that in pipewire/wireplumber wiki.
USB audio interfaces work best if '(Frames/Sample Rate) * Period' is a number dividable by 2. Standard buffer sizes like 64, 128, 256, 512 don't really do the trick.
Could non standard values be added to Pipecontrol? Working examples are: 48, 96, 144, 192, 240, 288, 336, 384, 432, 480, 528, 576, 624, 672, 720, 768, 816, 864, 912, 960, 1008, 1056, 1104, 1152, 1200, 1248, 1296, 1344, 1392, 1440, 1488, 1536, 1584, 1632, 1680, 1728, 1776, 1824, 1872, 1920...
Using these numbers has huge positive impact on xruns if USB device is used.
Hi,
Pipewire seems to be stack at periods/buffer of 2 and setting it to 3 through ["api.alsa.period-num"] = 3, in wireplumber config doesn't seem to be effective. But I'm not sure if it's the right place to set it or even if it's possible. There is very little on that in pipewire/wireplumber wiki. USB audio interfaces work best if '(Frames/Sample Rate) * Period' is a number dividable by 2. Standard buffer sizes like 64, 128, 256, 512 don't really do the trick.
Could non standard values be added to Pipecontrol? Working examples are: 48, 96, 144, 192, 240, 288, 336, 384, 432, 480, 528, 576, 624, 672, 720, 768, 816, 864, 912, 960, 1008, 1056, 1104, 1152, 1200, 1248, 1296, 1344, 1392, 1440, 1488, 1536, 1584, 1632, 1680, 1728, 1776, 1824, 1872, 1920...
Using these numbers has huge positive impact on xruns if USB device is used.