[FFmpeg-trac] #2918(undetermined:new): Transmuxing Facebook MP4s creates bad mpeg-ts stream

FFmpeg trac at avcodec.org
Fri Aug 30 17:19:00 CEST 2013

#2918: Transmuxing Facebook MP4s creates bad mpeg-ts stream
             Reporter:  nealzebub    |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
 '''OS:''' CentOS 6.3 64-bit
 '''Build:''' N-55797-g535d9a9
 '''Obtained from:'''  http://ffmpeg.gusari.org/static/64bit/

 Summary of the bug:
 Attempting to transmux an MP4 file downloaded from Facebook to mpeg-ts or
 HLS stream results in an an invalid stream.  By invalid, I mean an mpeg-ts
 file or pipe stream is produced that FFmpeg itself cannot use.  From my
 brief analysis, the problem looks to be redundant PPS, one for each key-
 frame, a few packets prior to the one that belongs.

 How to reproduce:
 The command I really want to use:
 ffmpeg -i transmuxme.mp4 -sn -codec copy -bsf:v h264_mp4toannexb -f mpegts
 pipe:1 | ffmpeg -f mpegts -i pipe:0 -codec copy -map 0 -f ssegment
 -segment_format mpegts -initial_offset 10 segmentName_%04d.ts

 Commands that I used to make things simpler:
 Go from MP4 to MPEG-TS file
 ffmpeg -i transmuxme.mp4 -sn -codec copy -bsf:v h264_mp4toannexb -f mpegts

 Read-in the TS file just created to segment(receive errors reading the
 ffmpeg -i mp4tots.ts -map 0 -sn -codec copy -bsf:v h264_mp4toannexb -f
 ssegment -segment_format mpegts -initial_offset 10 segmentName_%04d.ts

 The full console output are attached, as I used "-report".  They are quite
 lengthy to put in-line here.

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2918>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list