[Bug 721310] GstBin: consider allowing option to block propagation of EOS

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Thu Jan 2 01:10:00 PST 2014


https://bugzilla.gnome.org/show_bug.cgi?id=721310
  GStreamer | gstreamer (core) | git

Sebastian Dröge (slomo) <slomo> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |slomo at coaxion.net,
                   |                            |wim.taymans at gmail.com
     Ever Confirmed|0                           |1

--- Comment #2 from Sebastian Dröge (slomo) <slomo at coaxion.net> 2014-01-02 09:09:56 UTC ---
Not sure either but the potential problem I see here is if you have multiple
sinks and just want to drain one of them. You'll never get the EOS message in
your application unless the other sink goes EOS too.

The forward-message property does not seem like a solution for this as you have
to set it on all bins in the hierarchy and it's rather inconvenient if all you
want is to drain one sink. I think something like a sync message handler would
be good to have here (which can't be used because the parent bin installs one),
some signal that hooks into GstElement::post_message() or something like that.
I currently don't see a clean solution other than subclassing GstBin (not
convenient), forward-message on *all* bins (not convenient) or adding some new
API.


All this child-parent message handling should be rewritten to use
GstElement::post_message() too instead of child busses, but that's a separate
issue.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list