Wim Taymans da86026b7a latency: handle negative latency correctly ... In our current world, it is possible to have a negative delay. This means that the stream should be delayed to sync with other streams. The pulse-server sets negative delay and the Latency message can hold those negative values so make sure we handle them in the helper functions as well. Do the delay calculations in pw_stream and JACK with signed values to correctly handle negative values. Clamp JACK latency range to 0 because negative latency is not supported in JACK. We should also probably make sure we never end up with negative latency, mostly in ALSA when we set a Latency offset, but that is another detail.		2024-10-23 10:47:58 +02:00
..
daemon	pulse-server: add condition support in pulse.cmd	2024-10-23 09:08:50 +02:00
examples	remove deprecate Props settings, use node.param.Props	2024-10-08 10:27:36 +02:00
gst	gst: deviceprovider: fix memory leak in do_add_nodes	2024-10-22 21:53:57 +00:00
modules	pulse-server: add condition support in pulse.cmd	2024-10-23 09:08:50 +02:00
pipewire	latency: handle negative latency correctly	2024-10-23 10:47:58 +02:00
tests	pw-container: use smaller path for temporary file	2024-06-27 21:18:06 +00:00
tools	profiler: add followerClock block	2024-10-09 11:31:54 +02:00
meson.build	meson.build: fix compile with -Dexamples=disabled	2023-11-28 10:18:25 +00:00