Tool/software: GStreamer / C++
What are the pros and cons for code parsing the gstreamer pipeline with gst-launch-parse vs. manually creation of a pipeline using factory elements?
Are there limitations for one or the other?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software: GStreamer / C++
What are the pros and cons for code parsing the gstreamer pipeline with gst-launch-parse vs. manually creation of a pipeline using factory elements?
Are there limitations for one or the other?
Hi Felix,
This is more of a Gstreamer community forum query. Please reach out to Gstreamer forum for a detailed explanation.
AFAIK, gst-launch-parse if more experimentatl/development tool for running static pipelines. Manually creating the elements and pipeline with Application, will give you more flexibility in programming the parameters of the elements dynamically (For eg- Encoder change in bitrate, resolutions, framerate etc..)
Few reference links:
https://gstreamer.freedesktop.org/documentation/application-development/
https://stackoverflow.com/questions/16100967/limitations-of-gst-parse-launch
Hope this helps.
Best Regards,
Suren
Thanks for your quick response. We will have a look on the references and sorry for the confusion.