Gstreamer critical on pipeline.set_state(Gst.State.NULL)

Krutskikh Ivan stein.hak at gmail.com
Sun Jul 31 06:54:56 UTC 2016


I would like to bump my question

2016-07-29 13:59 GMT+03:00 Krutskikh Ivan <stein.hak at gmail.com>:

> Maybe I should go with sync state changes on all my pipelines?
>
> 2016-07-29 13:53 GMT+03:00 Krutskikh Ivan <stein.hak at gmail.com>:
>
>> Hi all,
>>
>> I get a really annoying bug while using gstreamer on python. :
>>
>>
>> GStreamer-CRITICAL **:
>> июл 26 16:09:44 archive1 distributor.py[5954]: Trying to dispose element
>> queue9, but it is in PLAYING instead of the NULL state.
>>
>> And such for every element of the pipeline.
>>
>> I use Gst.parse_launch for creating pipelines and
>>
>>     def message_handler(self,bus,message):
>>         streamer = None
>>         for s in self.job.streamers:
>>             if s.get_bus() == bus:
>>                 streamer = s
>>
>>         msgType = message.type
>>
>>         if msgType == Gst.MessageType.ERROR or msgType ==
>> Gst.MessageType.EOS:
>>             streamer.pipeline.set_state(Gst.State.NULL)
>>             if streamer == self.job.streamers[0]:
>>                 if self.queue and not self.export_running:
>>                     self.finish()
>>
>>                 if self.ping_test(self.host) == 0:
>>                     self.job.state = -2
>>                 else:
>>                     self.job.state = -1
>>                 self.recorder = None
>>
>>             streamer = None
>>
>> For message handling.
>>
>> This is kind of urgent for me, what can I do to solve this?
>>
>> Thanks in advance!
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160731/4a5315e8/attachment.html>


More information about the gstreamer-devel mailing list