[gstreamer-bugs] [Bug 160730] New: mpegdemuxer should remove pads on "new-media" event
bugzilla-daemon at bugzilla.gnome.org
bugzilla-daemon at bugzilla.gnome.org
Tue Dec 7 13:14:36 PST 2004
http://bugzilla.gnome.org/show_bug.cgi?id=160730
GStreamer | gst-plugins | Ver: HEAD CVS
Summary: mpegdemuxer should remove pads on "new-media" event
Product: GStreamer
Version: HEAD CVS
Platform: Other
OS/Version: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: meiker at upb.de
QAContact: gstreamer-bugs at lists.sourceforge.net
This feature would greatly help to implement channel zapping in the DVB sample
application (in the sandbox module). dvbsrc is sending a "new-media" event every
time it tunes to a new channel. The new channel may or may not contain new
elemtary stream ids for audio and/or video. In the following usecase a DVB
application (or spider...) can not determine which pads to connect to the mpeg
decoder elements.
1. Decoding channel A with eid's 1/2 (A/V)
Pads audio_00 and video_00 have been created in the mpegdemuxer
App linked them to the decoder elements
2. Tuning to channel B with eid's 3/4
"new-pad" event is emmited for audio_01, video_01
App links new pads to the decoder elements
3. Tuning back to channel A
No "new-pad" events are emmited so the wrong pads remain connected
to the decoder elements. The app actually knows it changed the channel
but as to assume (or awkwardly verify) that the pads which are connected
to the decoder elements are the correct ones.
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.
More information about the Gstreamer-bugs
mailing list