Got EOS from element "pipeline0" -> help with sometimes pads

Sebastian Dröge sebastian at centricular.com
Tue Oct 25 10:53:18 UTC 2016


On Mon, 2016-10-24 at 22:44 +0200, Graham Leggett wrote:
> Hi all,
> 
> I have the following streaming pipeline which runs for a few seconds,
> and then without being asked to, the pipeline gracefully shuts down
> as below.
> 
> For obvious reasons this is fatal for streaming - this needs to
> stream forever, and not shut down.
> 
> I am trying to understand the cause of this behaviour, and am
> struggling. As a guess, would “sometimes” pads be potentially
> involved? The tsdemux exposes sometimes pads, which delays the
> linking of the queue element. Am I right in guessing that if for some
> reason tsdemux decided to remove a sometimes pad for whatever reason
> (errors in the stream, who knows), this would trigger the rest of the
> stream and therefore the whole pipeline to shut down?

The stream could've changed, in which case you would have to link
dynamically new pads to the new pads of tsdemux (you can't do that with
gst-launch), or it might've encountered an error.

If you use playbin, it would handle that internally.

> If so, what could I do to prevent the shutdown? Is there an element
> that will relink a sometimes pad to an always pad on an unreliable
> stream if the sometimes pad goes away and comes back?

No but that can be implemented with some code

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20161025/783732e5/attachment.sig>


More information about the gstreamer-devel mailing list