|
Hi,
Can anyone please tell me if sending a flush_stop on the pipeline (after a flush_start) ...generates a EOS through the pipeline.
In my case, I see my that my pipeline does not restart and seems to hang after I do a flush_stop.
Here is my pipeline
tcpserversrc host=192.168.100.58 port=3000 blocksize=4194304 ! decodebin name=demux ! autoaudiosink demux. ! imxeglvivsink
I do...the following steps : -
1) stop data inflow from the network
2) pipeline pause
3) flush_Start
4) flush_stop
5) change pipeline state to playing
6) re-enable_data_over the network ...
But when I do a flush_stop .... The tcpserversrc log messages say :
pausing after gst_pad_push = eos
pausing task, reason eos
----few latency query logs messages---
It changes the pipeline state to playing but the data flow does not start ....
Any hints ?
Thanks
Amit
|