[FFmpeg-trac] #912(avformat:new): mpegts muxer does not follow TS buffering requirements specified in iso13818-1 section 2.4.2.3

[FFmpeg]

#912: mpegts muxer does not follow TS buffering requirements specified in
iso13818-1 section 2.4.2.3
----------------------------------+---------------------------------------
             Reporter:  jenf      |                     Type:  defect
               Status:  new       |                 Priority:  normal
            Component:  avformat  |                  Version:  unspecified
             Keywords:            |               Blocked By:
             Blocking:            |  Reproduced by developer:  0
Analyzed by developer:  0         |
----------------------------------+---------------------------------------
 The mpegts muxer in ffmpeg (tested with 0.9.1) does not respect the 512
 byte transport buffer for each pid as described in iso13818-1 section
 2.4.2.3.

 Streams created with ffmpeg (with the muxrate option) have been seen to
 send over 100 packets in sequence (at least on video data) which exceeds
 the maximum buffer extraction rate for streams in the Main Level (as
 defined in iso13818-2 table 8-13). The same also applies to audio packets,
 albeit with different limits.

 For any stream >18mbit/sec the maximum number of packets for a PID that
 can be inserted in sequence is 2 or 3 (assuming an empty buffer prior to
 insertion).

 This can cause errors in decoding the ts on certain hardware.
 The packets should therefore be ordered appropriately in the stream to
 comply with the TS buffer limit of 512 bytes when the muxrate parameter is
 specified.

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