mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-10-14 20:02:38 +00:00
9c4aab7508
Use separate timers for driving graph and for flushing, since they don't have the same period. Flushing is done based on the time positions of the next sample to be written, so it will stay in sync with the graph. Because writing too much data to SCO sockets generally only causes the device to skip ahead, we don't need to handle the case where the writing has been lagging. This fixes simultaneous playback to both ALSA and SCO sinks from the same graph, with SCO as driver, which previously produces broken sound (e.g. with pw-play --latency 512, linked to the two sinks) ALSA nodes require regular driver intervals, which was not true previously. |
||
---|---|---|
.. | ||
examples | ||
include | ||
plugins | ||
tests | ||
tools | ||
meson.build |