Of course AV1 requires high processing power because there are still no hardware decoders or encoders for it. Surprisingly, the first SoC with hw decode support for AV1 is mediateks recently announced flagship soc dimensity 1000.I checked some sources about this AV1 codec it's having heavy usage of processing power during encoding and decoding, much higher than h.265. With almost 30% better compression.
Even h. 264 has royalties as far as I have read (maybe I'm wrong).
I really wish h265 is open codec.
Cuz Google had to go through lot of work around to make it get around h 265 codec without having INFRINGEMENT With the same . I guess the codec is developed (not sure) but might be waiting for people to have much more better chip for encoding and decoding purpose.
VP9 also has/had the same problem with (for example) all laptops with Intel Skylake (6th gen) and older chips which do not support hw decode for VP9. This causes high CPU usage while playing YouTube as the decoding is not offloaded to fixed function decoder. This in turn causes battery drain and heating on these older devices but Google does not seem to be bothered. You can actually force h264 playback on YouTube for smoother playback on older devices using h264ify extension but that results in the stream being limited to 1080p, has lower quality to VP9 equivalent, and uses more bandwidth.
Edit: sorry for off topic. No more.
Last edited: