[Bug 765115] alsasink: single segment audio glitch after 200ms at startup

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=765115

--- Comment #2 from Jan Schmidt <thaytan at noraisin.net> ---
(In reply to Nicolas Dufresne (stormer) from comment #1)
> We also discussed that with Wim. I believe this should be configurable. We
> are missing a third size, we have latency-time, which is the size of
> write(), buffer-time, which is both the size of the ring buffer and the
> latency. But I think the latency/start-threshold should be in-between the
> size of a write() and the ring buffer size, and that should be configurable.

That's only possible with pulsesink that maps the output ringbuffer and writes
into it directly. With almost all the other audio sinks that write the first
batch of data as rapidly as possibly, the ringbuffer start threshold *has* to
be the full size or it can glitch.

pulsesink has a custom commit function, so it can arrange any start threshold
it wants. In any case, I think that enhancement is orthogonal to this bug.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.