GNOME Bugzilla – Bug 163891
Gst-launch-ext will not play an MPEG video
Last modified: 2005-01-19 21:24:24 UTC
Please describe the problem: Gst-launch will not play a specific MPEG video. Totem/gstreamer plays the video fine. gstreamer-0.8.8-2 gstreamer-plugins-0.8.7-2 "file Washington_zoom_in.mpeg" says: Washington_zoom_in.mpeg: MPEG sequence, CIF NTSC, NTSC 4:3, 29.97 fps, Constrained Steps to reproduce: Execute "gst-launch-ext-0.8 Washington_zoom_in.mpeg" to play the attached media file. Actual results: Gst-launch says: Running command-line gst-launch-0.8 filesrc location="Washington_zoom_in.mpeg" ! mpegdemux name=d { d.audio_00 ! queue ! mad ! audioconvert ! audioscale ! osssink } { d.video_00 ! queue ! mpeg2dec ! ffmpegcolorspace ! xvimagesink } RUNNING pipeline ... But a window never appears. Sending an interrupt causes: Caught interrupt. Execution ended after 79225 iterations (sum 168982701000 ns, average 2132946 ns, min 483000 ns, max 8353359000 ns). Expected results: A window should appear, displaying the video. Does this happen every time? Yes. Other information:
The file Washington_zoom_in.mpeg is available at http://www.flyn.org/random/Washington_zoom_in.mpeg. It was too big to attach to this bug report.
Itś a sequence. Rename to .m1v and itĺl work. Additionally, try: gst-launch filesrc location=file.mpeg ! mpeg2dec ! xvimagesink
gst-launch-ext does a pipeline based on file extension (totem guesses from content, using typefinding) here, the file isn't a mpeg system stream, but a mpeg video elementary stream so, its correct extension should be m1v. that's why it can't work if sent thru mpegdemux.
gst-launch filesrc location="Washington_zoom_in.m1v" ! mpeg2dec ! xvimagesink works fine. But, gst-launch-ext still tries to use mpegdemux: Running command-line gst-launch-0.8 filesrc location="Washington_zoom_in.m1v" ! mpegdemux ! { queue ! mpeg2dec ! ffmpegcolorspace ! xvimagesink } WARNING: erroneous pipeline: could not link queue0 to mpeg2dec0 Trying to run anyway. RUNNING pipeline ... Gst-launch seems to assume a .m1v file is a system stream, not a video elementary stream.
Right, fixed. I assume I can close this now?
Confirmed fixed. Thank you.