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

FFmpeg trac at avcodec.org
Sun Jul 24 22:28:59 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 Sesse):

 It's all about where you want to allocate your CPU power. One one of the
 machines I run this on, the mixing process takes up literally all my CPU,
 so there's simply none left for x264 (maybe 10% of one 800 MHz core); it
 has to go to Quick Sync or else I would simply get no stream. :-) In the
 case of the 4x3.6 GHz Haswell, any CPU I don't use will go into making the
 5 Mbit stream better; I could of course try to spend a core or so on
 running with low CRF on ultrafast, but that means one core less for the
 “real” stream that users will see.

 Of course, x264 is much better quality-wise (bit-for-bit) than any
 hardware encoder I've ever seen. I'm not sure if I understand your
 question, though; do you ask if it produces a smaller bitstream at e.g.
 medium preset (I would be surprised if it didn't), or just if it produces
 a valid one at all?

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

More information about the FFmpeg-trac mailing list