Dynamically changing the pipeline example code

[David Jaggard]

Hi Tim,

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?

Best regards,

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

> On Mon, 2016-02-08 at 12:24 +0000, David Jaggard wrote:
>
> Hi,
>
> > Referring to the example here:
> >
> > http://gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/
> > section-dynamic-pipelines.html
> >
> > in the pad_probe_cb function the blocking probe is removed straight
> > away. It seems to me that this would allow data to continue to flow
> > into the element following the EOS. That data would then be lost when
> > the element is removed.
>
> Removing the probe inside the probe callback will only have an effect
> once you return from the callback, so it doesn't matter if that's done
> at the beginning of the function or at the end here, if I read things
> correctly.
>
> 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/fd171d19/attachment.html>