GNOME Bugzilla – Bug 583905
[mpegtsmux] issue with file creatd by qtdemux ! h264parse ! mpegtsmux
Last modified: 2010-04-06 20:29:34 UTC
The following pipeline remuxes a file with h264 video. It goes without error and totem do play the output. However the ffmpeg error spew only appears on the console if I remux into mpegts. If I use qtmux I do not get this [cschalle@crazyhorse Videos]$ totem h264.mov [cschalle@crazyhorse Videos]$ gst-launch-0.10 filesrc location=h264.mov ! qtdemux ! h264parse ! mpegtsmux ! filesink location=h264remuxed.ts Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock Got EOS from object "/GstPipeline:pipeline0". Execution ended after 1662543563 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ... [cschalle@crazyhorse Videos]$ totem h264remuxed.ts 0:00:01.198804317 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198890571 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198910126 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198927098 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198943720 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198959853 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198978501 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.198994565 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.199010279 18976 0x9d026c0 ERROR ffmpeg :0:: number of reference frames exceeds max (probably corrupt input), discarding one 0:00:01.199632006 18976 0x9d026c0 ERROR ffmpeg :0:: cabac_init_idc overflow 0:00:01.199657987 18976 0x9d026c0 ERROR ffmpeg :0:: decode_slice_header error [cschalle@crazyhorse Videos]$ totem h264.mov [cschalle@crazyhorse Videos]$ gst-launch-0.10 filesrc location=h264.mov ! qtdemux ! h264parse ! qtmux ! filesink location=h264remuxed.mov Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock Got EOS from object "/GstPipeline:pipeline0". Execution ended after 462127937 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...
I couldn't reproduce it. Can you still reproduce it with your h264 file? If it happens with your file, can you upload it so I can test? I generated mine with: "gst-launch v4l2src num-buffers=100 ! x264enc ! qtmux ! filesink location=h264.mov" I'm using git versions of gstreamer and plugins.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!