appsink and EOS

[Tim-Philipp Müller]

On Sun, 2012-09-09 at 00:03 -0700, Brian Quandt wrote:

Hi Brian,

> I'm not sure this works, ie I've already tried the set_state routes,
> but I any attempt to change the state not returning from the state
> change call, ie
> sink.set_state(gst.STATE_NULL) 
> never returns, and no error messages.
>
> This is gstreamer version 0.10, using python as my development
> environment.

Do you have a small test application that demonstrates your issue?

Where are you doing the set_state call from? Are you doing it from a
callback? (i.e. from the streaming thread not your application thread)

Cheers
 -Tim

> 
> On Fri, Sep 7, 2012 at 1:45 AM, Tim-Philipp Müller <t.i.m at zen.co.uk>
> wrote
>         On Thu, 2012-09-06 at 21:54 -0700, Brian Quandt wrote:
>         
>         > Is there a way to get an appsink out of EOS, after it has
>         received
>         > such a notification and now reports itself via its eos
>         property as
>         > being in EOS (ie eos property which is readonly is set to
>         true)?
>         >
>         > Or do you have to just delete the element and recreate it
>         and hook a
>         > new one back into the bin?
>         
>         Either do a flushing seek on the pipeline (or the sink), or
>         set the
>         sink's state to NULL or READY and then back to PLAYING again.
>         
>         Cheers
>          -Tim
>         
>         _______________________________________________
>         gstreamer-devel mailing list
>         gstreamer-devel at lists.freedesktop.org
>         http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> 
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel