GNOME Bugzilla – Bug 166686
ALSA have troubles with hoary ogg file
Last modified: 2005-08-29 15:46:30 UTC
Please describe the problem: [cschalle@cschalle temp]$ gst-launch-0.8 filesrc location="warty-dance.ogg" ! oggdemux ! vorbisdec ! audioconvert ! audioscale ! alsasink RUNNING pipeline ... ERROR (0x831d918 - 307744:21:37.150543000) GST_PADS( 6591) gstpad.c(2563):gst_pad_set_explicit_caps:<vorbisdec0> failed to negotiate (try_set_caps with "audio/x-raw-float, rate=(int)11024, channels=(int)2, endianness=(int)1234, width=(int)32, buffer-frames=(int)0" returned REFUSED) ERROR: from element /pipeline0/vorbisdec0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2563): gst_pad_set_explicit_caps: /pipeline0/vorbisdec0: failed to negotiate (try_set_caps with "audio/x-raw-float, rate=(int)11024, channels=(int)2, endianness=(int)1234, width=(int)32, buffer-frames=(int)0" returned REFUSED) ERROR (0x831d918 - 307744:21:37.151572000) scheduler( 6591) gstoptimalscheduler.c(2797):gst_opt_scheduler_iterate:<GstOptScheduler@0x83e3a50> in error state Execution ended after 22 iterations (sum 746033000 ns, average 33910590 ns, min 36000 ns, max 605213000 ns). [cschalle@cschalle temp]$ Steps to reproduce: Ronald could reproduce this so just filing for tracking purposes. Actual results: Expected results: Does this happen every time? Other information:
I think http://bugs.debian.org/302227 is the same bug, but I can't tell for sure. The reporter provided the following error message: ERROR: from element /pipeline0/spider0/vorbisdec0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2563): 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)4321, width=(int)32, buffer-frames=(int)0" returned REFUSED) Could someone tell me if we're probably talking of the same bug? Thanks!
Christian, could you try with "alsasink device=hw:0"?
Loïc, could you file a new bug about that issue? Thanks. Christian, where is that file? Do you still have problems in 0.9?
Wingo, I think this won't be needed: I confirmed with the Debian submitter that adding "alsasink device=hw:0" solves the problem, hence my question to Christian. There already a lot of dupes in the GStreamer BTS on the ALSA issue sadly.
Don't have the file anymore. Closing as fixed.
http://listen.fm4.amd.co.at:31337/fm4-mq.ogg is still accesible if that matters, and plays fine with playbin here. I presume the problem was on alsasink's side rather than on the played file.