7 ms·
The VP9 decoder installed base is about double HEVC's: https://ngcodec.com/news/2017/10/21/why-we-are-supporting-vp9-and-av1 https://ngcodec.com/news/2017/10/2
by clouddrover 9y ago
The VP9 decoder installed base is about double HEVC's:
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...
So to me that bodes well for future AV1 support in all kinds of devices.
- scarface74 9y agoIt doesn't matter. No one is going to support a video format that's not compatible with iOS. Adobe effectively lost the war with Flash on mobile the day that Apple decided not to support it. Even though it was available for Android.
- clouddrover 9y agoBoth YouTube and Netflix support VP9: https://medium.com/netflix-techblog/more-efficient-mobile-encodes-for-netflix-downloads-625d7b082909 https://medium.com/netflix-techblog/more-efficient-mobile-en... And YouTube doesn't do 4K encoding in H.264 anymore. If you want 4K video from YouTube you need VP9 support (or AV1 when YouTube starts AV1 encodes): http://appleinsider.com/articles/17/09/21/apple-tv-4k-wont-play-4k-youtube-videos-because-of-missing-google-codec http://appleinsider.com/articles/17/09/21/apple-tv-4k-wont-p...
- scarface74 9y agoThe subject of the article was the "fight for patent-unencumbered media codecs is almost won". To "win" that fight means that content providers can abandon patent protected formats. Netflix is still having to deal with patents and now they had to dedicate more resources to support an additional format. Large content providers like YouTube or Netflix really don't care about the patent and have the resources for storage and encoding multiple formats. Where patents hurt are smaller entrants that would benefit from patent free formats. They still have to support patented formats and now they have to spend money on encoding and storage on yet another codec if the want to use VP9. What's the benefit of supporting two formats? One that is supported everywhere and one that isn't it?
- clouddrover 9y ago> To "win" that fight means that content providers can abandon patent protected formats. And that's what's happening. VP9 is royalty-free and AV1 will be royalty-free. > Where patents hurt are smaller entrants that would benefit from patent free formats. So it's good that both YouTube and Netflix support VP9 and AV1. It helps make royalty-free video formats commonplace on the web. > What's the benefit of supporting two formats? It's worth it for the bandwidth saving. VP9 significantly outperforms H.264.
- scarface74 9y agoAnd that's what's happening. VP9 is royalty-free and AV1 will be royalty-free Who are these content providers that are "abandoning" H.264? so it's good that both Netflix and YouTube support VP9 and Av1 Good for who? End users don't care if content is encoded in a patent free format. They just care about the content being available on their platform.
- clouddrover 9y ago> End users don't care if content is encoded in a patent free format. This is a tired argument. The same argument was attempted when VP8 was new, and when VP9 was new, and now again with AV1. I'm sure the same, worn-out ground will be revisited when AV2 comes along. End users don't care that TCP\IP is royalty-free or that HTTP and HTML are royalty-free or that any of the other commonly used formats and protocols are royalty-free. They don't care because they don't understand the issues. Developers care. Builders care. I care. I want to implement video on the internet for any use case without having to consult a lawyer just to understand the licensing implications of doing so. VP9 and AV1 make that possible. VP9 and AV1 normalize video on the internet by making it royalty-free like all the other internet formats and protocols. Content companies and hardware companies and software companies don't join AOMedia for the fun of it. They join because it's the practical choice: http://aomedia.org/about-us/ http://aomedia.org/about-us/
- notyourday 9y ago
- mapmap 9y agoGoogle chrome plays 4k YouTube videos on the Mac but Safari does not. Is there a reason that Google cannot ship the VP9 codec with their Apple TV app? Or is the Apple TV 4K hardware unable to accommodate VP9 and will never support it?
- deleted 9y ago[deleted]
- phkahler 9y ago>> No one is going to support a video format that's not compatible with iOS. You might try reading the article next time. Apple recently joined the Alliance for Open Media. That indicates to me that they are likely to support AV1. Apple was really the last holdout and it would be poor business for them not to play.
- scarface74 9y agoHow does Apple joining the alliance negate the sentence that market share doesn't matter if a format is not compatible with iOS? My contention wasn't that Apple wouldn't support VP9, it was that if Apple didn't support VP9, it's not likely that content developers would leave iOS users out in the cold.
- vetinari 9y agoiOS users are welcome to purchase devices that have proper support for standards at their next refresh cycle.
- scarface74 9y agoHow did that workout for Adobe with Flash?
- 0xCMP 9y agoMost users did not want flash. Most users don't want web apps or apps inside web views, but they'll use those if they have to. Why switch phones to get flash if you really wanted a native experience in the first place?
- scarface74 9y ago"Most users didn't want Flash". That's a lot of revisionist history. Apple was being knocked for not supporting Flash from the time the first iPhone was released in 2007 until a year or two after the iPad was released in 2010.
- Animats 9y agoApple just signed up for AV1.[1] [1] https://www.cnet.com/news/apple-online-video-compression-av1/ https://www.cnet.com/news/apple-online-video-compression-av1...
- mtgx 9y agoYes, it matters. Apple joined AOM, which means it will kill HEVC in the same way it killed Flash. Once the HEVC-only devices are out of the market, Apple will say it will drop support for HEVC.
- digi_owl 9y agoIndeed. We witnessed ethis with H264, where even the likes of Nokia (before they sold the phone business to Microsoft and later licensed off the brand) leaned in on not having webm be part of the HTML video standard. This because they had a bunch of devices out there that could do H264 in hardware, but had to do webm in software, and thus playing the latter format would take a greater toll on the battery. And even if every damn device use a programmable DSP these days, the problem is not solved. Because only the OEM can be expected to provide the firmware needed for new formats. Effectively the only way to win this would be for GPLv3 or similar to be made law, so that consumer devices are not beholden to OEMs for maintenance.
- dv_dt 9y agoI think you really have to look at installed or planned hardware decoders, or closely coupled software/GPU decoders to really declare victory. Edit: software/GPU decoders, not hardware/GPU decoders.