GNOME Bugzilla – Bug 145059
ERROR: from element /pipeline0/mad0: Internal GStreamer error: pad problem.
Last modified: 2004-12-22 21:47:04 UTC
I use gstreamer 0.8.1 with alsa output (and alsa-lib 1.0.5) that works: gst-launch-0.8 filesrc location=/mnt/data/mp3/Track5.mp3 ! mad ! filesink location=a aplay -f dat a that doesnt: gst-launch-0.8 filesrc location=/mnt/data/mp3/Track5.mp3 ! mad ! alsasink device=hw:0 RUNNING pipeline ... ERROR: from element /pipeline0/mad0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2403): gst_pad_set_explicit_caps: /pipeline0/mad0: failed to negotiate (try_set_caps with "audio/x-raw-int, endianness=(int)1234, signed=(boolean)true, width=(int)16, depth=(int)16, rate=(int)44100, channels=(int)2" returned REFUSED) Execution ended after 1 iterations (sum 2523000 ns, average 2523000 ns, min 2523000 ns, max 2523000 ns). that doesnt work either: gst-launch-0.8 filesrc location=/mnt/data/mp3/Track5.mp3 ! mad ! alsasink RUNNING pipeline ... ERROR: pipeline doesn't want to play. and it doesnt play, no matter what I do... any ideas ?
This is a feature. ;). Add audioconvert/audioscale in between: gst-launch-0.8 filesrc location=/mnt/data/mp3/Track5.mp3 ! mad ! audioconvert ! audioscale ! alsasink
Ah ! Okay, it works when I use your command and add "device=hw:0". Thanks a lot :) If I dont add "device=hw:0" it doesnt work and muine doesnt work either (although that could be muine's fault... it just writes "killed" and dies ... hmm)... but any way to set the default alsa device for alsasink ? (not that I think thats the reason but hey....)
You can set a default device in your ~/.alsarc, see the ALSA documentation for details.
Yep, putting a .asoundrc into my homedir with the following worked (for archival purposes ;)): pcm.!default { type hw card 0 } ctl.!default { type hw card 0 } ----------done----- now it works without explicit device string, though with some weird warning ... but hey, it works ^^
Created attachment 29076 [details] warnings when running gst-launch, works though
updating 0.8.2 solved even that "issue"... great ^^ sorry for the spam
Yeah, that was a known bug somewhere else. Thanks for letting us know that it works now, I'll dup similar bug reports against this one.