GNOME Bugzilla – Bug 140411
mp3 not identified/working properly with gstreamer 0.8
Last modified: 2004-12-22 21:47:04 UTC
Since upgrading to 0.8.0 gstreamer, 25% of my mp3s don't play anymore, and rhythmbox doesn't "identify" them when searching for them anymore. I'm assuming its all a similar problem, Here is an example of gst-launch with one of the songs: swat@tomsk:~$ gst-launch-0.8 filesrc location=buggered\ mp3s/Funnies\ -\ Doh.mp3 ! spider ! osssink RUNNING pipeline ... ERROR: from element /pipeline0/spider0/wavparse0: Internal GStreamer error: pad problem. File a bug. Additional debug info: gstpad.c(2392): gst_pad_set_explicit_caps: /pipeline0/spider0/wavparse0: failed to negotiate (try_set_caps returned REFUSED) Execution ended after 2 iterations (sum 8432000 ns, average 4216000 ns, min 4093000 ns, max 4339000 ns). swat@tomsk:~$ The MP3 is available at http://swat.me.uk/bugdemo.mp3 Also on a side note, the broken songs appears with MP3 icons, in nautilus, until you select them, when that icon changes to WAV.
the problem is that your mp3 files are inside a riff/wav file. apoc@apoc test $ file bugdemo.mp3 bugdemo.mp3: RIFF (little-endian) data, WAVE audio, MPEG Layer 3, stereo 44100 Hz If you extract the mp3 data with this command line, you'll get a *clean* mp3 file that will work with rhythmbox : gst-launch-0.8 filesrc location=bugdemo.mp3 ! wavparse ! filesink location=clean.mp3 apoc@apoc test $ file clean.mp3 clean.mp3: MP3, 96 kBits, 44.1 kHz, JStereo Anyway, the problem should be resolved. I get this error from rhythmbox : Probably a caps problem ERROR GST_PADS(21947) gstpad.c(2426):gst_pad_set_explicit_caps:<wavparse0> (null) ERROR GST_PADS(21947) gstpad.c(2426):gst_pad_set_explicit_caps:<wavparse0> failed to negotiate (try_set_caps with "audio/mpeg, mpegversion=(int)1, layer=(int)3, rate=(int)44100, channels=(int)2" returned REFUSED) ERROR scheduler(21947) gstoptimalscheduler.c(2298):gst_opt_scheduler_iterate:<GstOptScheduler@0x8136958> in error state
This worked fine in gstreamer 0.6.x. Does this mean that I have to figure out a way to "clean" all my mp3s? I would imagine a great number of people would have similar problems with their mp3s - are there any plans to include a workaround for this?
Spider doesn't like it. A workaround would be to make the pad in wavparse a request pad, then it'd work fine.
Ok... I'm not all that clued up on this. Where do we go next with this?
Give me a few days to work on it... ;).
Fixed in CVS.
Excellent stuff, thanks!