HandBrake

With H.264 I can see almost constant 2200-2300% CPU usage against 1200-1500% when encoding in H.265. I agree that H.264 is the most reasonable choice for most users in the near future, but if you wind up encoding with x265 again on your current CPU, I recommend adding the "pmode" flag. If...

While looking through the default settings, I noticed a couple of things that seemed odd in terms of AVC as a codec, not just Quicksync itself. Keyint : MSDK defaults this to 1 sec. Meanwhile, both x264 and x265 defaults keyint to 10s. Even Youtube only forces an I frame every 5 seconds nowadays. Un...

Thanks for the slides. Slide 12 is especially interesting because it comes so close to being real, useful information. It's strange that they chose to give PSNR decibels, instead of filesize percentages, as a measurement. It's grudgingly acceptable if they only focused on a single bitrate or QP, but...

Your source conveniently omits the x264 settings used. Slow x264 down to the speed of HEVC and see how it compares. Both of those links are mine. Sorry that the first doesn't include in-depth settings; it was originally made to be linked through another post (that already had settings). You'll find...

With 1080p material, x264 should range from 40% of ffmpeg's mpeg2video size (at ~CRF30) to 50% of its size (CRF20). You're comparing x264 with ffmpeg MPEG-2 source? Who does that? How could one even tell a difference using that source? Misunderstanding here: Raw i420 sources (combination of Derf an...

h265 is an unknown quantity, but any claims of a 50% file size reduction over h264 are to be held highly suspect. There's really no reason to think of HEVC as an unknown quantity. The reference encoder is slow, but you'll find that it performs quite well and can at least go toe to toe with x264 at ...