GstParse Parses pipeline syntax into elements This method allows you to create a pipeline from a command line syntax description. The following example creates a simple mp3 player. GstElement *pipeline; /* create a pipeline to hold our elements */ pipeline = gst_pipeline_new ("launch"); /* build a pipeline in the pipeline */ gst_parse_launch ("filesrc location=some.mp3 ! mad ! osssink", GST_BIN (pipeline)); /* play the thing */ gst_element_set_state (pipeline, GST_STATE_PLAYING); while (gst_bin_iterate (GST_BIN (pipeline))); gst_element_set_state (pipeline, GST_STATE_NULL); Elements are separated with a !, properties are set with property=value, specific pads of an element are selected by replacing the ! with padname!. Elements can be added to a bin by embracing them with (). Threads can be made with {}. Get the error quark passed in the GError messages. @Returns: The parse error quark The error quark The parsing errors. @GST_PARSE_ERROR_SYNTAX: A syntax error was detected @GST_PARSE_ERROR_NO_SUCH_ELEMENT: The pipeline description contains a non existing element @GST_PARSE_ERROR_NO_SUCH_PROPERTY: The pipeline description contains a non existing element property @GST_PARSE_ERROR_LINK: A pad link could not be made @GST_PARSE_ERROR_COULD_NOT_SET_PROPERTY: @GST_PARSE_ERROR_EMPTY_BIN: @GST_PARSE_ERROR_EMPTY: @pipeline_description: @error: @Returns: @argv: @error: @Returns: