After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712577 - Mpeg2 playback regression
Mpeg2 playback regression
Status: RESOLVED DUPLICATE of bug 710615
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.2.1
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-11-18 11:36 UTC by Eric
Modified: 2013-11-18 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Eric 2013-11-18 11:36:58 UTC
Hi,

there seems to be a regression on the playback of mpeg2 file.

Since 1.2.0, I have a mpeg2 file that doesn't play to end anymore;It stops after about 20s with the following message:

etrousset@etrousset-Vostro-420-Series ~/source_ext/gst-1.2.1/build_debug/bin $ ./gst-launch-1.0 playbin uri=file:///home/etrousset/source_ext/gst-1.2.1/build_debug/bin/122.mpeg 

(gst-plugin-scanner:5622): GStreamer-WARNING **: Failed to load plugin '/home/etrousset/source_ext/gst-1.2.1/build_debug/lib/gstreamer-1.0/libgstdfbvideosink.so': libdirectfb-1.7.so.0: cannot open shared object file: No such file or directory
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...

(gst-launch-1.0:5621): GStreamer-WARNING **: gstpad.c:4506:store_sticky_event:<dvdlpcmdec0:src> Sticky event misordering, got 'segment' before 'caps'

(gst-launch-1.0:5621): GStreamer-WARNING **: gstpad.c:4506:store_sticky_event:<'':decodepad2> Sticky event misordering, got 'segment' before 'caps'

(gst-launch-1.0:5621): GStreamer-WARNING **: gstpad.c:4506:store_sticky_event:<decodepad2:proxypad3> Sticky event misordering, got 'segment' before 'caps'
Redistribute latency...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstAudioSinkClock

** (gst-launch-1.0:5621): CRITICAL **: gst_video_decoder_allocate_output_frame: assertion `frame->output_buffer == NULL' failed
ERROR: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstMpegPSDemux:mpegpsdemux0: Internal data stream error.
Additional debug info:
gstmpegdemux.c(2937): gst_flups_demux_loop (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstMpegPSDemux:mpegpsdemux0:
stream stopped, reason error
Execution ended after 0:00:20.006220559
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Cheers, 
Eric T
Comment 1 Tim-Philipp Müller 2013-11-18 11:48:47 UTC
Thanks for the bug report.

This might be fixed by this commit in master (which will probably be cherry-picked into 1.2 for the next release):

 commit 8c1be8796e58bfcab7c9b9ac2ca089b10bf803b4
 Author: Mark Nauwelaerts <mnauw@users.sourceforge.net>
 Date:   Mon Nov 11 13:15:54 2013 +0100

    mpeg2dec: graceful degradation for badly parsed input

See bug #710615

Any chance you could try it? (there were also some fixes for the parsers in -bad which might also help)
Comment 2 Eric 2013-11-18 13:38:51 UTC
Yes, it seems to be au duplication of the bug you mentioned, merging mpeg2dec with the master seems to fix the issue.

Thx,
Eric

*** This bug has been marked as a duplicate of bug 710615 ***