pipeline doesn't send send GST_MESSAGE_STATE_CHANGED when changing to NULL

[gyunaev]

> You shouldn't get READY->NULL state change messages, at least not from
> the pipeline itself.

But waiting for the state change to NULL for elements should be fine, right?

> How to solve this properly depends on the design of your application.
> You probably also don't want to use gst_bus_timed_pop_filtered() but
> integrate the bus with some kind of main/event loop. 

I'm using Qt, so I'm not confident starting glib event loop as I do not know
what the hidden issues could be (and none of the Qt apps I've seen starts
it).

I considered an APPLICATION message, but if I can use the already handled
messages, this is better.

So probably the question now should be, are there any negative consequences
if
I consider sink state change to NULL as pipeline objects being destroyed?



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/pipeline-doesn-t-send-send-GST-MESSAGE-STATE-CHANGED-when-changing-to-NULL-tp4675996p4676011.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.