[gstreamer-bugs] [Bug 640859] basesink default drift-tolerance causes glitches on some clips

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Mon Jan 31 15:39:09 PST 2011


https://bugzilla.gnome.org/show_bug.cgi?id=640859
  GStreamer | gst-plugins-base | git

--- Comment #25 from Edward Hervey <bilboed at gmail.com> 2011-01-31 23:39:04 UTC ---
(In reply to comment #24)
> And here's another argument. Pick any mp3 file, convert it with GStreamer to
> matroska vorbis or flac, and try this:
> 
> gst-launch-0.10 filesrc location=test.mka ! matroskademux ! flacdec ! pulsesink
> drift-tolerance=100
> 
> You would hear glitches all the time, because basesink would do
> resynchronization every buffer and apparently GStreamer timestamps have a
> jitter of around 100us, while FFmpeg has 10ms.
> 

  Congratulations, you've just proven that the default 40ms is a better choice
than 100microseconds. I applause your logic. Wait, you had a point ?

  The moment you'll understand that drift-tolerance is called as such because
it's the threshold at which we consider timestamp inconsistencies as *drift*
and not as *jitter* you might be able to [censored] the [PG rated]. Both
Olivier and Mark have proven their understanding of this problem in their
comments, but you insist in childing around.

P.S. Now please, as a courtesy to those actually trying to figure out an
acceptable way to counteract this minor odd issue, just stop spamming these bug
reports repeating yourself 500 times in as many different ways of you disliking
how GStreamer works despite the fact that it handles A/V sync for 99.99999999%
of the files/use-cases out there in a much better way than any of the tools
you've mentioned. WE GOT THE POINT, WE UNDERSTAND THE ISSUE AT HAND ! It just
doesn't help, makes up grumpy, and makes us not want to help you. Unlike kids,
we prefer to ponder the issue at hand to try to find an *acceptable* fix which
won't introduce regressions (and yes, we're thinking about it, the answer isn't
in screwing up audio sync for everyone else but rather in detecting the busted
files at the demuxer level). Would you (or your employer) prefer a rapid fix
that fixes this marginal braindead file playback while screwing up all the
other use-cases ? Good night (or morning).

-- 
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