In PipeWire it manifests from 512 (frames/period) upwards, at least in my configurations..
nope, here after doing pw-metadata -n settings 0 clock.force-quantum 512
and pw-metadata -n settings 0 clock.force-quantum 1024
nothing strange happens, that meaning business as usual.
however, pw-metadata -n settings 0 clock.force-quantum 2048
is a dang showstopper: can't get it to playback even at all, but that's probably due on my PW configuration having this property default.clock.max-quantum = 2048 so I wouldn't complain :)
check your pipewire.conf (and jack.conf) then, I'd suggest.
nope, here after doing
pw-metadata -n settings 0 clock.force-quantum 512and
pw-metadata -n settings 0 clock.force-quantum 1024nothing strange happens, that meaning business as usual.
however,
pw-metadata -n settings 0 clock.force-quantum 2048is a dang showstopper: can't get it to playback even at all, but that's probably due on my PW configuration having this property
default.clock.max-quantum = 2048so I wouldn't complain :)check your pipewire.conf (and jack.conf) then, I'd suggest.
byee