8 ms·
Vastly used? I'm not so sure about that. Vastly used in tandem with H264 when required? Absolutely. If iOS can hardware decode H264 but not WebM it actually is
by untog 9y ago
Vastly used? I'm not so sure about that. Vastly used in tandem with H264 when required? Absolutely.
If iOS can hardware decode H264 but not WebM it actually isn't in the user's interest to support WebM, because it'll reduce incentive to provide H264 versions of content, which means iOS users will experience battery drain faster.
It might not be particularly fair, but it does make sense.
- wlesieutre 9y agoNative apps like VLC can play WebM on iOS with software decoding, but as you say it murders the battery. If Apple supported that in browsers I'd bet that Google or other companies would switch their video hosting over, much to the detriment of anyone who watches videos on an iPhone. It's an open standard so clearly they're doing the pro-consumer good thing!
- gsich 9y agoIt would give an incentive to Apple to support hardware decoding.
- acdha 9y agoAgain, who benefits from this? You’re talking about duplicating a ton of work simply to have approximately the same quality. You can contrast this with AV1 which is also a lot of work but which delivers better quality at smaller sizes. It’s not surprising that they picked that option instead.
- gsich 9y agoEveryone.
- acdha 9y agoYou mean “me”. This is not a mainstream issue which normal people care about: they use a browser or app, click play, and it works. Very few people care about what format that uses.
- gsich 9y agoYes. So because few people are about it, it's irrelevant? I don't think so. Most people also don't care how their device works, or basically anything that's not their area of expertise. Are all those irrelevant too?
- acdha 9y agoYour problem is treating this as an emotional exercise in team loyalty rather than an engineering problem. Even Apple has finite resources so it’s unlikely that they’re going to spend time on something which duplicates but does not improve existing functionality. The number of people with a large collection of videos which are only available in VP8 just isn’t large enough to justify the investment.
- clouddrover 9y ago"Normal" people also don't care about TCP\IP or HTTP or HTML or image formats or any of the detail that makes the web or the internet generally work. It's a pointless argument. "Normal" people do care about their videos starting fast with high image quality. AV1 will deliver them that and deliver it better than H.264 has done. This is true whether they know it or not, whether they care about it or not.
- simonh 9y agoThat's pure misdirection. If Apple didn't support HTTP iPhones would not be able to use the web at all. If Apple doesn't support VP8 nobody notices a thing. Of course faster load times are nice, they will come, but whether it's through VP8, HEVC, VP1, or something else will take time to shake out. Meanwhile somebody on HN will moan about Apple's monopolistic user hostile refusal to support every single blasted codec released ever. Good grief, there are even people who still think Apple should have supported Flash, and therefore presumably still support it because the world today would be so much better if Flash was still widely used, or something.
- clouddrover 9y ago
- pwinnski 9y agoApple does support hardware decoding, just not of webm.
- gsich 9y agoYes, vastly used. Just look at Youtube. Besides it's a free codec. How do you know what's in the users interest? A choice between "Video playing" vs. "Video not playing" is pretty obvious to me. (And I am a user too) If battery really is a concern (assuming it is), just make it an option not to play videos if they require software decoding. Besides that, users usually (an assumption I made, just as you did) don't watch lengthy videos (1-2 hours) on an iOS device.
- Terretta 9y agoYouTube is not ‘vastly’. Get back to us when it’s ‘vast’ among commercial content providers. Contrary to your point about not watching on iOS, I, and everyone I know, watch all content on an iOS device, both in the living room and on the go. There is certainly a segment of the market that is using misc devices or “casting” to USB sticks plugged into TVs, but the 4K TV owning cord cutters I know tend to also own iPhones and use Apple TVs. We saw this shift happen even more when iOS (and TvOS) gained SSO across apps with the “TV” app as indexer, and another bump when Amazon Prime released.
- gsich 9y agoWhy not? Just go by traffic. Youtube default to VP9 on Chrome, so yes it is vastly used. Netflix can't even display 4K on the desktop properly. If you watch in the living room (on TV) you are not watching it on the iOS device. By that I mean the screen of the iOS device. Being in the living room, watching on TV, means you have no battery issue. Watching on your device means literally that, watching it on your device with your devices' screen. Not some casting or streaming to other displays.
- MBCook 9y agoSo what you’re saying is since Google has manipulated the environment so that Google’s preferred codec is the most used on Google‘s website, which happens to be the largest video site on the Internet… that means Google’s codec is better. If we ignore YouTube, which Google controls to their own benefit, what’s the percentage of WebM/VP9 versus H264/H265?