[gstreamer-bugs] [Bug 539042] New: input-selector emit multiple segments with select-all=True
bugzilla-daemon at bugzilla.gnome.org
Wed Jun 18 15:33:05 PDT 2008
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:
GStreamer | gst-plugins-bad | Ver: HEAD CVS
Summary: input-selector emit multiple segments with select-
Version: HEAD CVS
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: tester at tester.ca
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
I'm testing switching video codecs live with farsight2, whenever a new video
codec appears, a new pad comes out of fs2 and I like it to an input-selector
with "select-all" set to True (thats then connected to an xvimagesink).
It fails because every time a new pad is connected, it also sends a NEWSEGMENT
event that input-selector forwards almost blindly and that the sink then
I guess that input-selector should do much more complicated magic with the
segments and combine them in a smart way and check if an update should be sent
instead of a newsegment (or maybe nothing if they match).. Maybe even in the
case of select-all, it should just retimestamp every buffer to the running time
and only send a [0,-1] segment out or something...
Here is a small demo program:
pipeline = gst.parse_launch ("videotestsrc is-live=1 ! input-selector
select-all=1 name=a ! xvimagesink")
vts = gst.element_factory_make("videotestsrc")
print "added second source"
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=539042.
More information about the Gstreamer-bugs