Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I hope it's just not gonna be another VP9 where Google flips the switch to save some bucks on bandwidth but there not being any dedicated decode hardware in the wild yet, meaning everyone's battery gets nuked.


The problem is it has to be that way because nobody includes hardware decoders until major players are using the codec, so it's chicken and egg.

In theory the hardware vendors could notice that Google is developing a new codec which they could be reasonably expected to start using and then include hardware decoders in their devices before Google starts using it, but they don't really have the right incentives to do that. "Our device has a hardware decoder for a codec nobody is using" isn't really something customers buy phones based on. Meanwhile if the vendor doesn't put it in this year's model then they get to sell you a new phone with a hardware decoder next year after Google flips the switch and your battery life tanks until you buy the new phone.


But VP9 decoder is supported by almost every SoC now (Phones, tablets, TV, Set-top boxes, etc).

And TV/STB SoC vendors like Amlogic, Broadcom or Realtek already announced products with AV1 support.


It absolutely will. They’ve already started experimenting with that.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: