mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-31 22:25:38 -04:00
15908328d1
When freewheeling we will immediately schedule a new graph cycle when we get a process call because the graph completed. When the process call is not done, because of some xrun or because some node was removed that causes the graph to fail completion, The next cycle will happen after a timeout. This timeout was calculated as the ideal wakeup time (after a quantum of time) and would accumulate for each timeout. The result is that the timeout ended up far in the future and would stall the freewheel driver for a long time. Fix this by always setting the next timeout to wakeup time + freewheel.timeout seconds. Also add a config property for the timeout (10 seconds, like jack2 by default). |
||
|---|---|---|
| .. | ||
| cpu-arm.c | ||
| cpu-x86.c | ||
| cpu.c | ||
| dbus.c | ||
| evl-plugin.c | ||
| evl-system.c | ||
| journal.c | ||
| logger.c | ||
| loop.c | ||
| meson.build | ||
| node-driver.c | ||
| null-audio-sink.c | ||
| plugin.c | ||
| system.c | ||