GStreamer Daemon - Interacting with Pipelines: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
No edit summary
Line 22: Line 22:
# A pipeline named ''p3'' consisting on an audio+video transport stream video recording.
# A pipeline named ''p3'' consisting on an audio+video transport stream video recording.


On the other hand, the following commands '''will fail'''


⇒ ''Failed Gstd Commands:''
<syntaxhighlight lang="bash" line="line" style="background-color:lavender">
pipeline_create videotestsrc ! autovideosink
pipeline_create p
pipeline_create p ridgerun
</syntaxhighlight>
They will fail because:
# No name was specified
# No description was provided
# The pipeline syntax is wrong (there's no element named ridgerun)


== Play Pipelines ==
== Play Pipelines ==

Revision as of 21:29, 19 May 2017



Home


This wiki describes the basics on how to interact with GStreamer pipelines. Specifically, how to create new pipelines, change their state, list existing pipelines and finally destroy them. You'll find that the family of commands used to interact with pipelines are prefixed with pipeline_<action>.

Create Pipelines

In order to create a pipeline use the following command:

pipeline_create name description
Creates a new pipeline named after name using the description gst-launch syntax.

For example:

Gstd Commands:

pipeline_create p1 videotestsrc ! autovideosink
pipeline_create p2 playbin
pipeline_create p3 mpegtsmux name=mux videotestsrc ! x264enc ! mux. audiotestsrc ! avenc_aac ! mux. mux. ! filesink location=test.ts

would create respectively:

  1. A pipeline named p1 consisting on a simple videotestsrc display
  2. A pipeline named p2 consisting on a single element (playbin), which is enough to do playback of a file
  3. A pipeline named p3 consisting on an audio+video transport stream video recording.

On the other hand, the following commands will fail

Failed Gstd Commands:

pipeline_create videotestsrc ! autovideosink
pipeline_create p
pipeline_create p ridgerun

They will fail because:

  1. No name was specified
  2. No description was provided
  3. The pipeline syntax is wrong (there's no element named ridgerun)

Play Pipelines

Pause Pipelines

Stop Pipelines

Delete Pipelines

List Pipelines




Home