[gstreamer-bugs] [Bug 415754] New GstMuxer class

[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=415754

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #27 from Mark Nauwelaerts  2008-01-21 21:38 UTC -------
What would it mean (or does it mean) to (possibly) drop GstCollectPads for
0.11?
Although it has indeed evolved into an implementation/design with some ugly
(ABI) hacks and some other (lock?) bumps, the basic "collect and call-back"
principle seems pretty OK and serves a number of elements (notably muxers)
well.
Assuming sufficiently similar streaming (API) etc in 0.11, so it should serve
there as well.

So, if not GstCollectPads (principle) for 0.11, how should muxers (a.o.) get by
in re-usable fashion?

If, however, still a GstCollectPads approach, there is (as suggested) indeed a
great deal to be said for a (e.g.) GstCollectPads2, which (unimaginatively
keep-it-simple) could be a "copied", cleaned and (MuxPads) enhanced version of
its predecessor.  I may then make a stab at this (not right now ;-) ), though
it then evidently remains to be seen whether that will be up to core
taste/specs.


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