Next: GstPipeline, Previous: GstPad, Up: Top
Get a pipeline from a text pipeline description
These function allow to create a pipeline based on the syntax used in the gst-launch utillity.
unsigned-int
)Get the error quark used by the parsing subsystem.
- ret
- the quark of the parse errors.
mchars
) (ret <gst-element>
)Create a new pipeline based on command line syntax. Please note that you might get a return value that is not ‘
#f
’ even though the error is set. In this case there was a recoverable parsing error and you can try to play the pipeline.
- pipeline-description
- the command line describing the pipeline
- error
- the error message in case of an erroneous pipeline.
- ret
- a new element on success, ‘
#f
’ on failure. If more than one toplevel element is specified by the pipeline-description, all elements are put into a<gst-pipeline>
, which than is returned.
mchars
) (ghost_unconnected_pads bool
) (ret <gst-element>
)This is a convenience wrapper around
gst-parse-launch
to create a<gst-bin>
from a gst-launch-style pipeline description. Seegst-parse-launch
and the gst-launch man page for details about the syntax. Ghost pads on the bin for unconnected source or sink pads within the bin can automatically be created (but only a maximum of one ghost pad for each direction will be created; if you expect multiple unconnected source pads or multiple unconnected sink pads and want them all ghosted, you will have to create the ghost pads yourself).
- bin-description
- command line describing the bin
- ghost-unconnected-pads
- whether to automatically create ghost pads for unconnected source or sink pads within the bin
- err
- where to store the error message in case of an error, or NULL
- ret
- a newly-created bin, or NULL if an error occurred.
Since 0.10.3