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

[Stirling Westrup]

In any case, a solution to the problem has been found, it seems.

On Fri, Sep 25, 2015 at 3:24 PM, Stirling Westrup <swestrup at gmail.com>
wrote:

> 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.
>
>
>


-- 
Stirling Westrup
Programmer, Entrepreneur.
https://www.linkedin.com/e/fpf/77228
http://www.linkedin.com/in/swestrup
http://technaut.livejournal.com
http://sourceforge.net/users/stirlingwestrup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20150925/771a4251/attachment.html>