[Bug 644945] Gstreamer audio synchronization fails at low latency.
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Mon Apr 4 14:54:23 PDT 2011
https://bugzilla.gnome.org/show_bug.cgi?id=644945
GStreamer | gst-plugins-base | 0.10.32
Håvard Graff (hgr) <havard.graff> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |havard.graff at tandberg.com
--- Comment #1 from Håvard Graff (hgr) <havard.graff at tandberg.com> 2011-04-04 21:54:16 UTC ---
Generally it is a very bad idea to have the device wait for anything at all. I
have seen BSOD on Windows and complete sound-system failure on OSX as a result
of doing this. So don´t :)
Another tip is to not interpret, but rather log out all read/write access so
that you are able to simulate the failing scenario. My guess is that you are
being a bit unfair with that pipeline. Remember that your pipeline latency
effectively will end up as headroom in your ringbuffer. If there is no, or only
very little headroom, you *will* get under-runs (glitches / silence), this is
the case for all ringbuffers. If you simply were to increase the latency of the
pipeline with a bit more, you would effectively increase the headroom in the
ringbuffer, making underruns more unlikely.
I would also be interested to know if this patch will help a bit: Given that
your buffers is 10ms, and the resync threshold is default 20ms, it could very
well be that you end up in that "grey" zone that this patch addresses:
http://cgit.freedesktop.org/gstreamer/gst-plugins-base/commit/?id=588ac0ae6fdfb55c612cc84f5426cbf1ee4aec4e
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list