4 ms·
HEVC and VP9 were released at around the same time, but today VP9 has twice the installed base of HEVC: https://ngcodec.com/news/2017/10/21/why-we-are-supporti
by clouddrover 9y ago
HEVC and VP9 were released at around the same time, but today VP9 has twice the installed base of HEVC:
https://ngcodec.com/news/2017/10/21/why-we-are-supporting-vp9-and-av1 https://ngcodec.com/news/2017/10/21/why-we-are-supporting-vp...
The simplicity of VP9's licensing versus the complexity HEVC's licensing probably has a lot to do with that.
- revelation 9y agoEhh, this is counting 1.7 billion mobile users for VP9 but not HEVC because of mobile Chrome installs. It's hard to take this serious when it's counting software decoding on mobile (if Chrome will even decode it on a lot of those phones, they know its pointless in SW.) Meanwhile, nothing iOS supports VP9 HW decode. Until they come around, people could give a fuck about installed base. Then there is the stuff this article doesn't very well measure. Like DVB-T2 in Germany using 1080p50 10 bit HEVC. That is expected to be around for a decade or more. That is a whole lot of TV settop boxes.
- vetinari 9y agoVP9 support is mandatory in Android. If you want to ship Play Store, that is. So it is not due to mobile Chrome installs. The amount of Android devices dwarfs iOS devices and Apple knows that it is not viable position in long term. That's why they joined AV1. People in near future would not give a fuck about the Apple, if they couldn't play their Youtube or Netflix videos in 4K on them.