State Change *always* times out, then immediately succeeds!

Stirling Westrup swestrup at gmail.com
Fri Sep 25 12:24:33 PDT 2015


On Sat, Sep 19, 2015 at 8:39 AM, Sérgio Agostinho <
sergio.r.agostinho at gmail.com> wrote:

> Why are you going for GST_MESSAGE_ASYNC_DONE instead
> of  GST_MESSAGE_STATE_CHANGED?
> Notice the example they give in the documentation
>
> http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/GstMessage.html#gst-message-parse-state-changed
> You have access to the object's (unique) name.
>

Yes, but the bus monitoring routine has no knowledge of the target states
of pipeline objects, so it can't tell which STATE CHANGED messages are
relevant, and which not. It would have to signal ALL of them.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20150925/9893bfc9/attachment.html>


More information about the gstreamer-devel mailing list