GNOME Bugzilla – Bug 320114
GStreamer-WARNING **: pushing data on non-negotiated pad mad1:src, not allowed.
Last modified: 2006-01-13 11:44:20 UTC
Some of my mp3s (while the most others are ok) result in a lot the above warnings and an exit code of 255 for the command: gst-launch playbin uri=file:///mnt/.../additive.mp3 They play ok with: gst-launch-0.8 filesrc location=/mnt/../additive.mp3 ! spider ! audioscale ! audioconvert ! alsasink (or osssink) I am new to gstreamer. Can you please give me some pointers on how to further investigate the problem. I could upload such "corrupt" files where you suggest.
Can you test: gst-launch-0.8 filesrc location=/mnt/../additive.mp3 ! spider ! audioconvert ! audioscale ! alsasink and gst-launch-0.8 filesrc location=/mnt/../additive.mp3 ! decodebin ! audioconvert ! audioscale ! alsasink and gst-launch-0.8 gnomevfssrc location=/mnt/../additive.mp3 ! spider ! audioconvert ! audioscale ! alsasink ?
No warning (and sound output) with all of the three suggested commands.
The last one should have been: gst-launch-0.8 gnomevfssrc location=/mnt/../additive.mp3 ! decodebin ! audioconvert ! audioscale ! alsasink Can you try that also please?
No warning, sound output, i exit with ctrl-c.
I'd like to see the file then...
I uploaded the file to http://omnek.net/temp/additive.mp3
works fine here.. With "no warning, sound output" you are saying that there is sound output or not? (sorry for my poor english)
I have the same issue - some mp3 files are fine and some are bad (same error: GStreamer-WARNING **: pushing data on non-negotiated pad mad1:src, not allowed. then segfault) Playing the "bad" files with totem works (my totem is configured to use xine instead of gstreamer). I also have the problem with the additive.mp3 file provided by Dominic.
There is no sound output.
Internal discussion question: could this be because of the alsasink bug (samplerate-related)?
I too have this problem. I'm seeing it in both the file linked above and an mp3 I have. myers@soap:~/audio$ gst-launch-0.8 playbin uri=file:///home/myers/audio/additive.mp3 RUNNING pipeline ... (process:26200): GStreamer-WARNING **: pushing data on non-negotiated pad mad0:src, not allowed. (this repeats until you kill it) gst-launch-0.8 filesrc location=<badfile>.mp3 ! spider ! audioconvert ! audioscale ! alsasink (30 seconds of silence with 100% cpu, then 0% cpu and audio. audio begins with a distortion that is not heard when you playback via mpg321) gst-launch-0.8 filesrc location=<badfile>.mp3 ! decodebin ! audioconvert ! audioscale ! alsasink (3 seconds of silence with 100% cpu, then 0% cpu and audio. audio begins with a distortion that is not heard when you playback via mpg321) gst-launch-0.8 gnomevfssrc location=/mnt/../additive.mp3 ! decodebin ! audioconvert ! audioscale ! alsasink (same as last one) I also swapped out alsasink with osssink on the last one, same results, so I don't think the theory in comment #10 is correct.
Tried it with gst core 0.8.9 and 0.8.11 and gst mad plugin 0.8.8 and 0.8.11 (from debian packages)
There is also a bug report on Ubuntu's launchpad with some activity going on: https://launchpad.net/products/rhythmbox/+bug/3668
What's going on no this bug?
20 days without any activity ... is there some thing I/we can do to push a solution?
The unfortunate fact is that there are very few people doing any work at all on gstreamer 0.8 any more. All effort is going into the 0.9 series (due to be released as 0.10 in one week!). If you have any problems with 0.9 with any files, we'd like to hear about them, and we'll try to fix them. 0.9/0.10 will hopefully work much, much better for users in general, though there are still many things that haven't yet been ported to 0.9. If someone provides a patch for 0.8, it'll probably get committed, but it's unlikely that any of the core gstreamer hackers will be doing much work on this sort of thing. Sorry.
*** Bug 321391 has been marked as a duplicate of this bug. ***
Works for me in 0.10, marking fixed.