Kudos to the AOM engineering team for accelerating results to this degree. I’ll have full BD-Rate stats in the Streaming Media article. So, on this system, the version of FFmpeg supplied by the OTT shop contact took only about twice as long to encode the file as x265, and delivered a file higher in quality by about 2 VMAF points.
Here are the results, encoding strings are below. So, you can’t compare any of these encoding times with previous articles.
at the top, and an Information section below on how to use it.”īecause my Z840 workstation was busy and because I wanted to test all encodes on a single CPU system, I ran all encodes on a Telestream Gear 2 system equipped with a 6-core (12 with HTT) system configured as shown below. To get started, read the main readme page on the code repo. It completely automates the entire process. “ Media Autobuild Suite is a very handy tool for compiling popular open source media processing tools like ffmpeg on Windows. Here’s what he said about how he compiled the version. Since then, a video engineer from a large OTT shop forwarded me a version of FFmpeg for testing. Yesterday I reported that the Alliance for Open Media’s aomenc encoder was 70% faster than a version of FFmpeg downloaded from Zeranoe (all tests on Windows). Thanks for all the help I got from multiple sources, including Google, Visionular, Intel, Sébastien Faure, and others who wish to remain nameless, for improving the accuracy of my recent AV1-related research, which will appear in a future article in Streaming Media Magazine. Congrats to AOM for delivering on their promise to get encoding times down. With a properly compiled version of FFmpeg, encoding performance is slightly faster than the Alliance for Open Media’s encoder, though output quality is very slightly lower. AV1 encoding on Windows is now only 2x slower than x265.
0 kommentar(er)
