[gstreamer-bugs] [Bug 443081] volume plugin goes async forever
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Sat Jun 2 02:37:15 PDT 2007
If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
http://bugzilla.gnome.org/show_bug.cgi?id=443081
GStreamer | gst-plugins-base | Ver: 0.10.12
Tim-Philipp Müller changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDINFO
------- Comment #2 from Tim-Philipp Müller 2007-06-02 09:37 UTC -------
Probably not a bug, but wrong usage. There are raw audio formats that volume
doesn't handle. There are also sample rates and raw audio formats that alsasink
can't not handle (depends on your driver, device etc.). If gst-launch can't
link two elements right away, it will wait to see if something in the pipeline
creates a new pad later, hoping that might then work. This is probably what
you're seeing here. Data never makes it to the sink, and gst-launch waits
around for more pads.
Try this:
gst-launch-0.10 filesrc location=... ! wavparse ! audioconvert ! volume !
audioconvert ! audioresample ! alsasink
or:
gst-launch-0.10 playbin uri=file:///path/to/foo.wav
--
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.
You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=443081.
More information about the Gstreamer-bugs
mailing list