mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2024-12-25 01:30:38 +00:00
1c1af875d4
Original commit message from CVS: * check/gst/gstbin.c: (pop_messages), (GST_START_TEST): * check/gst/gstbus.c: (message_func_eos), (message_func_app), (send_messages), (GST_START_TEST), (gstbus_suite): * check/gst/gstpipeline.c: (GST_START_TEST): * check/pipelines/cleanup.c: (run_pipeline): * check/pipelines/simple_launch_lines.c: (run_pipeline), (GST_START_TEST): * gst/gstbus.c: (gst_bus_have_pending), (gst_bus_source_prepare), (gst_bus_source_check), (gst_bus_source_dispatch), (gst_bus_create_watch), (gst_bus_add_watch_full), (gst_bus_add_watch), (poll_func), (poll_timeout), (gst_bus_poll): * gst/gstbus.h: * tools/gst-launch.c: (event_loop): * tools/gst-md5sum.c: (event_loop): GstBusHandler -> GstBusFunc, return value has the same meaning as any other GSource (FALSE == remove source). _add_watch() and _add_watch_full() now take a MessageType mask to only handle specific types of messages. _poll() returns the GstMessage instead of the message type to avoid race conditions. _have_pending() takes a MessageType mask now too. Added testsuite for multiple bus watches. Fix testsuites and applications for new bus API. |
||
---|---|---|
.. | ||
.gitignore | ||
BUGS | ||
gst-complete.1.in | ||
gst-complete.c | ||
gst-compprep.1.in | ||
gst-compprep.c | ||
gst-feedback-0.7 | ||
gst-feedback-m.m | ||
gst-feedback.1.in | ||
gst-indent | ||
gst-inspect.1.in | ||
gst-inspect.c | ||
gst-launch.1.in | ||
gst-launch.c | ||
gst-md5sum.1.in | ||
gst-md5sum.c | ||
gst-run.c | ||
gst-typefind.1.in | ||
gst-typefind.c | ||
gst-xmlinspect.1.in | ||
gst-xmlinspect.c | ||
gst-xmllaunch.1.in | ||
Makefile.am | ||
README | ||
xml2text.xsl |
gst-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: gst-launch filesrc location=music.mp3 ! mad ! osssink This plays an mp3 music file music.mp3 using libmad, and: gst-launch filesrc location=music.mp3 ! mp3parse ! mpg123 ! osssink Plays and mp3 music file using mpg123 You can also stream files over http: gst-launch httpsrc location=http://domain.com/music.mp3 ! mad ! osssink And using gnome-vfs you can do the same with: gst-launch gnomevfssrc location=music.mp3 ! mad ! osssink gst-launch gnomevfssrc location=http://domain.com/music.mp3 ! mad ! osssink And too play the same song with gnome-vfs via smb: gst-launch gnomevfssrc location=smb://computer/music.mp3 ! mad ! osssink Here we convert a Mp3 file into an Ogg Vorbis file: gst-launch filesrc location=music.mp3 ! mad ! vorbisenc ! filesink location=music.ogg And then we can play that file with: gst-launch filesrc location=music.ogg ! oggdemux ! vorbisdec ! audioconvert ! osssink Some other useful pipelines are.. Plays wav files (currently there are no wav encoders): gst-launch filesrc location=music.wav ! wavparse ! osssink Converts wav files into mp3 and ogg files: gst-launch filesrc location=music.wav ! wavparse ! vorbisenc ! filesink location=music.ogg gst-launch filesrc location=music.wav ! wavparse ! mpegaudio ! filesink location=music.mp3 You can also use lame for mp3 encoding if you have it installed, it does a much better job than mpegaudio. Rips all songs from cd and saves them into a mp3 file: gst-launch cdparanoia ! mpegaudio ! filesink location=cd.mp3 You can toy around with gst-inspect to discover the settings for cdparanoia to rip individual tracks Record sound from your sound input and encode it into an ogg file: gst-launch osssrc ! vorbisenc ! filesink location=input.ogg gst-launch not only handles audio but video as well: For mpeg1 files (video and audio streams respectively): gst-launch filesrc location=video.mpg ! mpegdemux video_00! { queue ! mpeg2dec ! sdlvideosink } gst-launch filesrc location=video.mpg ! mpegdemux audio_00! { queue ! mad ! osssink } for mpeg1 with both audio and video (for glib2): gst-launch filesrc location=video.mpg ! mpegdemux name=demux video_00! { queue ! mpeg2dec ! sdlvideosink } demux.audio_00! { queue ! mad ! osssink } for mpeg1 with both audio and video (for gtk1.2, the shim doesn't handle the 'name' property yet): gst-launch filesrc location=video.mpg ! mpegdemux video_00! { queue ! mpeg2dec ! sdlvideosink } mpegdemux0.audio_00! { queue ! mad ! osssink } For mpeg2 files (video and audio streams respectively): gst-launch filesrc location=video.mpeg ! mpegdemux video_00! { queue ! mpeg2dec ! sdlvideosink } gst-launch filesrc location=video.mpeg ! mpegdemux private_stream_1.0! { queue ! a52dec ! osssink } for mpeg2 with both audio and video (glib2): gst-launch filesrc location=video.mpg ! mpegdemux name=demux video_00! { queue ! mpeg2dec ! sdlvideosink } demux.private_stream_1.0! { queue ! a52dec ! osssink } Note: The types of audio streams in the mpeg files can vary! For an avi file (DivX, mjpeg,...) gst-launch filesrc location=video.avi ! avidecoder video_00! { queue ! sdlvideosink } avidecoder0.audio_00! { queue ! osssink } gst-complete ================== This is a simple utility which provides custom bash completion when typing gst-launch commands. Simply run "gst-compprep" as root to build the registry of completions, and then put, in your .bashrc, "complete -C gst-complete gst-launch" (ensuring that gst-complete is on your path). You can then enjoy context sensitive tab-completion of gst-launch commands. gst-register ================== This tool will perform an introspection on all available plugins and will create a registry file in /etc/gstreamer/reg.xml. Startup time will be much faster since the gstreamer core doesn't have to bring all the plugins files into memory at startup. As with gst-compprep you need to run this as root for it too work correctly. gst-inspect ================= Allows you to check the properties of plugins and elements. ./gst-inspect will show all the plugins available and the elements they contain. ./gst-inspect <pluginname/elementname> shows more info about the plugin/element. gst-xmlinspect ================= Dump properties of plugins and elements in an xml format. You can transform the xml to something else with an appropriate stylesheet. ./gst-xmlinspect <elementname> | xsltproc xml2text.xsl -