Dynamically changing the pipeline example code

[David Jaggard]

Thank you. I was just missing the fact that EOS blocks the pad from
receiving more data.

On 9 February 2016 at 15:42, Tim Müller <tim at centricular.com> wrote:

> On Tue, 2016-02-09 at 15:17 +0000, David Jaggard wrote:
>
> Hi David,
>
> > But it appears that all the callback does is inject the EOS event and
> > then exit. It does not appear to wait for the EOS event to reach the
> > next probe (which could happen several seconds later if the element
> > is a queue, for example). So as the blocking probe has now been
> > removed from the element sink it appears to be possible for data to
> > flow again into the element. Or does the EOS event itself prevent
> > that element from accepting any more data?
>
> That's right, when you push an EOS event on a pad, the pad will be
> flagged as EOS and when someone tries to push more data to it, they'll
> get a GST_FLOW_EOS flow return and upstream will stop streaming in
> response to that.
>
> The application will have to wait for an EOS message on the bus to make
> sure the EOS has filtered through to the sink and everything has
> finished up as it should.
>
> Cheers
>  -Tim
>
> --
> Tim Müller, Centricular Ltd - http://www.centricular.com
>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160209/ab07c8e0/attachment.html>