Various fixes to improve latency handling (see the patches). What's missing is: - No pre-emptive latency increase, like the ALSA module does with its watermark. Perhaps we need to have the same approach? Or is there some other value we can monitor? Right now it will have to glitch before it responds. - Once increased, the latency can never be reduced. Because every increase is after we've glitched, it's not really safe to start reducing the latency again.
Created attachment 117188 [details] [review] tunnel-sink-new: don't force latency limit
Created attachment 117189 [details] [review] tunnel-new: respect client latency requirements better
Created attachment 117190 [details] [review] tunnel-new: Increase latency on underflow/overflow
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/47.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.