> For each component (subgraph of the whole PipeWire graph), one node is the driver and is responsible for timing information.
A new thing I learned I guess. JACK treats both the output ports and input ports of the single hw device as a driver, and if the output ports (capture) generates more samples than the input ports (playback) accept, you eventually get buffer xruns.
> Note: in this simple example, the buffer size provided to ALSA by PipeWire determines the time we have to generate new data.
I thought PipeWire uses quantums, effectively ignoring ALSA periods and "racing the beam" using software timers instead.
A new thing I learned I guess. JACK treats both the output ports and input ports of the single hw device as a driver, and if the output ports (capture) generates more samples than the input ports (playback) accept, you eventually get buffer xruns.
> Note: in this simple example, the buffer size provided to ALSA by PipeWire determines the time we have to generate new data.
I thought PipeWire uses quantums, effectively ignoring ALSA periods and "racing the beam" using software timers instead.