GNOME Bugzilla – Bug 134498
Gstreamer fails to play audio through any sink
Last modified: 2004-12-22 21:47:04 UTC
Whenever I try to play audio through gstreamer via the command-line or any program that interfaces with it, I either get no sound at all or static. The following commands produce static: /opt/gnome2/bin/gst-launch gnomevfssrc location=/Side.ogg ! volume ! audioconvert ! esdsink or change esdsink to ossink. I am using a Sound Blaster Live on the 2.6.1 kernel with alsa as the sound drivers. This is not format specific mp3s suffer from the same static sound. This is CVS Gstreamer checked out as of ~22:00 Pacific time
What happens when you run 'gst-launch sinesrc ! audioconvert ! osssink' or 'sinesrc ! osssink'?
When I run each command they both have the same effect of a variable beeping noise sounding like morsecode, but very very fast. Not a continous beep like I have heard it should be. cowbud@udc ~$ gst-launch sinesrc ! osssink RUNNING pipeline ... Caught interrupt. Execution ended after 27 iterations (sum 665228000 ns, average 24638074 ns, min 613000 ns, max 42256000 ns). cowbud@udc ~$ gst-launch sinesrc ! audioconvert ! osssink RUNNING pipeline ... Caught interrupt. Execution ended after 18 iterations (sum 520723000 ns, average 28929055 ns, min 714000 ns, max 122310000 ns).
Oops, sinesrc was broken. Could you update CVS and try sinesrc ! osssink again?
Just updated CVS, same issue. No other compile errors or anything. If there is any more information I can provide you with let me know.
Updated to latest CVS, problem is now fixed
Sorry I guess I got excited about the gst-launch playing a sine wave. Apparently the first issue is still an issue. When I do the following: /opt/gnome2/bin/gst-launch gnomevfssrc location=/mnt/more/Mp3\ Sinles/The_White_Stripes_-_Elephant_-_01_-_Seven_Nation_Army.mp3 ! volume ! osssink with osssink or esdsink I get static, however gst-launch sinesrc ! audioconvert ! osssink which didn't work before now works perfectly.
you forgot a decoder, like "mad" :) can you try again with that ?
looking at it again, you didn't have a decoder in your first example either, so I'm pretty sure this isn't an actual bug.
I agree with Thomas, this isn't a bug...