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.
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.
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-p...
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?
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.
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.
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:
Profit is in the users, not in the developers
The choice isn't AV1 or users. It's AV1 and users.
And I can't find how much licensing actual costs for H.264.
What does that have to do with patents and why people should care?
This is bad for users, whether they realize it or not. They end up with fewer (and potentially worse) options.
It doesn't really have an affect on small content producers. I do live streams for a non profit. We pay one time for Wirecast and the Black Magic hardware. Pay a neglible cost to send the livestream to our provider and they broadcast it. iOS users at least can view from the browser using HLS. We also send another stream to Facebook. How does H.264 patents affect us?
You don't have to "consult a lawyer", unless you are creating your own codec. You pay the licensing fee which in the grand scheme of things is lower than all of your other costs - hosting, development tools, internet costs, etc. and you're done.
[1] Which I wouldn't be so sure. Many H.264-using devices come with disclaimer, that they are not licensed for professional use and that you may need your own license. As usual, consult your lawyer. The point of VP9/AV1 is, that this is not necessary.
End users do care about the cost of their devices. Patent-free formats lower that cost. And patent encumbrances just make it more difficult and costly for manufacturers to include support; sometimes some formats get left out due to cost.
I certainly agree that end users don't care about patents, but they care about some of the practical problems that patent-encumbered formats cause down the line. These are usually not showstoppers, but they help cause customer confusion and sticker shock.
Having to support both formats in the short- or medium-term is definitely annoying and costly for manufacturers, but if we do actually win the open format war (I think the OP is a little overly optimistic there), that problem goes away.
You get a much wider and more loyal user base if you're smart enough not to enforce such silliness anymore.
I was working on networked audio/video devices back in ~2005 when that space was pretty new. We had a line-item BOM cost for encoder/decoder licenses that was not chump-change, which got passed on to customers.
I can only imagine costs have gotten much worse since then. When you take into account all the electronics your average connected person owns: phone, tablet, TV, AppleTV/GoogleTV/Roku, computer OS, etc., it really starts to add up.
Even if the parent poster is overstating and it's on the order of $50 per person, that's a ton of wasted money when you consider the total cost.
Consider all the electronics you've owned over the past 20-25 years. You undoubtedly paid a dollar or two for less complex ones and much more for more complex devices.
Eventually they will, the only missing piece for AV1 to become the de facto successor to h264 was Apple, with them onboard AV1 will cover all of web and mobile. I mean look at the companies behind AV1:
Google, Microsoft, Apple, Amazon, Netflix, Facebook, Mozilla, Cisco, Intel, AMD, ARM, IBM, NVidia, Broadcom, and that's about HALF the list.
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.
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.
Pushing open formats now means we develop a habit of only allowing open formats into industrial standards, which means in the medium and long term we all win with lower costs.
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.
[1] https://www.cnet.com/news/apple-online-video-compression-av1...
Edit: software/GPU decoders, not hardware/GPU decoders.
Now if only Apple would join Vulkan, too, so we can all agree on a cross-platform graphics API, too. Because of Apple Khronos now has to make a subset of Vulkan that will be cross-platform. This means that if developers end-up adopting that one over Metal on iOS, the situation will be worse off for everyone, including Apple.
Apple has gotten better with supporting standards from the Steve Jobs days, but I think it still has some way to go.
What does it cost to join as a governing member? Money? Apple has an unbelievably big pile of it. Spending it relieves their tax burden, so why not buy the most expensive level of membership?
Cynically, maybe they want to influence it so that it sucks, so while Apple does support it, Apple's going to have their own proprietary code, so Apple videos on Apple gear looks great. Everyone else gets the AOM code which, for some reason, everyone else's looks (and sounds) ever so slightly worse.
They could influence the codec so it works better on Apple hardware, so they get an advantage while designing the GPU that will go inside the iPhone XI or XII.
They could use this to see what the codec will support, and then decide not to support it out of spite, just like the iPhone X does't have USB-C, even though their laptop team has discovered that technology.
Point is, why knows? Yes, it is reasonable to think that Apple joining AOM means they'll put AOM codecs on their devices, but unless you work at Apple at the executive level, it's pure conjecture (and even then, executives are allowed to change their minds).
Apple joining simply means they won't sue AOM's company for video codec patent.
They joined AOM at the highest level, which means they get a seat on the board of directors, I can't see any reason why they would do this unless they have decided to use it on their products.
Apple uses Opus too, I think IETF announced it as a RFC standard. ( If my memory serve me correct )
But Apple only support the usage of Opus in limited ways.
So why would Apple not use it? If we forget about the patents and royalty fees for the moment. AV1 isn't necessarily better then HEVC from Apple's prospective.
HEVC is actually a standard, and has been for many years. There are many difference implementation of HEVC encoder and decoder, all adhering to this standard and conformance. Even Apple has their own implementation, there are Open Sources like x265, and many other commercial solution as well. AV1 isn't a standard, ( yet ) and there is one and only one implementation. Now before any geeks starting arguing about software benefits of implementation as standard over written standard, you need to think of this not as a pieces of software ( While it certainly is ), but a tools for professionals. Those who do TVs, and movies, etc all wanted something different and they want choices.
Google, or On2 to be precise; continuing its tradition of over hyping its codec. AV1 at its start was no where near 30% better then HEVC. And since they claim AV1 is now another 30% better then their initial version, you would have expect it to be 1.3 x 1.3 better then HEVC. But truth to be told AV1 when tested by panel of expert provide tangible better results then HEVC, at the cost of much slower encoding time. While that was done a while ago and AV1 has since improved a lot more, we shall wait and see when it finalized.
Everyone has been saying they will be forced to support AV1 because of Netflix and Youtube. Well that is only half correct because Netflix are already encoding in HEVC. And Netflix, has yet to provide their newer results of HEVC vs AV1. My guess is that they are waiting for AV1 to finalize. VMAF is a lot better then all other PSNR or SSIM, but it is still not perfect.
There are zero Full hardware AV1 decoder ( There may be partial Hardware decode that could be enabled with update, but you be the judge how many hardware manufacture is going to enable that then to sell you something new ) , but there are billions of devices capable of decoding HEVC already.
So apart from being royalty free, AV1 doesn't have a lot of advantage to it. The question is, for most business, will using AV1 saves me more money in the long term then using HEVC.
Apple joining on board, with No Press Release from AOM, and only Cnet manage to pick up, suggest this may be an Intentional leak. Or one way of Apple saying, HEVC Groups, you either do as I say and lower your fees, allow free software decode implementation ( One of the group already allows that ), or you know what? You can hold on to your patents for as long as you want and you wont earn a single dent in the billion of iOS devices in the future.
Once the AV1 bitstream is frozen, it will also be a 'standard', only this will be royalty free.
>there are Open Sources like x265, and many other commercial solution as well.
Nothing prevents x265 devs from making xAV1 (or whatever AV1 will end up being called), their spokesperson over at Doom9 has already said that they will go where the market goes in terms of encoder development, they are also very pissed in regards to the HEVC licensing debacle.
>we shall wait and see when it finalized.
Indeed, the bitstream is (supposed) to be finalized this month, after that happens we will finally see optimization take place (basically rewriting all hot spots into handwritten assembly) and thus be able to assess the quality claims and just how much slower it will be.
>Well that is only half correct because Netflix are already encoding in HEVC.
Netflix was one of the first companies to join AOM to develop a royalty free codec, it seems clear their intentions is to replace HEVC with AV1 once wide hardware support arrives.
>There are zero Full hardware AV1 decoder
There can't be until the bitstream has been frozen, from what I've read the first hardware supporting AV1 will be 12-18 months after said bitstream freeze.
Throughout the development of AV1, there's been constant consulting with hardware developers and they have had a large say in how AV1 works, the hardware companies that are part of AOM are:
Intel, AMD, ARM, Broadcom, NVidia, Realtek and now recently Apple
>So apart from being royalty free, AV1 doesn't have a lot of advantage to it.
If the estimates are correct, ~30% better compression is a HUGE advantage, another advantage from the point of the companies in AOM is that developing a codec themselves means it will fulfill their needs much better.
Google was going this route ever since they purchased On2, but now it really has reached critical mass with their third generation codec (VP10) being the base for AV1 which has made practically all the big tech companies come together and solve their codec needs using it.
>Apple joining on board, with No Press Release from AOM
I think Apple didn't want to ruffle any feathers with MPEGLA and the other HEVC licensees, Apple picking up HEVC support across their products was seen as a good sign for HEVC, the same Apple joining all the other tech giants in AOM backing AV1 is quite the opposite. Thus they join with no fanfare. Pure speculation of course.
https://streaminglearningcenter.com/codecs/netflix-on-av1.ht...
This means AV1 will be the de facto next generation codec standard on the web as it will be supported by all browsers and all mobile devices, something HEVC never will.
https://github.com/nokiatech/heif
Apple could and probably will add AV1 support to their HEIF implementation in the future.