gstreamer/tools
Wim Taymans 7ccc2cf90b Externalized the plugin information in /etc/gstreamer/reg.xml
Original commit message from CVS:
Externalized the plugin information in /etc/gstreamer/reg.xml
- no need to do a plugin_load_all()
- plugins are loaded when needed
- typedetect functions are loaded when needed (still buggy)
- no need to check for the existance of the plugin in the codecs
- added gstreamer-register to create the reg.xml file
- renamed launch to gstreamer-launch
- plugins need to register the typefactory they provide
modified the plugins to meet the new design
modified the plugins to correctly set their pad types
autoplugging can be done without loading the plugins now
2000-08-28 20:20:55 +00:00
..
.gitignore Externalized the plugin information in /etc/gstreamer/reg.xml 2000-08-28 20:20:55 +00:00
gstreamer-launch.c Externalized the plugin information in /etc/gstreamer/reg.xml 2000-08-28 20:20:55 +00:00
gstreamer-register.c Externalized the plugin information in /etc/gstreamer/reg.xml 2000-08-28 20:20:55 +00:00
Makefile.am Externalized the plugin information in /etc/gstreamer/reg.xml 2000-08-28 20:20:55 +00:00
README initial checkin 2000-01-30 10:44:33 +00:00

launch
======

This is a tool that will construct pipelines based on a command-line
syntax.  The syntax is rather complex to enable all the features I want it
to have, but should be easy to use for most people.  Multi-pathed and
feedback pipelines are the most complex.

A simple commandline looks like:

./launch disksrc demo.mp3 | mp3parse | mpg123 | audiosink-oss

A more complex pipeline looks like:

./launch disksrc redpill.vob | css-descramble | private_stream_1.0| \
(ac3parse | ac3dec | audioink-oss) video_0| (mpeg2dec | videosink)