ALSA period size doesn't match JACK buffer size with Pro Audio profile
Tried on e4def0ce. When selecting the Pro Audio profile for the sound card (an internal Intel HDA), and running a JACK client like Ardour with PIPEWIRE_LATENCY=256/48000
, the ALSA params are configured as follow:
$ cat /proc/asound/card*/*/*/hw_params
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 1024
buffer_size: 32768
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 1024
buffer_size: 32768
closed
closed
closed
According to the FAQ and as discussed in IRC with @wtaymans, since 0.3.81, when the device profile is set to pro audio, the ALSA period size should match the JACK buffer size (in this case 256).
I've also tried to force the quantum with:
pw-metadata -n settings 0 clock.force-quantum 256
But this didn't change the resulting ALSA params (tried this with the devices in closed state, so I've started the JACK client after setting the metadata option).
If I use wireplumber to set api.alsa.period-size
to 256
, and restart wireplumber and pipewire, the period size is configured correctly, but the ALSA buffer size is still pretty high:
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 256
buffer_size: 8192
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 256
buffer_size: 8192
closed
closed
closed
pw-dump.json (the dump is taken without any forced setting, so default wireplumber config and no particular metadata option set by CLI)