PW_KEY_NODE_LATENCY ignored for input stream process callback?
I have a device node with a quantum of 128 bytes.
If I connect a SPA_AUDIO_FORMAT_F32_LE
(4 bytes) stereo (2 channels) stream to said device and the direction is
-
PW_DIRECTION_OUTPUT
: I have to feed (at least) 1024 bytes each call in order to avoid xruns. -
PW_DIRECTION_INPUT
: The buffer in the callback always provides 1024 bytes.
If I set the PW_KEY_NODE_LATENCY
property to 480/48000
(10 ms latency) when connecting the stream and the direction is
-
PW_DIRECTION_OUTPUT
: I have to feed (at least) 3840 bytes each call in order to avoid xruns. -
PW_DIRECTION_INPUT
: The buffer in the callback always provides 1024 bytes. I would, instead, expect the buffer to always provide 3840 bytes.
Is this the expected behavior? If yes, is there a way to tell PipeWire how many bytes to provide for each call?