AW: Unable to change state GST_STATE_PLAYING - possible bug in decodebin ?

[Thornton, Keith]

Hi,
it does not re-use src_0 and src_1 until it has cycled through the possibilities. The next pads used are src_2 and src_3. ... When you know this, you can use this information when reconnecting. I don't think it is a bug.

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] Im Auftrag von amitchawla
Gesendet: Freitag, 3. Juni 2016 11:07
An: gstreamer-devel at lists.freedesktop.org
Betreff: Re: Unable to change state GST_STATE_PLAYING - possible bug in decodebin ?

Hi

I have discovered that when I restart the pipeline, the source pads of the demux (decodebin) , do not get linked. From the GST_PADS debug messages, it is appearing that ,
 
During the initial normal playing of the pipeline (from gst_parse_launch ), decodebin src_0 and src_1 pads are connected to imxeglvivsink and autoaudiosink , but after I restart the pipeline.... 
 
GST_STATE_READY -> GST_STATE_PAUSE , the debug messages from GST_PADS show that decodebin is attempting to send events and messages on decodebin source pads src_2 and src_3 , which were obviously not linked initially... that is why it is getting "not linked" debug messages.

it is a possible bug in decodebin, or do I have to do something else to reconnect to src_0 and src_1 pads ?

Amit





--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Unable-to-change-state-GST-STATE-PLAYING-tp4677811p4677874.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel