* both x264 and x265 take less time to encode and the produce smaller files (lossless compression)
* AV1 takes 160x-190x more time than x264 (lossless compression)
* AV1 can't take advantage of multi-threading the same way x264 and x265 can. Neither for encoding nor for decoding.
* AV1 requires 3.5x-6x more CPU power to decode than x264
I just fail to see how AV1 is "all around better". Can you share another link? Maybe this time more specific so I can read the data you used to get to that conclusion.
Dav1d is an AV1 decoder which takes advantage of multi-threading:
https://code.videolan.org/videolan/dav1d
https://medium.com/@ewoutterhoeven/dav1d-0-1-0-release-the-f...
BitMovin and Intel both have AV1 encoders which can take advantage of multiple cores. BitMovin demonstrated live AV1 video almost two years ago:
https://bitmovin.com/bitmovin-supports-av1-encoding-vod-live...
https://bitmovin.com/constantly-evolving-video-landscape-dis...
That said, I have no idea whatsoever about video codecs; I'm just saying what I understood from the link I was provided with.
Also, do bear in mind that the primary use-case here is for Youtube to cut down their bandwidth consumption, and other similar users who don't mind doing a one-time encode that either takes a while, or needs to be run with process-level parallelism (different files at the same time). Multi-threaded encoders are not really a primary design goal here.
The format is practically worthless until there is a hardware decoder for it, nobody will software-decode AV1 on their smartphones or laptops. Nobody is going to design a hardware encoder until the standard stabilizes. Google can do all the Youtube encodes they want but they are going to have to keep developing and serving H264 for a long, long time.
Dav1d (https://code.videolan.org/videolan/dav1d) runs fine on my laptop for 1080p AV1 decoding. Your mileage may vary.
> Nobody is going to design a hardware encoder until the standard stabilizes.
NGCodec will release a hardware encoder this year. They use FPGAs for their encoders. Twitch uses NGCodec for their live VP9 streaming:
https://ngcodec.com/news/2019/1/7/ngcodec-announces-av1-supp...
https://blog.twitch.tv/how-does-vp9-deliver-value-for-twitch...
"On 25 June 2018, a validated version 1.0.0 of the specification was released. On 8 January 2019 a validated version 1.0.0 with Errata 1 of the specification was released."
If it's more familiar, think of it as similar to saying that the x86 or ARM instruction set has been finalized: the first generation will work but over time every component will be optimized to improve certain areas and there will be tailored versions for specific applications (e.g. video codecs used in chat have hard latency requirements while Netflix can afford a LOT of optimization time for a file which will be streamed a billion times).