[gstreamer-bugs] [Bug 576381] [basesink] QoS: emergency rendering not always done
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Mon Mar 23 05:59:28 PDT 2009
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=576381
GStreamer | gstreamer (core) | Ver: git
Tim-Philipp Müller changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
Target Milestone|HEAD |0.10.23
------- Comment #4 from Tim-Philipp Müller 2009-03-23 13:00 UTC -------
commit 13f804123800839b4d8114deacb8a36224c62cde
Author: Tim-Philipp Müller <tim.muller at collabora.co.uk>
Date: Mon Mar 23 12:34:34 2009 +0000
basesink: fix once-per-second 'emergency rendering' for case where all
buffers but the very first are late
Due to a typo basesink didn't do any emergency rendering of late buffers
if the only buffer ever rendered was the first one with timestamp 0. This
means that in cases where the decoder is very very slow, we'd never see
any buffers but the very first one rendered. Fixes #576381.
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=576381.
More information about the Gstreamer-bugs
mailing list