This is because it goes against multiple core values of the Firefox project: Firefox needs to be royalty-free in order to ship in many FOSS projects, which HEVC usage would prevent it from being and Mozilla believes in a free and open web, and that isn’t possible if you promote patent-encumbered standards. These steep royalties were already problematic for products like Google Chrome, Opera, Netflix, Amazon Video, Cisco WebEx Connect, Skype, and others, and they completely exclude HEVC as an option for projects like Mozilla Firefox. In order to ship a product with HEVC support, you need to acquire licenses from at least four patent pools (MPEG LA, HEVC Advance, Technicolor, and Velos Media) as well as numerous other companies, many of which do not offer standard licensing terms - instead requiring you to negotiate terms. The biggest difference between AV1 and HEVC (High-Efficiency Video Coding), also known as H.265, is in the licensing. It got to the point where Google even started to release code for VP10, but the company announced the cancelation of VP10 and formed the Alliance for Open Media (AOMedia) instead. Google announced that they planned to release VP10 in 2016 and then would release an update every 18 months to ensure a steady progression. A tiny increase in video compression per video can result in huge cost savings and a major improvement in user experience when you're accounting for billions of video minutes. However, because Google has a vested interest in adopting better compression algorithms to reduce the bandwidth usage of its data centers, it began to work on VP10 - the successor to VP9. YouTube made use of the codec on any device that could support it (as that meant big savings for Google thanks to reduced bandwidth), and it has even been adopted by video-on-demand services such as Netflix, Twitch, and Vimeo. VP9 is a royalty-free codec developed by Google that anyone can use, and because it's royalty-free, it could be implemented on any platform or service that wanted it. The context behind AV1 and why it was created is important as well. Google claims that its new Argos VCU can handle videos 20-33 times more efficiently than conventional servers. The chip, code-named "Argos", is a second-gen Video (trans) Coding Unit (VCU) that converts videos uploaded to the platform to various compression formats and optimizes them for different screen sizes. In fact, the company has designed its own silicon for the encoding of AV1 video that will be used in data centers for YouTube. Not only that, but YouTube on desktop also supports AV1, and you can enable it in your account settings so long as you're using a compatible browser. We reached out to Google for comment and were told that the Chromecast with Google TV (HD) supports AV1. Support is slowly growing in the industry, and the chipset in the Chromecast HD also supports AV1 decode, too. Later, the Qualcomm Snapdragon 8 Gen 2 brought support for AV1 decoding, and it's rumored that the upcoming Tensor G3 will support AV1 encoding as well. The Nvidia Geforce 3000 series supported decoding, the new Nvidia Geforce 4000 series supports both encoding and decoding, and Samsung's Exynos 2100/2200 both support AV1 decoding as well. The first smartphone chipset to support AV1 decode was the MediaTek Dimensity 1000, which supported up to 4K 60 FPS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |