Parse pipeline to Python

Arjen Veenhuizen arjen at moonlightmedia.nl
Tue Apr 4 11:07:31 UTC 2017


The biggest differences between your command line pipeline and your code is
that on the former you rely on decodebin to do all the hard word of
selecting the correct demuxer and decoders while in the latter you try to do
it yourself. It is quite possible that you selected the incorrect elements.

Follow these [1] steps to create a DOT file of your command line pipeline
and convert the DOT file to a PNG. This PNG gives you insight in what
decodebin is actually doing under the hood. Check it to make sure you are
using the correct demuxer and decoders. 

[1]
https://developer.ridgerun.com/wiki/index.php/How_to_generate_a_Gstreamer_pipeline_diagram_(graph)




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Parse-pipeline-to-Python-tp4682430p4682508.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list