GNOME Bugzilla – Bug 153814
alsasink still broken (segfaults) on nforce2 chipset
Last modified: 2005-08-29 15:43:30 UTC
I have an athlon with nforce2 chipset running suse 9.1 (kernel 2.6.5) When trying to run gstreamer with alsasink i get a floating point exception. osssink runs fine. Other apps run fine with alsa. gst-launch-0.8 filesrc location=file.{mp3|ogg} ! spider ! volume ! alsasink RUNNING pipeline ... Excepción de coma flotante
Blease provide a backtrace.
Here is the backtrace. Hope it's ok (gdb) backtrace
+ Trace 50538
i had a similar problem with gstreamer and alsasink as output, what solved this problem for me was setting the Default Sink to Output: Custom & pipeline: "alsasink device=output" in gstreamer-properties. With Output: ALSA gstreamer-properties crashes with the message "gstreamer-properties: pcm.c:2094: snd_pcm_wait: Assertion `err == 1' failed."
If I use the "device=hw:0,0" property I get another kind of error miguel@linux:~> gst-launch-0.8 filesrc location=file.ogg ! spider ! volume ! alsasink device=hw:0,0 RUNNING pipeline ... ERROR: from element /pipeline0/spider0/vorbisdec0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2490): gst_pad_set_explicit_caps: /pipeline0/spider0/vorbisdec0: failed to negotiate (try_set_caps with "audio/x-raw-float, rate=(int)44100, channels=(int)2, endianness=(int)1234, width=(int)32, buffer-frames=(int)0" returned REFUSED) Execution ended after 14 iterations (sum 203615000 ns, average 14543928 ns, min 30000 ns, max 108520000 ns).
That's a negotiation error, and you'd expect that. Use audioscale and audioconvert in between: gst-launch-0.8 filesrc location=file.ogg ! spider ! audioconvert ! audioscale ! volume ! alsasink device=hw:0,0
gst-launch-0.8 filesrc location=file.ogg ! spider ! audioconvert ! audioscale ! volume ! alsasink device=hw:0,0 That works fine! Using "device=default" still segfaults.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 151288 ***