[gstreamer-bugs] [Bug 583905] New: Possible bug in mpegtsmux

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=583905

  GStreamer | gst-plugins-bad | Ver: 0.10.22
           Summary: Possible bug in mpegtsmux
           Product: GStreamer
           Version: 0.10.22
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: Uraeus at linuxrising.org
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: oxcsnicho at gmail.com
     GNOME version: Unspecified
   GNOME milestone: Unspecified


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 at crazyhorse Videos]$ totem h264.mov 
[cschalle at 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 at 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 at crazyhorse Videos]$ totem h264.mov 
[cschalle at 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 ...


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=583905.