[gstreamer-bugs] [Bug 579058] [asfdemux] proper handling of RTSP input
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Tue May 5 13:49:46 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=579058
GStreamer | gst-plugins-ugly | Ver: git
Mark Nauwelaerts changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manauw at skynet.be
------- Comment #5 from Mark Nauwelaerts 2009-05-05 20:49 UTC -------
I would say special handling involves some catering for latency (due to
internal preroll prior to activation of pads) and minding a bit more about
upstream segments. IMHO, most of this has been addressed by some recent
commits, among which
commit 0b28139203e17be6f1bf0e504cde0cbfac55e860
Author: Mark Nauwelaerts <mark.nauwelaerts at collabora.co.uk>
Date: Sat May 2 13:45:22 2009 +0200
asfdemux: report initial latency due to internal preroll queue
commit b6d4fb9e4f4e562a7de1691b37cded2859b86235
Author: Mark Nauwelaerts <mark.nauwelaerts at collabora.co.uk>
Date: Sat May 2 16:08:03 2009 +0200
asfdemux: fixes for streaming mode
* Improve newsegment handling, e.g. upstream might live in TIME.
* Only send newsegment if we have needed info.
* Avoid reading past end of data section.
--
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=579058.
More information about the Gstreamer-bugs
mailing list