[FFmpeg-trac] #5732(avcodec:open): Display corruption on very high-bitrate H.264 files

FFmpeg trac at avcodec.org
Sun Jul 24 22:03:28 EEST 2016

#5732: Display corruption on very high-bitrate H.264 files
             Reporter:  Sesse       |                    Owner:
                 Type:  defect      |                   Status:  open
             Priority:  minor       |                Component:  avcodec
              Version:  git-master  |               Resolution:
             Keywords:  h264        |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  0           |

Comment (by cehoyos):

 Replying to [comment:13 Sesse]:
 > I ran your decode command-line. I couldn't really play out.nut in
 anything, it looks more like a still image to me. But I've uploaded it to
 http://storage.sesse.net/out.nut in case you can get something usable out
 of it.

 Works fine here with MPlayer and FFmpeg, thank you!

 > As for x264's performance on this clip, Nageru makes one in parallel to
 the QSV stream. (The QSV stream is meant for archival, the x264 stream is
 meant for direct consumption by clients.) At 5 Mbit/sec on a 4x3.6 GHz
 Haswell (we run with speedcontrol, which on this machine largely means
 hovering around somewhere between the equivalent of “slow” and “slower”
 presets), it was much better than the YouTube version
 (https://www.youtube.com/watch?v=-N5CLcSkkWs), but far from perfect. I
 would say x264 did a respectable job, but not a fantastic one.

 Am I correct that the h264 stream you uploaded is 25Mbit/sec?

 Just for reference: The input stream is decoded correctly by current
 FFmpeg as confirmed by the reference decoder, a specific bug workaround
 for the encoder would make sense.

Ticket URL: <https://trac.ffmpeg.org/ticket/5732#comment:14>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list