[gstreamer-bugs] [Bug 480222] mpegdemux does not emit no-more-pads signal

[GStreamer (bugzilla.gnome.org)]

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

  GStreamer | gst-plugins-ugly | Ver: 0.10.6

Wim Taymans changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |NOTABUG




------- Comment #7 from Wim Taymans  2009-05-06 15:53 UTC -------
no-more-pads should be used like this:

 - an element that knows exactly how many streams there will be for the
complete
   duration of the stream can signal this when it has added all pads
   (qtdemux, avidemux). It is expected that no more pads appear while
streaming.

 - If after the no-more-pads signal more streams appear, the application should
   assume that all previous pads will be removed from the element. The pads 
   added after the no-more-pads signal belong to a new group or related media
   and is in no way related to the previous pads. (oggdemux with chained oggs)

 - An element that does not know how many streams there will be at runtime and
   where pads can appear/disappear while streaming, should not signal
   no-more-pads. The application must peek into the file for a configurable
   amount of time/bytes before starting playback of the discovered streams.
When
   streams are added at a later time, they will logically belong to the
   previously streams. (mpeg2 but maybe not mpeg1, which has fixed headers)

The no-more-pads signal thus marks the boundaries of related streams. Decodebin
uses this signal to quickly start playback instead of waiting for queues to
fill up. It's also used to manage the pad groups in decodebin2.

so you need to look at how the container works and what the features are to
determine if it should emit no-more-pads or not. Hope that clears it up. 


-- 
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=480222.