GStreamer FAQ (0.8.10) | ||
---|---|---|
<<< Previous | Next >>> |
A: First of all, verify that you have a working registry and that you can inspect them by typing
$ gst-inspect fakesrc |
It's time to try out a few things. Start with gst-launch and two plug-ins that you really should have : fakesrc and fakesink. They do nothing except pass empty buffers. Type this at the command-line :
$ gst-launch -v fakesrc num-buffers=3 ! fakesink |
RUNNING pipeline ... fakesrc0: last-message = "get ******* (fakesrc0:src)gt; (0 bytes, 0) 0x8057510" fakesink0: last-message = "chain ******* (fakesink0:sink)lt; (0 bytes, 0) 0x8057510" fakesrc0: last-message = "get ******* (fakesrc0:src)gt; (0 bytes, 1) 0x8057510" fakesink0: last-message = "chain ******* (fakesink0:sink)lt; (0 bytes, 1) 0x8057510" fakesrc0: last-message = "get ******* (fakesrc0:src)gt; (0 bytes, 2) 0x8057510" fakesink0: last-message = "chain ******* (fakesink0:sink)lt; (0 bytes, 2) 0x8057510" execution ended after 5 iterations (sum 301479000 ns, average 60295800 ns, min 3000 ns, max 105482000 ns) |
A: You can test this by trying to play a sine tone. For this, you need to link the sinesrc plug-in to an output plug-in that matches your hardware. A (non-complete) list of output plug-ins for audio is
osssink for OSS output
esdsink for ESound output
artsdsink for aRTs output
alsasink for ALSA output
jacksink for JACK output
$ gst-inspect osssink |
Then try to play the sine tone by running
$ gst-launch sinesrc ! osssink |
In GNOME, you can configure audio output for most applications by running
$ gstreamer-properties |
A: To do this you use the gst-inspect command-line tool, which comes standard with GStreamer. Invoked without any arguments,
$ gst-inspect |
$ gst-inspect volume |
Also, if you install the gst-editor package, you will have a graphical plugin browser available, gst-inspect-gui.
A: Bug management is now hosted on GNOME's Bugzilla at http://bugzilla.gnome.org, under the product GStreamer. Using bugzilla you can view past bug history, report new bugs, etc. Bugzilla requires you to make an account here, which might seem cumbersome, but allows us to at least have a chance at contacting you for further information, as we will most likely have to.
A: When doing a bug report, you should at least describe
your distribution
how you installed GStreamer (from cvs, source, packages, which ?)
if you installed GStreamer before
It also is useful for us if you attach output of the gst-feedback command to your bug report. If you're having problem with a specific application (either one of ours, somebody else's, or your own), please also provide a log of gst-mask by running
myapp --gst-mask=-1 > mask.log 2>&1 gzip mask.log |
If the application you are having problems with is segfaulting, then provide us with the necessary gdb output. See The GStreamer application I used stops with a segmentation fault. What can I do ?
A: You access the GStreamer command line interface using the command gst-launch. To decode an mp3 and play it through OSS, you could use
gst-launch filesrc location=thesong.mp3 ! mad ! osssink |
To automatically detect the right codec in a pipeline, try
gst-launch filesrc location=my-random-media-file.mpeg ! spider ! osssink |
We also have a simple tool called gst-launch-ext used for debugging, which has predefined pipelines for you. This means you can just write
gst-launch-ext (filename) |
<<< Previous | Home | Next >>> |
Getting GStreamer | Troubleshooting GStreamer |