gst-register is used to rebuild the database of plugins. It is used after a new plugin has been added to the system. The plugin database can be found, by default, in /etc/gstreamer/reg.xml. This is a tool that will construct pipelines based on a command-line syntax. A simple commandline looks like: gst-launch filesrc location=hello.mp3 ! mad ! osssink A more complex pipeline looks like: gst-launch filesrc location=redpill.vob ! mpegdemux name=demux \ demux.audio_00! { ac3parse ! a52dec ! osssink } \ demux.video_00! { mpeg2dec ! xvideosink } You can also use the the parser in you own code. GStreamer provides a function gst_parse_launch () that you can use to construt a pipeline. The following programs lets you create an mp3 pipeline using the gst_parse_launch () function: #include <gst/gst.h> int main (int argc, char *argv[]) { GstElement *pipeline; GstElement *filesrc; GError *error = NULL; gst_init (&argc, &argv); if (argc != 2) { g_print ("usage: %s <filename>\n", argv[0]); return -1; } pipeline = gst_parse_launch ("filesrc name=my_filesrc ! mad ! osssink", &error); if (!pipeline) { g_print ("Parse error: %s\n", error->message); exit (1); } filesrc = gst_bin_get_by_name (GST_BIN (pipeline), "my_filesrc"); g_object_set (G_OBJECT (filesrc), "location", argv[1], NULL); gst_element_set_state (pipeline, GST_STATE_PLAYING); while (gst_bin_iterate (GST_BIN (pipeline))); gst_element_set_state (pipeline, GST_STATE_NULL); return 0; } Note how we can retrieve the filesrc element from the constructed bin using the element name. The gst-launch syntax is processed by a flex/bison parser. This section is intended to provide a full specification of the grammar; any deviations from this specification is considered a bug. ... mad ... A bare identifier (a string beginning with a letter and containing only letters, numbers, dashes, underscores, percent signs, or colons) will create an element from a given elementfactory. In this example, an instance of the "mad" mp3 decoding plugin will be created. ... !sink ... An exclamation point, optionally having a qualified pad name (an the name of the pad, optionally preceded by the name of the element) on both sides, will connect two pads. If the source pad is not specified, a source pad from the immediately preceding element will be automatically chosen. If the sink pad is not specified, a sink pad from the next element to be constructed will be chosen. An attempt will be made to find compatible pads. Pad names may be preceded by an element name, as in my_element_name.sink_pad. ... location="http://gstreamer.net" ... The name of a property, optionally qualified with an element name, and a value, separated by an equals sign, will set a property on an element. If the element is not specified, the previous element is assumed. Strings can optionally be enclosed in quotation marks. Characters in strings may be escaped with the backtick (\). If the right-hand side is all digits, it is considered to be an integer. If it is all digits and a decimal point, it is a double. If it is "true", "false", "TRUE", or "FALSE" it is considered to be boolean. Otherwise, it is parsed as a string. The type of the property is determined later on in the parsing, and the value is converted to the target type. This conversion is not guaranteed to work, it relies on the g_value_convert routines. No error message will be displayed on an invalid conversion, due to limitations in the value convert API. ( ... ) A pipeline description between parentheses is placed into a bin. The open paren may be preceded by a type name, as in jackbin.( ... ) to make a bin of a specified type. Square brackets make pipelines, and curly braces make threads. The default toplevel bin type is a pipeline, although putting the whole description within parentheses or braces can override this default. This is a tool to query a plugin or an element about its properties. To query the information about the element mad, you would specify: gst-inspect mad Below is the output of a query for the osssink element: Factory Details: Long name: Audio Sink (OSS) Class: Sink/Audio Description: Output to a sound card via OSS Version: 0.3.3.1 Author(s): Erik Walthinsen <omega@cse.ogi.edu>, Wim Taymans <wim.taymans@chello.be> Copyright: (C) 1999 GObject +----GstObject +----GstElement +----GstOssSink Pad Templates: SINK template: 'sink' Availability: Always Capabilities: 'osssink_sink': MIME type: 'audio/raw': format: String: int endianness: Integer: 1234 width: List: Integer: 8 Integer: 16 depth: List: Integer: 8 Integer: 16 channels: Integer range: 1 - 2 law: Integer: 0 signed: List: Boolean: FALSE Boolean: TRUE rate: Integer range: 1000 - 48000 Element Flags: GST_ELEMENT_THREADSUGGESTED Element Implementation: No loopfunc(), must be chain-based or not configured yet Has change_state() function: gst_osssink_change_state Has custom save_thyself() function: gst_element_save_thyself Has custom restore_thyself() function: gst_element_restore_thyself Clocking Interaction: element requires a clock element provides a clock: GstOssClock Pads: SINK: 'sink' Implementation: Has chainfunc(): 0x40056fc0 Pad Template: 'sink' Element Arguments: name : String (Default "element") device : String (Default "/dev/dsp") mute : Boolean (Default false) format : Integer (Default 16) channels : Enum "GstAudiosinkChannels" (default 1) (0): Silence (1): Mono (2): Stereo frequency : Integer (Default 11025) fragment : Integer (Default 6) buffer-size : Integer (Default 4096) Element Signals: "handoff" : void user_function (GstOssSink* object, gpointer user_data); To query the information about a plugin, you would do: gst-inspect gstelements A sample media player.