GNOME Bugzilla – Bug 154811
cannot play mpeg1 files using gst-launch
Last modified: 2004-12-22 21:47:04 UTC
Any mpeg1 file doesn't play when using gst-launch-0.8. I can hear the audio, but the video thread doesn't work. I can see the video only if I remove the threads. I'm running gstreamer-0.8.7 and gst-plugins-0.8.5. Here's the log: gst-launch-0.8 filesrc location="toca.mpg" ! mpegdemux name=demux ! { queue ! mpeg2dec ! sdlvideosink } { demux. ! queue ! mad ! audioscale ! osssink } WARNING: erroneous pipeline: could not link queue0 to mpeg2dec0 Trying to run anyway. RUNNING pipeline ... (process:13075): GStreamer-WARNING **: Unhandled state change from PLAYING to READY ** (process:13075): WARNING **: invalid state change 2050 for element thread1 (process:13075): GStreamer-WARNING **: thread1: state change in callback 2 8 Caught interrupt. Execution ended after 20355 iterations (sum 196041324000 ns, average 9631113 ns, min 27000 ns, max 470689000 ns).
There seems to be more than one problem here. First, the queue from the video thread gets connected to the mpegparse:src instead of mpegdemux:video_00. If I comment out the code to create a source pad in mpegparse.c, the video plays correctly. I can also specify the video_00 pad myself on command-line but this isn't practical because if there's no video stream, the pipeline gets stuck at the end. Second, there seem to be some kind of threading problem when I run the pipeline: gst-launch-0.8 filesrc location="ferrari_456.mpg" ! mpegdemux name=demux ! { queue ! mpeg2dec ! sdlvideosink } { demux. ! queue ! mad ! esdsink } RUNNING pipeline ... (process:26362): GStreamer-WARNING **: Unhandled state change from PLAYING to READY (process:26362): GStreamer-WARNING **: Unhandled state change from PLAYING to READY I'm running gstreamer-0.8.7 (with gstthread.c from CVS) and gst-plugins-0.8.5
The 'src' pad was removed some time ago. This should no longer occur (I think this was fixed in 0.8.5 already, else it's definately fixed in 0.8.6). The warnings are not something to worry about now, they seem harmless, although I don't know what causes them... Open a separate bug for them if you wish.