[Bug 657076] audioringbuffer: may fail to provide running clock

[GStreamer (GNOME Bugzilla)]

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

--- Comment #10 from Jan Schmidt <thaytan at noraisin.net> ---
The reason noone ever complained about glitches before is because they don't
happen with pulsesink where we map the pulseaudio ringbuffer directly and write
into it. They only happen with all the other audio sinks that rely on the
default ringbuffer.

With pulseaudio, it'll start the ringbuffer, write 1 segment and then
pulseaudio will start playing that segment. As long as the next segment is
written within 10ms, there'll be no glitch - unlike the default ringbuffer
where for the first $ringbuffersize milliseconds, segments will be read as
quickly as the audio device accepts them.

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