MAN page 발췌
NAME gst-launch-1.0 - build and run a GStreamer pipeline SYNOPSIS gst-launch-1.0 [OPTION...] PIPELINE-DESCRIPTION DESCRIPTION gst-launch-1.0 is a tool that builds and runs basic GStreamer pipelines. In simple form, a PIPELINE-DESCRIPTION is a list of elements separated by exclamation marks (!). Properties may be appended to elements, in the form property=value. For a complete description of possible PIPELINE-DESCRIPTIONS see the section pipeline description below or consult the GStreamer documentation. Please note that gst-launch-1.0 is primarily a debugging tool for developers and users. You should not build applications on top of it. For applications, use the gst_parse_launch() function of the GStreamer API as an easy way to construct pipe‐ lines from pipeline descriptions. PIPELINE DESCRIPTION A pipeline consists elements and links. Elements can be put into bins of different sorts. Elements, links and bins can be specified in a pipeline description in any order. Elements ELEMENTTYPE [PROPERTY1 ...] Creates an element of type ELEMENTTYPE and sets the PROPERTIES. Properties PROPERTY=VALUE ... Sets the property to the specified value. You can use gst-inspect-1.0(1) to find out about properties and allowed values of different elements. Enumeration properties can be set by name, nick or value. Bins [BINTYPE.] ( [PROPERTY1 ...] PIPELINE-DESCRIPTION ) Specifies that a bin of type BINTYPE is created and the given properties are set. Every element between the braces is put into the bin. Please note the dot that has to be used after the BINTYPE. You will almost never need this functionality, it is only really useful for applications using the gst_launch_parse() API with 'bin' as bintype. That way it is possible to build partial pipelines instead of a full-fledged top-level pipeline. Links [[SRCELEMENT].[PAD1,...]] ! [[SINKELEMENT].[PAD1,...]] [[SRCELEMENT].[PAD1,...]] ! CAPS ! [[SINKELEMENT].[PAD1,...]] [[SRCELEMENT].[PAD1,...]] : [[SINKELEMENT].[PAD1,...]] [[SRCELEMENT].[PAD1,...]] : CAPS : [[SINKELEMENT].[PAD1,...]] Links the element with name SRCELEMENT to the element with name SINKELEMENT, using the caps specified in CAPS as a filter. Names can be set on elements with the name property. If the name is omitted, the element that was specified directly in front of or after the link is used. This works across bins. If a padname is given, the link is done with these pads. If no pad names are given all possibilities are tried and a matching pad is used. If multiple padnames are given, both sides must have the same number of pads specified and multiple links are done in the given order. So the simplest link is a simple exclamation mark, that links the element to the left of it to the element right of it. Linking using the : operator attempts to link all possible pads between the elements Caps MEDIATYPE [, PROPERTY[, PROPERTY ...]]] [; CAPS[; CAPS ...]] Creates a capability with the given media type and optionally with given properties. The media type can be escaped using " or '. If you want to chain caps, you can add more caps in the same format afterwards. Properties NAME=[(TYPE)]VALUE in lists and ranges: [(TYPE)]VALUE Sets the requested property in capabilities. The name is an alphanumeric value and the type can have the following case-insensitive values: - i or int for integer values or ranges - f or float for float values or ranges - b, bool or boolean for boolean values - s, str or string for strings - fraction for fractions (framerate, pixel-aspect-ratio) - l or list for lists If no type was given, the following order is tried: integer, float, boolean, string. Integer values must be parsable by strtol(), floats by strtod(). FOURCC values may either be integers or strings. Boolean values are (case insensitive) yes, no, true or false and may like strings be escaped with " or '. Ranges are in this format: [ VALUE, VALUE ] Lists use this format: { VALUE [, VALUE ...] } PIPELINE EXAMPLES The examples below assume that you have the correct plug-ins available. In general, "pulsesink" can be substituted with another audio output plug-in such as "alsasink" or "osxaudiosink" Likewise, "xvimagesink" can be substituted with "xima‐ gesink", "glimagesink", or "osxvideosink". Keep in mind though that different sinks might accept different formats and even the same sink might accept different formats on different machines, so you might need to add converter elements like audioconvert and audioresample (for audio) or videoconvert (for video) in front of the sink to make things work. Audio playback Play the mp3 music file "music.mp3" using a libmpg123-based plug-in and output to an Pulseaudio device gst-launch-1.0 filesrc location=music.mp3 ! mpegaudioparse ! mpg123audiodec ! audioconvert ! audioresample ! pulsesink Play an Ogg Vorbis format file gst-launch-1.0 filesrc location=music.ogg ! oggdemux ! vorbisdec ! audioconvert ! audioresample ! pulsesink Play an mp3 file or an http stream using GIO gst-launch-1.0 giosrc location=music.mp3 ! mpegaudioparse ! mpg123audiodec ! audioconvert ! pulsesink gst-launch-1.0 giosrc location=http://domain.com/music.mp3 ! mpegaudioparse ! mpg123audiodec ! audioconvert ! audioresample ! pulsesink Use GIO to play an mp3 file located on an SMB server gst-launch-1.0 giosrc location=smb://computer/music.mp3 ! mpegaudioparse ! mpg123audiodec ! audioconvert ! audioresample ! pulsesink Format conversion Convert an mp3 music file to an Ogg Vorbis file gst-launch-1.0 filesrc location=music.mp3 ! mpegaudioparse ! mpg123audiodec ! audioconvert ! vorbisenc ! oggmux ! filesink location=music.ogg Convert to the FLAC format gst-launch-1.0 filesrc location=music.mp3 ! mpegaudioparse ! mpg123audiodec ! audioconvert ! flacenc ! filesink location=test.flac |
'프로그램 사용 > gstreamer' 카테고리의 다른 글
gst h264 filesink (0) | 2021.07.14 |
---|---|
gstreamer 관련 (0) | 2021.07.13 |
gstreamer element 생성 gst_element_factory_make() (0) | 2021.07.13 |
gst fpsdisplaysink (0) | 2021.02.18 |
gst videorate (0) | 2021.02.09 |