AOMedia Video 1

offene, lizenzkostenfreie Videokompression
Dies ist eine alte Version dieser Seite, zuletzt bearbeitet am 11. Juni 2017 um 01:50 Uhr durch 50.101.171.181 (Diskussion) (References). Sie kann sich erheblich von der aktuellen Version unterscheiden.

AOMedia Video 1 (AV1) is an open, royalty-free video coding format designed for video transmissions over the Internet. It is being developed by the Alliance for Open Media (AOMedia), a consortium of leading firms from the semiconductor industry, video on demand providers, and web browser developers, founded in 2015. It is the primary contender for standardisation by the video standard working group NetVC of the Internet Engineering Task Force (IETF).[1] The group has put together a list of criteria to be met by the new video standard.[2] It is meant to succeed its predecessor VP9 and compete with HEVC/H.265 from the Moving Picture Experts Group.[3]

AV1 can be used together with the audio format Opus in a future version of the WebM format for HTML5 web video and WebRTC.[4]

Purpose

The purpose of AV1 is to be as good as possible under royalty-free patent licensing. Crucial to this objective is therefore to ensure, during development, that it does not infringe on patents of competing companies. This contrasts to its main competitor HEVC, for which IPR review was not part of the standardization process.[5] The latter practice is stipulated in ITU-T's definition of an open standard. The case of HEVC's independent patent pools has been characterized by critical observers as a failure of price management.[6]

Under patent rules adopted from the World Wide Web Consortium (W3C), technology contributors license their AV1-connected patents to anyone, anywhere, anytime based on reciprocity, i.e. as long as the user doesn't engage in patent litigation.[7] As a defensive condition, anyone engaging in patent litigation loses the right to the patents of all patent holders.[5]

It aims for state of the art performance with a noticeable compression efficiency advantage at only slightly increased coding complexity. The efficiency goal is 25% improvement over HEVC.[2]

However, based on the most recent and the most reliable researches in this field [8], the AV1 performance is currently considered to be significantly inferior compared to other codecs, such as HEVC-based codecs or even H.264/AVC-based. Particularly, according to the experimental results presented in detail in [8], the coding efficiency of AV1 was shown to be inferior to all tested encoders, in particular relative to the reference encoders of H.264/AVC and HEVC with an average bit-rate overhead at the same objective quality of 10.5% and 65.7%, respectively. Also, it was shown that for these bit-rate overheads, the AV1 encoding times are quite similar to those of the full-fledged HM and JM reference software encoders, which have been developed during the standardization of HEVC and H.264/AVC, respectively.

According to another less-known publication, at the beginning of June 2016 its performance was already comparable to HEVC as measured using the objective metric PSNR-HVS-M.[9]

It is specifically designed for real-time applications (especially WebRTC) and higher resolutions (wider color gamuts, higher frame rates, UHD) than typical usage scenarios of the current generation (H.264) of video formats where it is expected to achieve its biggest efficiency gains. It is therefore planned to support the color space from ITU-R Recommendation BT.2020 and 10 and 12 bits of precision per color component.[10]

Technology

 
AV1 introduces "T-shaped" partitioning schemes for coding units, a feature from VP10

Vorlage:See also AV1 is a traditional block-based frequency transform format featuring new techniques taken from several experimental formats that are testing technology for a next-generation format after HEVC and VP9.[11] Based on Google's experimental VP9 evolution project VP10,[12] it will incorporate additional techniques developed in Xiph's/Mozilla's Daala and Cisco's Thor.

Doing internal processing in higher precision (10 or 12 bits per sample) leads to compression improvement due to smaller rounding errors in reference imagery. For intra prediction, there are more (than 8) angles for directional prediction and weighted filters for per-pixel extrapolation. Temporal prediction can use more references. Prediction can happen for bigger units (≤128×128) and they can be subpartitioned in more ways. Predictions can be combined in more advanced ways (than a uniform average) in a block, including smooth and sharp gradients in different directions. This allows either inter-inter or inter-intra predictions to be combined in the same block.[13][14] Conventional scalar quantisation with binary arithmetic coding is currently used, inherited from VP9, but experiments are ongoing to investigate other systems including multisymbol coding, and Perceptual Vector Quantization from Daala.[15] Asymmetric Numeral Systems coding is being considered for the entropy coding phase.[16] For the in-loop filtering step it has a deblocking filter and experimental deringing filters from both Thor and Daala.

The Alliance publishes a reference implementation written in C and assembly language (aomenc, aomdec) as free software under the terms of the BSD 2-Clause License.[17]

History

The first official announcement of the project came with the press release on the formation of the Alliance. The growing usage of its predecessor VP9 is attributed to confidence in the Alliance and (the development of) AV1 as well as the pricey and complicated licensing situation of MPEG's competitor HEVC.[5]

The roots of the project precede the Alliance, however. Individual contributors started experimental technology platforms years before: Daala already published code in 2010, VP10 was announced on September 12, 2014, and Thor was published on August 11, 2015. The first version 0.1.0 of the AV1 reference codec was published on April 7, 2016.

In April 2017, using the 8 currently enabled experimental features (of 77 total), Bitmovin was able to demonstrate favorable objective metrics, as well as visual results, compared to HEVC on the Sintel animated film.[18][19]

The bitstream format is projected to be frozen in Q3[18] or Q4[20] of 2017. The first compatible hardware components are expected to become available within 12 months after that.

Adoption

It is expected that Alliance members have interest in adopting the format, in respective ways, once the bitstream is frozen.[10][18] The member companies represent several industries, including browser vendors (Google, Mozilla, Microsoft), content providers (Google, Netflix, Amazon) and hardware manufacturers (Intel, AMD, ARM, Nvidia).[5]

Video streaming service YouTube declared intent to transition to the new format as fast as possible, starting with highest resolutions within six months after the finalization of the bitstream format.[10]

Like its predecessor VP9, AV1 will be used together with the WebM and Opus formats. These are well supported among web browsers, with the exception of Safari (desktop and mobile editions) and the discontinued Internet Explorer (prior to Edge) (see VP9 in HTML5 video § browser support).

References

Vorlage:Reflist

Commons: AOMedia Video – Sammlung von Bildern, Videos und Audiodateien

Vorlage:Compression formats

  1. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen blend.
  2. a b Sebastian Grüner: Der nächste Videocodec soll 25 Prozent besser sein als H.265. golem.de, 19. Juli 2016, abgerufen am 1. März 2017.
  3. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen VP9 successor.
  4. Tsahi Levent-Levi: WebRTC Codec Wars: Rebooted. In: BlogGeek.me. 3. September 2015, abgerufen am 1. März 2017: „The beginning of the end of HEVC/H.265 video codec“
  5. a b c d Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen tb_lca.
  6. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen epic_fail.
  7. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen patent license.
  8. a b Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen comparison.
  9. Sebastian Grüner: Freie Videocodecs teilweise besser als H.265. golem.de, 9. Juni 2016, abgerufen am 1. März 2017.
  10. a b c Jan Ozer: What is AV1? In: Streaming Media. Information Today, Inc., 3. Juni 2016, archiviert vom Original am 26. November 2016; abgerufen am 26. November 2016: „... Once available, YouTube expects to transition to AV1 as quickly as possible, particularly for video configurations such as UHD, HDR, and high frame rate videos ... Based upon its experience with implementing VP9, YouTube estimates that they could start shipping AV1 streams within six months after the bitstream is finalized. ...“ Fehler beim Aufruf der Vorlage:Cite web: Archiv im Parameter URL erkannt. Archive müssen im Parameter Archiv-URL angegeben werden.
  11. Romain Bouqueau: A view on VP9 and AV1 part 1: specifications, GPAC Project on Advanced Content, 12. Juni 2016. Abgerufen am 1. März 2017 
  12. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen basis.
  13. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen VP10.
  14. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen VP10_1_year_in_presentation.
  15. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen Daala.
  16. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen ANS.
  17. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen license.
  18. a b c Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen bitmovin_moves_in.
  19. Referenzfehler: Ungültiges <ref>-Tag; kein Text angegeben für Einzelnachweis mit dem Namen ozer_compares_hevc.
  20. https://fosdem.org/2017/schedule/event/om_av1/