[Bug 757548] aggregator: Forced to produce data in paused state

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Fri Apr 15 13:23:24 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=757548

--- Comment #8 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
(In reply to Nicolas Dufresne (stormer) from comment #7)
> That case seems to be really rare in fact. If I read correctly, GstBaseSrc
> will send the stream-start before it call create/fill which is the one that
> may block if there is no data coming. For demuxers, the non-enforced rule is
> that expose pads should have caps, which imply that stream-start has been
> "sticked" to the pad already. So I agree the use case might exist, but it's
> probably avoidable in most cases.

Note that for demuxers it's not that easy. They are expected to have
stream-start on the pad when they expose it... but the event is only forwarded
downstream then after linking when the next buffer is pushed (or serialized
event). So maybe much later.

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