Английская Википедия:AV1

Материал из Онлайн справочника
Перейти к навигацииПерейти к поиску

Шаблон:Short description Шаблон:Hatnote group Шаблон:Use dmy dates Шаблон:Infobox file format

AOMedia Video 1 (AV1) is an open, royalty-free video coding format initially designed for video transmissions over the Internet. It was developed as a successor to VP9 by the Alliance for Open Media (AOMedia),[1] a consortium founded in 2015 that includes semiconductor firms, video on demand providers, video content producers, software development companies and web browser vendors. The AV1 bitstream specification includes a reference video codec.[2] In 2018, Facebook conducted testing that approximated real-world conditions, and the AV1 reference encoder achieved 34%, 46.2% and 50.3% higher data compression than libvpx-vp9, x264 High profile, and x264 Main profile respectively.[3]

Like VP9, but unlike H.264 (AVC) and H.265 (HEVC), AV1 has a royalty-free licensing model that does not hinder adoption in open-source projects.[4][5][6][7][1][8]

AVIF is an image file format that uses AV1 compression algorithms.

History

Файл:AV1-logo.svg
AV1 logo prior to 2018

The Alliance's motivations for creating AV1 included the high cost and uncertainty involved with the patent licensing of HEVC, the MPEG-designed codec expected to succeed AVC.[9][7] Additionally, the Alliance's seven founding members – Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix – announced that the initial focus of the video format would be delivery of high-quality web video.[10] The official announcement of AV1 came with the press release on the formation of the Alliance for Open Media on 1 September 2015. Only 42 days before, on 21 July 2015, HEVC Advance's initial licensing offer was announced to be an increase over the royalty fees of its predecessor, AVC.[11] In addition to the increased cost, the complexity of the licensing process increased with HEVC. Unlike previous MPEG standards where the technology in the standard could be licensed from a single entity, MPEG LA, when the HEVC standard was finished, two patent pools had been formed with a third pool on the horizon. In addition, various patent holders were refusing to license patents via either pool, increasing uncertainty about HEVC's licensing. According to Microsoft's Ian LeGrow, an open-source, royalty-free technology was seen as the easiest way to eliminate this uncertainty around licensing.[9]

The negative effect of patent licensing on free and open-source software has also been cited as a reason for the creation of AV1.[7] For example, building an H.264 implementation into Firefox would prevent it from being distributed free of charge since licensing fees would have to be paid to MPEG-LA.[12] Free Software Foundation Europe has argued that FRAND patent licensing practices make the free software implementation of standards impossible due to various incompatibilities with free-software licenses.[8]

Many of the components of the AV1 project were sourced from previous research efforts by Alliance members. Individual contributors had started experimental technology platforms years before: Xiph's/Mozilla's Daala published code in 2010, Google's experimental VP9 evolution project VP10 was announced on 12 September 2014,[13] and Cisco's Thor was published on 11 August 2015. Building on the code base of VP9, AV1 incorporates additional techniques, several of which were developed in these experimental formats.[14]

Many companies are part of Alliance for Open Media, including Samsung, Vimeo, Microsoft, Netflix, Mozilla, AMD, Nvidia, Intel and ARM, Google, Facebook, Cisco, Amazon, Hulu, VideoLAN, Adobe, and Apple. Apple is an AOMedia governing member, although it joined after the formation. The management of the AV1 streams has been officially included among the typological videos manageable by Coremedia.[15] The first version 0.1.0 of the AV1 reference codec was published on April 7, 2016. Although a soft feature freeze came into effect at the end of October 2017, development continued on several significant features. The bitstream format, was projected to be frozen in January 2018 but was delayed due to unresolved critical bugs as well as further changes to transformations, syntax, the prediction of motion vectors, and the completion of legal analysis.Шаблон:Citation needed The Alliance announced the release of the AV1 bitstream specification on March 28, 2018, along with a reference, software-based encoder and decoder.[16] On 25 June 2018, a validated version 1.0.0 of the specification was released.[17] On January 8, 2019, a validated version 1.0.0 with Errata 1 of the specification was released. Martin Smole from AOM member Bitmovin said that the computational efficiency was the greatest remaining challenge after the bitstream format freeze had been completed.[18] While working on the format, the encoder was not targeted for production use and speed optimizations were not prioritized. Consequently, the early version of AV1 was orders of magnitude slower than existing HEVC encoders. Much of the development effort was consequently shifted towards maturing the reference encoder. In March 2019, it was reported that the speed of the reference encoder had improved greatly and within the same order of magnitude as encoders for other common formats.[19] On January 21, 2021, the MIME type of AV1 was defined as video/AV1. The usage of AV1 using this MIME type is restricted to Real-time Transport Protocol purposes only.[20]

Purpose

AV1 aims to be a video format for the web that is both state of the art and royalty free.[1] According to Matt Frost, head of strategy and partnerships in Google's Chrome Media team, "The mission of the Alliance for Open Media remains the same as the WebM project."[21] A recurring concern in standards development, not least of royalty-free multimedia formats, is the danger of accidentally infringing on patents that their creators and users did not know about. This concern has been raised regarding AV1,[22] and previously VP8,[23] VP9,[24] Theora[25] and IVC.[26] The problem is not unique to royalty-free formats, but it uniquely threatens their status as royalty-free.

Patent licensing AV1, VP9, Theora, MPEG-5 Base profile VVC, HEVC, AVC, MPEG-5 Main profile GIF, MP3, MPEG-1, MPEG-2, MPEG-4 Part 2
By known patent holders Шаблон:Free Шаблон:Nonfree Patents expired
By unknown patent holders Impossible to ascertain until the format is old enough that any patents would have expired (at least 20 years in WTO countries)

To fulfill the goal of being royalty free, the development process requires that no feature can be adopted before it has been confirmed independently by two separate parties to not infringe on patents of competing companies. In cases where an alternative to a patent-protected technique is not available, owners of relevant patents have been invited to join the Alliance (even if they were already members of another patent pool). For example, Alliance members Apple, Cisco, Google, and Microsoft are also licensors in MPEG-LA's patent pool for H.264.[22] As an additional protection for the royalty-free status of AV1, the Alliance has a legal defense fund to aid smaller Alliance members or AV1 licensees in the event they are sued for alleged patent infringement.[22][6][27]

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 does not engage in patent litigation).[28] As a defensive condition, anyone engaging in patent litigation loses the right to the patents of all patent holders.Шаблон:Citation needed[29]

This treatment of intellectual property rights (IPR), and its absolute priority during development, is contrary to extant MPEG formats like AVC and HEVC. These were developed under an IPR uninvolvement policy by their standardization organisations, as stipulated in the ITU-T's definition of an open standard. However, MPEG's chairman has argued this practice has to change,[30] which it is:Шаблон:Citation needed EVC is also set to have a royalty-free subset,[31][32] and will have switchable features in its bitstream to defend against future IPR threats.Шаблон:Citation needed

The creation of royalty-free web standards has been a long-stated pursuit for the industry. In 2007, the proposal for HTML5 video specified Theora as mandatory to implement. The reason was that public content should be encoded in freely implementable formats, if only as a "baseline format", and that changing such a baseline format later would be hard because of network effects.[33]

The Alliance for Open Media is a continuation of Google's efforts with the WebM project, which renewed the royalty-free competition after Theora had been surpassed by AVC. For companies such as Mozilla that distribute free software, AVC can be difficult to support as a per-copy royalty is unsustainable given the lack of revenue stream to support these payments in free software (see FRAND § Excluding costless distribution).[4] Similarly, HEVC has not successfully convinced all licensors to allow an exception for freely distributed software (see HEVC § Provision for costless software).

The performance goals include "a step up from VP9 and HEVC" in efficiency for a low increase in complexity. NETVC's efficiency goal is 25% improvement over HEVC.[34] The primary complexity concern is for software decoding, since hardware support will take time to reach users. However, for WebRTC, live encoding performance is also relevant, which is Cisco's agenda: Cisco is a manufacturer of videoconferencing equipment, and their Thor contributions aim at "reasonable compression at only moderate complexity".[35]

Feature-wise, AV1 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 up to 12 bits of precision per color component.[36] AV1 is primarily intended for lossy encoding, although lossless compression is supported as well.[37]

Technology

Шаблон:See also AV1 is a traditional block-based frequency transform format featuring new techniques. Based on Google's VP9,[38] AV1 incorporates additional techniques that mainly give encoders more coding options to enable better adaptation to different types of input.

Файл:The Technology Inside Av1.svg
Processing stages of an AV1 encoder with relevant technologies associated with each stage

Шаблон:Infobox software

The Alliance published a reference implementation written in C and assembly language (aomenc, aomdec) as free software under the terms of the BSD 2-Clause License.[39] Development happens in public and is open for contributions, regardless of AOM membership. The development process was such that coding tools were added to the reference code base as experiments, controlled by flags that enable or disable them at build time, for review by other group members as well as specialized teams that helped with and ensured hardware friendliness and compliance with intellectual property rights (TAPAS). When the feature gained some support in the community, the experiment was enabled by default, and ultimately had its flag removed when all of the reviews were passed.[40] Experiment names were lowercased in the configure script and uppercased in conditional compilation flags.Шаблон:Citation needed To better and more reliably support HDR and color spaces, corresponding metadata can now be integrated into the video bitstream instead of being signaled in the container.

Partitioning

Файл:AV1 coding unit partitioning.svg
10 ways for subpartitioning coding units – into squares (recursively), rectangles, or mixtures thereof ("T-shaped")

Frame content is separated into adjacent same-sized blocks referred to as superblocks. Similar to the concept of a macroblock, superblocks are square-shaped and can either be of size 128×128 or 64×64 pixels. Superblocks can be divided in smaller blocks according to different partitioning patterns. The four-way split pattern is the only pattern whose partitions can be recursively subdivided. This allows superblocks to be divided into partitions as small as 4×4 pixels.

Файл:AV1 Partitioning.svg
Diagram of the AV1 superblock partitioning. It shows how 128×128 superblocks can be split all the way down to 4×4 blocks. As special cases, 128×128 and 8×8 blocks can't use 1:4 and 4:1 splits, and 8×8 blocks can't use "T"-shaped splits.

"T-shaped" partitioning patterns are introduced, a feature developed for VP10, as well as horizontal or vertical splits into four stripes of 4:1 and 1:4 aspect ratio. The available partitioning patterns vary according to the block size, both 128×128 and 8×8 blocks can't use 4:1 and 1:4 splits. Moreover, 8×8 blocks can't use "T" shaped splits.

Two separate predictions can now be used on spatially different parts of a block using a smooth, oblique transition line (wedge-partitioned prediction).Шаблон:Citation needed This enables more accurate separation of objects without the traditional staircase lines along the boundaries of square blocks.

More encoder parallelism is possible thanks to configurable prediction dependency between tile rows (ext_tile).[41]

Prediction

AV1 performs internal processing in higher precision (10 or 12 bits per sample), which leads to quality improvement by reducing rounding errors.

Predictions can be combined in more advanced ways (than a uniform average) in a block (compound prediction), including smooth and sharp transition gradients in different directions (wedge-partitioned prediction) as well as implicit masks that are based on the difference between the two predictors. This allows the combination of either two inter predictions or an inter and an intra prediction to be used in the same block.[42]Шаблон:Citation needed

A frame can reference 6 instead of 3 of the 8 available frame buffers for temporal (inter) prediction while providing more flexibility on bi-prediction[43] (ext_refsШаблон:Citation needed).

Файл:Bergensbanen 1280x720.ogv
Warped motion as seen from the front of a train

The Warped Motion (warped_motion)[41] and Global Motion (global_motionШаблон:Citation needed) tools in AV1 aim to reduce redundant information in motion vectors by recognizing patterns arising from camera motion.[41] They implement ideas that were attempted in preceding formats like e.g. MPEG-4 ASP, albeit with a novel approach that works in three dimensions. There can be a set of warping parameters for a whole frame offered in the bitstream, or blocks can use a set of implicit local parameters that get computed based on surrounding blocks.

Switch frames (S-frame) are a new inter-frame type that can be predicted using already-decoded reference frames from a higher-resolution version of the same video to allow switching to a lower resolution without the need for a full keyframe at the beginning of a video segment in the adaptive bitrate streaming use case.[44]

Intra prediction

Intra prediction consists of predicting the pixels of given blocks only using information available in the current frame. Most often, intra predictions are built from the neighboring pixels above and to the left of the predicted block. The DC predictor builds a prediction by averaging the pixels above and to the left of block.

Directional predictors extrapolate these neighboring pixels according to a specified angle. In AV1, 8 main directional modes can be chosen. These modes start at an angle of 45 degrees and increase by a step size of 22.5 degrees up until 203 degrees. Furthermore, for each directional mode, six offsets of 3 degrees can be signaled for bigger blocks, three above the main angle and three below it, resulting in a total of 56 angles (ext_intra).

The "TrueMotion" predictor was replaced with a Paeth predictor which looks at the difference from the known pixel in the above-left corner to the pixel directly above and directly left of the new one and then chooses the one that lies in direction of the smaller gradient as predictor. A palette predictor is available for blocks with up to 8 dominant colors, such as some computer screen content. Correlations between the luminosity and the color information can now be exploited with a predictor for chroma blocks that is based on samples from the luma plane (cfl).[41] In order to reduce visible boundaries along borders of inter-predicted blocks, a technique called overlapped block motion compensation (OBMC) can be used. This involves extending a block's size so that it overlaps with neighboring blocks by 2 to 32 pixels, and blending the overlapping parts together.[45]

Data transformation

To transform the error remaining after prediction to the frequency domain, AV1 encoders can use square, 2:1/1:2, and 4:1/1:4 rectangular DCTs (rect_tx),[43] as well as an asymmetric DST[46][47][48] for blocks where the top and/or left edge is expected to have lower error thanks to prediction from nearby pixels, or choose to do no transform (identity transform).

It can combine two one-dimensional transforms in order to use different transforms for the horizontal and the vertical dimension (ext_tx).[41][43]

Quantization

AV1 has new optimized quantization matrices (aom_qm).[49] The eight sets of quantization parameters that can be selected and signaled for each frame now have individual parameters for the two chroma planes and can use spatial prediction. On every new superblock, the quantization parameters can be adjusted by signaling an offset.

Filters

In-loop filtering combines Thor's constrained low-pass filter and Daala's directional deringing filter into the Constrained Directional Enhancement Filter, cdef. This is an edge-directed conditional replacement filter that smooths blocks roughly along the direction of the dominant edge to eliminate ringing artifacts.[50]

There is also the loop restoration filter (loop_restoration) based on the Wiener filter and self-guided restoration filters to remove blur artifacts due to block processing.[41]

Film grain synthesis (film_grain) improves coding of noisy signals using a parametric video coding approach. Due to the randomness, inherent to film grain noise, this signal component is traditionally either very expensive to code or prone to get damaged or lost, possibly leaving serious coding artifacts as residue. This tool circumvents these problems using analysis and synthesis, replacing parts of the signal with a visually similar synthetic texture based solely on subjective visual impression instead of objective similarity. It removes the grain component from the signal, analyzes its non-random characteristics, and instead transmits only descriptive parameters to the decoder, which adds back a synthetic, pseudorandom noise signal that's shaped after the original component. It is the visual equivalent of the Perceptual Noise Substitution technique used in AC3, AAC, Vorbis, and Opus audio codecs.

Entropy coding

Daala's entropy coder (daala_ecШаблон:Citation needed), a non-binary arithmetic coder, was selected for replacing VP9's binary entropy coder. The use of non-binary arithmetic coding helps evade patents but also adds bit-level parallelism to an otherwise serial process, reducing clock rate demands on hardware implementations.Шаблон:Citation needed This is to say that the effectiveness of modern binary arithmetic coding like CABAC is being approached using a greater alphabet than binary, hence greater speed, as in Huffman code (but not as simple and fast as Huffman code). AV1 also gained the ability to adapt the symbol probabilities in the arithmetic coder per coded symbol instead of per frame (ec_adapt).[41]

AV1 has provisions for temporal and spatial scalability.[51]

Quality and efficiency

A first comparison from the beginning of June 2016[52] found AV1 roughly on par with HEVC, as did one using code from late January 2017.[53]

In April 2017, using the 8 enabled experimental features at the time (of 77 total), Bitmovin was able to demonstrate favorable objective metrics, as well as visual results, compared to HEVC on the Sintel and Tears of Steel short films.[54] A follow-up comparison by Jan Ozer of Streaming Media Magazine confirmed this, and concluded that "AV1 is at least as good as HEVC now".[55] Ozer noted that his and Bitmovin's results contradicted a comparison by Fraunhofer Institute for Telecommunications from late 2016[56] that had found AV1 65.7% less efficient than HEVC, underperforming even H.264/AVC which they concluded as being 10.5% more efficient. Ozer justified this discrepancy by having used encoding parameters endorsed by each encoder vendor, as well as having more features in the newer AV1 encoder.[56] Decoding performance was at about half the speed of VP9 according to internal measurements from 2017.[44]

Tests from Netflix in 2017, based on measurements with PSNR and VMAF at 720p, showed that AV1 was about 25% more efficient than VP9 (libvpx).[57] Tests from Facebook conducted in 2018, based on PSNR, showed that the AV1 reference encoder was able to achieve 34%, 46.2% and 50.3% higher data compression than libvpx-vp9, x264 High profile, and x264 Main profile respectively.[58][3]

Tests from Moscow State University in 2017 found that VP9 required 31% and HEVC 22% more bitrate than AV1 in order to achieve similar levels of quality.[59] The AV1 encoder was operating at speed "2500–3500 times lower than competitors" due to the lack of optimization (which was not available at that time).[60] Tests from University of Waterloo in 2020 found that when using a mean opinion score (MOS) for 2160p (4K) video AV1 had the bitrate saving of 9.5% compared to HEVC and 16.4% compared to VP9. They also concluded that at the time of the study at 2160p the AV1 video encodes on average took 590× longer compared to encoding with AVC; while HEVC took on average 4.2× longer and VP9 took on average 5.2× longer than AVC respectively.[61][62]

The latest encoder comparison by Streaming Media Magazine as of September 2020, which used moderate encoding speeds, VMAF, and a diverse set of short clips, indicated that the open-source libaom and SVT-AV1 encoders took about twice as long time to encode as x265 in its "veryslow" preset while using 15-20% less bitrate, or about 45% less bitrate than x264 veryslow. The best-in-test AV1 encoder, Visionular's Aurora1, in its "slower" preset, was as fast as x265 veryslow while saving 50% bitrate over x264 veryslow.[63]

CapFrameX tested the GPUs performance with AV1 decoding.[64] On 5 October 2022, Cloudflare announced that it has a beta player.[65]

Profiles and levels

Profiles

AV1 defines three profiles for decoders which are Main, High, and Professional. The Main profile allows for a bit depth of 8 or 10 bits per sample with 4:0:0 (greyscale) and 4:2:0 (quarter) chroma sampling. The High profile further adds support for 4:4:4 chroma sampling (no subsampling). The Professional profile extends capabilities to full support for 4:0:0, 4:2:0, 4:2:2 (half) and 4:4:4 chroma sub-sampling with 8, 10 and 12 bit color depths.[16]

Feature comparison between AV1 profiles
Main (0) High (1) Professional (2)
Bit depth 8 or 10 8 or 10 8, 10 & 12
Chroma subsampling 4:0:0 Шаблон:Yes Шаблон:Yes Шаблон:Yes
4:2:0 Шаблон:Yes Шаблон:Yes Шаблон:Yes
4:2:2 Шаблон:No Шаблон:No Шаблон:Yes
4:4:4 Шаблон:No Шаблон:Yes Шаблон:Yes

Levels

Шаблон:Technical

AV1 defines levels for decoders with maximum variables for levels ranging from 2.0 to 6.3.[66] The levels that can be implemented depend on the hardware capability.

Example resolutions would be 426×240@30Шаблон:Nbspfps for level 2.0, 854×480@30Шаблон:Nbspfps for level 3.0, 1920×1080@30Шаблон:Nbspfps for level 4.0, 3840×2160@60Шаблон:Nbspfps for level 5.1, 3840×2160@120Шаблон:Nbspfps for level 5.2, and 7680×4320@120Шаблон:Nbspfps for level 6.2. Level 7 has not been defined yet.[67]

seq_level_idx Level MaxPicSize
(Samples)
MaxHSize
(Samples)
MaxVSize
(Samples)
MaxDisplayRate
(Hz)
MaxDecodeRate
(Hz)
MaxHeader
Rate (Hz)
MainMbps
(Mbit/s)
HighMbps
(Mbit/s)
Min Comp Basis Max Tiles Max Tile Cols Example
0 2.0 147456 2048 1152 4,423,680 5,529,600 150 1.5 - 2 8 4 426×240@30fps
1 2.1 278784 2816 1584 8,363,520 10,454,400 150 3.0 - 2 8 4 640×360@30fps
4 3.0 665856 4352 2448 19,975,680 24,969,600 150 6.0 - 2 16 6 854×480@30fps
5 3.1 1065024 5504 3096 31,950,720 39,938,400 150 10.0 - 2 16 6 1280×720@30fps
8 4.0 2359296 6144 3456 70,778,880 77,856,768 300 12.0 30.0 4 32 8 1920×1080@30fps
9 4.1 2359296 6144 3456 141,557,760 155,713,536 300 20.0 50.0 4 32 8 1920×1080@60fps
12 5.0 8912896 8192 4352 267,386,880 273,715,200 300 30.0 100.0 6 64 8 3840×2160@30fps
13 5.1 8912896 8192 4352 534,773,760 547,430,400 300 40.0 160.0 8 64 8 3840×2160@60fps
14 5.2 8912896 8192 4352 1,069,547,520 1,094,860,800 300 60.0 240.0 8 64 8 3840×2160@120fps
15 5.3 8912896 8192 4352 1,069,547,520 1,176,502,272 300 60.0 240.0 8 64 8 3840×2160@120fps
16 6.0 35651584 16384 8704 1,069,547,520 1,176,502,272 300 60.0 240.0 8 128 16 7680×4320@30fps
17 6.1 35651584 16384 8704 2,139,095,040 2,189,721,600 300 100.0 480.0 8 128 16 7680×4320@60fps
18 6.2 35651584 16384 8704 4,278,190,080 4,379,443,200 300 160.0 800.0 8 128 16 7680×4320@120fps
19 6.3 35651584 16384 8704 4,278,190,080 4,706,009,088 300 160.0 800.0 8 128 16 7680×4320@120fps

Supported container formats

Standardized

  • ISO base media file format:[68] the ISOBMFF containerization spec by AOMedia was the first to be finalized and the first to gain adoption. This is the format used by YouTube.
  • Matroska: version 1 of the Matroska containerization spec[69] was published in late 2018.[70]

Unfinished standards

  • MPEG Transport Stream (MPEG TS)[71]
  • Real-time Transport Protocol: a preliminary RTP packetization spec by AOMedia defines the transmission of AV1 OBUs (Open Bitstream Units[72]) directly as the RTP payload.[51] It defines an RTP header extension that carries information about video frames and their dependencies, which is of general usefulness to § scalable video coding. The carriage of raw video data also differs from for example MPEG TS over RTP in that other streams, such as audio, must be carried externally.

Not standardized

  • WebM: as a matter of formality, AV1 has not been sanctioned into the subset of Matroska known as WebM as of late 2019.[73] However support has been present in libwebm since May 2018.[74]
  • On2 IVF: this format was inherited from the first public release of VP8, where it served as a simple development container.[75] rav1e also supports this format.[76]
  • Pre-standard WebM: Libaom featured early support for WebM before Matroska containerization was specified; this has since been changed to conform to the Matroska spec.[77]

Adoption

Content providers

AV1 video is usually accompanied with AAC / Opus audio in an ISO base media file format (MP4) container.

In October 2016, Netflix stated they expected to be an early adopter of AV1.[78] On 5 February 2020, Netflix began using AV1 to stream select titles on Android, providing 20% improved compression efficiency over their VP9 streams.[79] On 9 November 2021, Netflix announced it had begun streaming AV1 content to a number of TVs with AV1 decoders as well as the PlayStation 4 Pro.[80]

Файл:YouTube AV1 video with Opus audio stat screenshot.png
YouTube video statistics with AV1 video codec and Opus audio codec

In 2018, YouTube began rolling out AV1, starting with its AV1 Beta Launch Playlist. According to the description, the videos are (to begin with) encoded at high bitrate to test decoding performance, and YouTube has "ambitious goals" for rolling out AV1. YouTube for Android TV supports playback of videos encoded in AV1 on capable platforms as of version 2.10.13, released in early 2020.[81] In 2020 YouTube started serving videos at 8K resolution in AV1.[82]

In February 2019, Facebook following their own positive test results, said it would gradually roll out the AV1 codec as soon as browser support emerges, starting with their most popular videos.[58] Also in 2022, Meta (Facebook's parent company) said to been interested in the SVT-AV1 as in the meantime Google engineer Matt Frost spoke at the ending on YouTube's Intel channel that an intention, was carrying out a first test in 2023,[83] when the hardware accelerations will be introduced and widespread, but on the latest May video by Streaming Media the status was unknown and no statements from the AOMedia were expressed.[84] MSVP (Meta Scalable Video Processor) was announced[85] and the symposis was published in a popular scientific research website on 15 October 2022. On 4 November 2022 AV1 codec was announced with the article of Meta technology blog and with Mark Zuckerberg on Instagram Reels which shows AV1 codec compared with H.264/MPEG-4 AVC. Citing "Our Instagram engineering team developed a way to dramatically improve video quality. We made basic video processing 94% faster.[86][87] And even though Android does support AV1 playback natively, you'll have to implement some type of testing protocol—like Meta —to ensure smooth playback until AV1 hardware support becomes pervasive, which probably won't be until 2024 or beyond.[88][89]

In June 2019, Vimeo's videos in the "Staff picks" channel were available in AV1 and Opus.[90] Vimeo is using and contributing to Mozilla's Rav1e encoder and expects, with further encoder improvements, to eventually provide AV1 support for all videos uploaded to Vimeo as well as the company's "Live" offering.[90]

On 30 April 2020, iQIYI announced support for AV1 for users on PC web browsers and Android devices, according to the announcement, as the first Chinese video streaming site to adopt the AV1 format.[91]

Twitch plans to roll out AV1 for its most popular content in 2022 or 2023, with universal support projected to arrive in 2024 or 2025.[92]

In April 2021, Roku removed the YouTube TV app from the Roku streaming platform after a contract expired. It was later reported that Roku streaming devices do not use processors that support the AV1 codec. In December 2021, YouTube and Roku agreed to a multiyear deal to keep both the YouTube TV app and the YouTube app on the Roku streaming platform. Roku had argued that using processors in their streaming devices that support the royalty-free AV1 codec would increase costs to consumers.[93][94]

In January 2022, the Chinese video sharing website Bilibili rolled out H.265 HEVC and AV1 encoding to videos with high view-count, while videos with lower view-count are only available in H.264 AVC.[95]

Software implementations

  • Libaom is the reference implementation. It includes an encoder (aomenc) and a decoder (aomdec). As the former research codec, it has the advantage of being made to justifiably demonstrate efficient use of every feature, but at the general cost of encoding speed. At feature freeze, the encoder had become problematically slow, but dramatic speed optimizations with negligible efficiency impact have subsequently been made.[96][19]
  • SVT-AV1 includes an open-source encoder and decoder developed primarily by Intel in collaboration with Netflix[97][98] with a special focus on threading performance. They implemented in Cidana Corporation (Cidana Developers) and Software Implementation Working Group (SIWG). In August 2020, the Alliance for Open Media Software Implementation Working Group adopted SVT-AV1 as their production encoder.[99] SVT-AV1 1.0.0 was released on 22 April 2022.[100] SVT-AV1 1.8.0 was released on 11 December 2023.[101]
  • rav1e is an encoder written in Rust and assembly language from the Xiph.Org Foundation.[76] rav1e takes the opposite developmental approach to aomenc: start out as the simplest (therefore fastest) conforming encoder, and then improve efficiency over time while remaining fast.[96]
  • dav1d is a decoder written in assembly and C99 focused on speed and portability, associated with VideoLAN.[102] The first official version (0.1) was released in December 2018.[103] Version 0.3 was announced in May 2019 with further optimizations demonstrating performance 2 to 5 times faster than aomdec.[104] Version 0.5 was released in October 2019.[105] Firefox 67 switched from Libaom to dav1d as a default decoder in May 2019.[106] In 2019, dav1d v0.5 was rated the best decoder in comparison to libgav1 and libaom.[107]
  • Cisco AV1 is a proprietary live encoder that Cisco developed for its Webex teleconference products. The encoder is optimized for latency[108] and the constraint of having an usable CPU footprint as with a "commodity laptop".[109] Cisco stressed that at their operating point – high speed, low latency – the large toolset of AV1 does not preclude a low encoding complexity.[108] Rather, the availability of tools for screen content and scalability in all profiles enabled them to find good compression-to-speed tradeoffs, better even than with HEVC;[109] Compared to their previously deployed H.264 encoder, a particular area of improvement was in high resolution screen sharing.[108]
  • libgav1 is a decoder written in C++11 released by Google.[110]

Other vendors had announced encoders, including EVE for AV1,[111] NGCodec,[112] Socionext,[113] Aurora[114] and MilliCast.[115]

Software support

Web browsers

Video players

Encoder front-ends

  • FFmpeg (libaom support since version 4.0,[136] rav1e support since version 4.3,[137] SVT-AV1 support since version 4.4[138])
  • HandBrake (since version 1.3.0, 9 November 2019 decoding support;[139] since version 1.6.0, 29 December 2022, SVT-AV1 and QSV AV1 encoding support)[140]
  • Bitmovin Encoding (since version 1.50.0, 4 July 2018)[141]

Video editors

  • DaVinci Resolve (since version 17.2, May 2021, decoding support; since version 17.4.6, March 2022, Intel Arc hardware encoding support, since version 18.1, November 2022, Nvidia hardware encoding support)

Others

  • GStreamer (since version 1.14)[142]
  • OBS Studio (libaom and SVT-AV1 support since 27.2 Beta 1)[143] and since OBS Studio 29.1 Beta 1 encoding with GPUs that support it (QSV, NVENC, VCN 4.0) as well as AV1 streaming transmission on YouTube and also other platforms via RTMP (Real Time Messaging Protocol), YouTube joins SRT Alliance.
  • MKVToolNix (adoption of final av1-in-mkv spec since version 28)
  • MediaInfo (since version 18.03)[144]
  • Google Duo (since April 2020)[145]
  • Adobe Audition (decoding support, preview video)
  • Avidemux (since version 2.76, 7 July 2020; decoding support)
  • VDPAU (since version 1.5, 7 March 2022; decoding support)

Operating system support

AV1 support by different operating systems
Microsoft Windows macOS BSD / Linux ChromeOS Android iOS
Codec support Шаблон:Partial Шаблон:Yes Шаблон:Yes Шаблон:Yes Шаблон:Yes Шаблон:Yes
Container support ISO base media file format (.mp4)
WebM (.webm)
Matroska (.mkv)
ISO base media file format (.mp4)
WebM (.webm)
ISO base media file format (.mp4)
WebM (.webm)
Matroska (.mkv)
ISO base media file format (.mp4)
WebM (.webm)
Matroska (.mkv)
ISO base media file format (.mp4)
WebM (.webm)
Notes - Support introduced in Windows 10 October 2018 Update (1809) with AV1 Video Extension add-on[123]

- Support for hardware acceleration added in Windows 10 November 2019 Update (1909)[146]

- Supported in Universal Windows Platform apps like Films & TV

- macOS Ventura has support for AVIF images, but not AV1 playback

- macOS Sonoma has support for AVIF images, AV1 hardware decoding support for devices with hardware decoding support, like Mac computers with Apple M3 SoCs.[127][128]

Supports decoding, from ChromeOS 70 onward Supported since Android 10[147][148][149] - iOS 16 has support for AVIF images, but not AV1 playback

- iOS 17 has support for AV1 playback on devices with hardware decoding support, like iPhone 15 Pro and iPhone 15 Pro Max.[126]

Hardware

Comparison of AV1 hardware
Company Product Шаблон:Abbr Шаблон:Abbr Profile Throughput
(single core)Шаблон:Clarify
Throughput
(max)Шаблон:Clarify
Ref
AMD RDNA 2 (excluding Navi 24 & iGPUs) Шаблон:Ya Шаблон:Na Main (0) 8K 10-bit [150][151][152]
RDNA 3 Шаблон:Ya Шаблон:Ya 8Kp60 (10-bit encode, 12-bit decode) [153][154]
Alveo MA35D Шаблон:Ya Шаблон:Ya [155][156]
Amlogic S905X4 Шаблон:Ya Шаблон:Na 4K 120fps 8K [157]
S908X Шаблон:Ya Шаблон:Na 8K 60fps
S805X2 Шаблон:Ya Шаблон:Na 1080p
Apple A17 Pro Шаблон:Ya Шаблон:Na 4K 60fps [158]
M3 series Шаблон:Ya Шаблон:Na
Broadcom BCM7218X Шаблон:Ya Шаблон:Na 4K [159]
Chips&Media WAVE510A
WAVE627[160]
Шаблон:Ya Шаблон:Ya Main (0) 4K 60fps 4K 120fps [161]
Google Tensor Original / G2 Шаблон:Ya Шаблон:Na 4K 60fps [162]
Tensor G3 Шаблон:Ya Шаблон:Ya 4K 60fps [163]
Intel Xe Шаблон:Ya Шаблон:Na Main (0) 8K 10-bit[164] [165][166][151][167]
Xe 2 Шаблон:Ya Шаблон:Ya 8K 10-bit 8K 10-bit
Arc Шаблон:Ya Шаблон:Ya [168]
Data Center GPU Flex Series Шаблон:Ya Шаблон:Ya [169][170]
MediaTek Dimensity 1000 series Шаблон:Ya Шаблон:Na 4K 60fps 4K 60fps [171][172][173][174]
Dimensity 9000 series Шаблон:Ya Шаблон:Na 8K 30fps [175][176]
MT96XX series Шаблон:Ya Шаблон:Na 4K 60fps 10-bit 4K 60fps 10-bit [177]
MT9950 Шаблон:Ya Шаблон:Na 8K 30fps [178]
NETINT Quadra T1 (1x Codensity G5 ASIC) Шаблон:Ya Шаблон:Ya 4x 4K 60fps 10-bit streams 4x 4K 60fps 10-bit streams [179][180]
Quadra T2 (2x Codensity G5 ASICs) Шаблон:Ya Шаблон:Ya 4x 4K 60fps 10-bit streams 8x 4K 60fps 10-bit streams [179][180]
Quadra T4 (4x Codensity G5 ASICs) Шаблон:Ya Шаблон:Ya 4x 4K 60fps 10-bit streams 16x 4K 60fps 10-bit streams [179][180]
Nvidia GeForce 30 Шаблон:Ya Шаблон:Na Main (0) 8K 60fps 10-bit [181][151][182]
GeForce 40 Шаблон:Ya Шаблон:Ya Main (0) 8K 60fps 10-bit 2x 8K 60fps 10-bit [183][184][185][186]
Qualcomm Snapdragon 8 Gen 2 Шаблон:Ya Шаблон:Na 8K 60fps [187]
Snapdragon 8 Gen 3 Шаблон:Ya Шаблон:Na
Realtek RTD1311 Шаблон:Ya Шаблон:Na 4K [188]
RTD2893 Шаблон:Ya Шаблон:Na 8K [189][190]
Rockchip RK3588 Шаблон:Ya Шаблон:Na 4K 60fps 10-bit [191]
Samsung Exynos 2000 series Шаблон:Ya Шаблон:Na 8K 30fps [192][193]

Several Alliance members demonstrated AV1 enabled products at IBC 2018,[194][195] including Socionext's hardware accelerated encoder. According to Socionext, the encoding accelerator is FPGA based and can run on an Amazon EC2 F1 cloud instance, where it runs 10 times faster than existing software encoders.

According to Mukund Srinivasan, chief business officer of AOM member Ittiam, early hardware support will be dominated by software running on non-CPU hardware (such as GPGPU, DSP or shader programs, as is the case with some VP9 hardware implementations), as fixed-function hardware will take 12–18 months after bitstream freeze until chips are available, plus 6 months for products based on those chips to hit the market.[40] The bitstream was finally frozen on March 28, 2018, meaning chips could be available sometime between March and August 2019.[22] According to the above forecast, products based on chips could then be on the market at the end of 2019 or the beginning of 2020.

  • On January 7, 2019, NGCodec announced AV1 support for NGCodec accelerated with Xilinx FPGAs.[112]
  • On April 18, 2019, Allegro DVT announced its AL-E210 multi-format video encoder hardware IP, the first publicly announced hardware AV1 encoder.[196][197]
  • On April 23, 2019, Rockchip announced their RK3588 SoC which features AV1 hardware decoding up to 4K 60fps at 10-bit color depth.[191]
  • On May 9, 2019, Amphion announced a video decoder with AV1 support up to 4K 60fps[198] On 28 May 2019, Realtek announced the RTD2893, its first integrated circuit with AV1 decoding, up to 8K.[189][190]
  • On June 17, 2019, Realtek announced the RTD1311 SoC for set-top boxes with an integrated AV1 decoder.[188]
  • On October 20, 2019, a roadmap from Amlogic shown 3 set-top box SoCs that are able to decode AV1 content, the S805X2, S905X4 and S908X.[199] The S905X4 was used in the SDMC DV8919 by December.[200]
  • On October 21, 2019, Chips&Media announced the WAVE510A VPU supporting decoding AV1 at up to 4Kp120.[201]
  • On November 26, 2019, MediaTek announced world's first smartphone SoC with an integrated AV1 decoder.[172] The Dimensity 1000 is able to decode AV1 content up to 4K 60fps.
  • On January 3, 2020, LG Electronics announced that its 2020 8K TVs, which are based on the α9 Gen 3 processor, support AV1.[202][203]
  • At CES 2020, Samsung announced that its 2020 8K QLED TVs, featuring Samsung's "Quantum Processor 8K SoC," are capable of decoding AV1.[204]
  • On August 13, 2020, Intel announced that their Intel Xe-LP GPU in Tiger Lake will be their first product to include AV1 fixed-function hardware decoding.[167][166]
  • On 1 September 2020, Nvidia announced that their Nvidia GeForce RTX 30 Series GPUs will support AV1 fixed-function hardware decoding.[181]
  • On 2 September 2020, Intel officially launched Tiger Lake 11th Gen CPUs with AV1 fixed-function hardware decoding.[205]
  • On 15 September 2020, AMD merged patches into the amdgpu drivers for Linux which adds support for AV1 decoding support on RDNA2 GPUs.[150][206][207]
  • On 28 September 2020, Roku refreshed the Roku Ultra including AV1 support.[208]
  • On 30 September 2020, Intel released version 20.3.0 for the Intel Media Driver which added support for AV1 decoding on Linux.[164][165][209]
  • On 10 October 2020, Microsoft confirmed support for AV1 hardware decoding on Xe-LP(Gen12), Ampere and RDNA2 with a blog post.[151]
  • On 11 January 2021, Intel announces new Pentium and Celeron models with 11th Gen UHD iGPU with the capability to support AV1 decode.[210]
  • On 12 January 2021, Samsung announced the Exynos 2100 with claimed AV1 decode support, however Samsung has not implemented AV1 support yet.[211][162]
  • On 16 March 2021, Intel officially launched Rocket Lake 11th Gen CPUs with AV1 fixed-function hardware decoding.[212]
  • On 19 October 2021, Google officially launched the Tensor featuring BigOcean supporting AV1 fixed-function hardware decoding.[213][162]
  • On 27 October 2021, Intel officially launched Alder Lake 12th Gen CPUs with AV1 fixed-function hardware decoding.[214]
  • On 4 January 2022, Intel officially launched Alder Lake 12th Gen mobile CPUs and non-K series desktop CPUs with AV1 fixed-function hardware decoding.[215]
  • On 17 February 2022, Intel officially announced that Arctic Sound-M has the industry's first hardware-based AV1 encoder inside a GPU.[216]
  • On 30 March 2022, Intel officially announced the Intel Arc Alchemist family with AV1 fixed-function hardware decoding and fixed-function hardware encoding.[217][218][219]
  • On 20 September 2022, Nvidia officially announced the Nvidia GeForce RTX 40 series with AV1 fixed-function hardware decoding and fixed-function hardware encoding.[184][185][186]
  • On 22 September 2022, Google released the Chromecast with Google TV (HD), the first Chromecast device with support for AV1 hardware decoding.[220]
  • On 26 September 2022, AMD released Ryzen 7000 series CPUs with an embedded GPU capable of AV1 hardware decoding.[221]
  • On 27 September 2022, Intel officially launched Raptor Lake 13th Gen CPUs with AV1 fixed-function hardware decoding.[222]
  • On 12 September 2023, Apple officially announced the iPhone 15 Pro and iPhone 15 Pro Max, featuring the A17 Pro SoC which is capable of AV1 hardware decoding.
  • On 19 September 2023, Intel officially announced Meteor Lake processor with AV1 fixed function hardware decoding and fixed function hardware encoding.[223]
  • On 16 October 2023, Intel officially launched Raptor Lake-Refresh 14th Gen CPUs with AV1 fixed-function hardware decoding.[224]
  • On 30 October 2023, Apple officially announced the M3 SoC family which are capable of AV1 hardware decoding.[225]
  • On 14 December 2023, Intel officially launched Intel Core Ultra Meteor Lake processor family with AV1 fixed function hardware decoding and fixed function hardware encoding.[226]

Patent claims

Sisvel, a Luxembourg-based company, has formed a patent pool, and are selling a patent license for AV1. The pool was announced in early 2019,[227] but a list of claimed patents was first published on 10 March 2020.[228] This list contains over 1050 patents.[228] The substance of the patent claims remains to be challenged.[229] Sisvel has stated that they won't seek content royalties, but their license makes no exemption for software.[228][229]

Шаблон:As of, the Alliance for Open Media has not responded to the list of patent claims. Their statement after Sisvel's initial announcement reiterated the commitment to their royalty-free patent license and made mention of the "AOMedia patent defense program to help protect AV1 ecosystem participants in the event of patent claims", but did not mention the Sisvel claim by name.[230]

According to The WebM Project, Google does not plan to alter their current or upcoming usage plans of AV1 even though they are aware of the patent pool.[231]

On 7 July 2022, it was revealed that the European Union's antitrust regulators had opened an investigation into AOM and its licensing policy. It said this action may be restricting the innovators' ability to compete with the AV1 technical specification, and also eliminate incentives for them to innovate.[232]

The Commission has information that AOM and its members may be imposing licensing terms (mandatory royalty-free cross licensing) on innovators that were not a part of AOM at the time of the creation of the AV1 technical, but whose patents are deemed essential to (its) technical specifications

On 23 May 2023, the European Commission decided to close the investigation while taking no further action. But in an email they reiterated that the closure does not constitute a finding of compliance or non-compliance with EU antitrust laws.[233]

In October 2023, patent pool operator Avanci announced the start of a new licensing program targeting video streaming operators that use AV1 in addition to H.265, H.266, VP9, etc.[234]

AV1 Image File Format (AVIF)

Шаблон:Main AV1 Image File Format (AVIF) is an image file format specification for storing still images or image sequences compressed with AV1 in the HEIF file format.[235] It competes with HEIC which uses the same container format, built upon ISOBMFF, but HEVC for compression.

See also

References

Шаблон:Reflist

External links

Шаблон:Commons category

Шаблон:Compression formats Шаблон:Compression Software Implementations

  1. 1,0 1,1 1,2 Ошибка цитирования Неверный тег <ref>; для сносок VP9 successor не указан текст
  2. Ошибка цитирования Неверный тег <ref>; для сносок av1-spec не указан текст
  3. 3,0 3,1 Шаблон:Cite web
  4. 4,0 4,1 Ошибка цитирования Неверный тег <ref>; для сносок tax не указан текст
  5. Ошибка цитирования Неверный тег <ref>; для сносок moz-avc-reluctance не указан текст
  6. 6,0 6,1 Ошибка цитирования Неверный тег <ref>; для сносок eetimes-av1release не указан текст
  7. 7,0 7,1 7,2 Ошибка цитирования Неверный тег <ref>; для сносок arstechnica-aom-announcement не указан текст
  8. 8,0 8,1 Ошибка цитирования Неверный тег <ref>; для сносок fsfe on frand не указан текст
  9. 9,0 9,1 Ошибка цитирования Неверный тег <ref>; для сносок cnet-aom-announcement не указан текст
  10. Ошибка цитирования Неверный тег <ref>; для сносок cisco-AV1-release не указан текст
  11. Ошибка цитирования Неверный тег <ref>; для сносок hevc-2015 не указан текст
  12. Ошибка цитирования Неверный тег <ref>; для сносок openh264 не указан текст
  13. Ошибка цитирования Неверный тег <ref>; для сносок CNETVP10September2014 не указан текст
  14. Ошибка цитирования Неверный тег <ref>; для сносок bitformat не указан текст
  15. Шаблон:Cite web
  16. 16,0 16,1 Ошибка цитирования Неверный тег <ref>; для сносок Shilov 2018 не указан текст
  17. Ошибка цитирования Неверный тег <ref>; для сносок Larabel 2018-06-25 не указан текст
  18. Ошибка цитирования Неверный тег <ref>; для сносок encoder speed не указан текст
  19. 19,0 19,1 Ошибка цитирования Неверный тег <ref>; для сносок near-reasonable не указан текст
  20. Шаблон:Cite web
  21. Ошибка цитирования Неверный тег <ref>; для сносок aom_mission не указан текст
  22. 22,0 22,1 22,2 22,3 Ошибка цитирования Неверный тег <ref>; для сносок ip remains не указан текст
  23. Ошибка цитирования Неверный тег <ref>; для сносок theregister-vp8 не указан текст
  24. Ошибка цитирования Неверный тег <ref>; для сносок comes of age не указан текст
  25. Ошибка цитирования Неверный тег <ref>; для сносок patents and standards не указан текст
  26. Ошибка цитирования Неверный тег <ref>; для сносок ivc не указан текст
  27. Ошибка цитирования Неверный тег <ref>; для сносок multichannel-nab2018 не указан текст
  28. Ошибка цитирования Неверный тег <ref>; для сносок theregisterpatent license не указан текст
  29. Шаблон:Cite web
  30. Ошибка цитирования Неверный тег <ref>; для сносок crisis не указан текст
  31. Шаблон:Cite web
  32. Шаблон:Cite web
  33. Ошибка цитирования Неверный тег <ref>; для сносок video element не указан текст
  34. Ошибка цитирования Неверный тег <ref>; для сносок netvc не указан текст
  35. Ошибка цитирования Неверный тег <ref>; для сносок integrating-thor не указан текст
  36. Ошибка цитирования Неверный тег <ref>; для сносок streamingmedia-2016-06-03 не указан текст
  37. Ошибка цитирования Неверный тег <ref>; для сносок github не указан текст
  38. Ошибка цитирования Неверный тег <ref>; для сносок basis не указан текст
  39. Ошибка цитирования Неверный тег <ref>; для сносок license не указан текст
  40. 40,0 40,1 Ошибка цитирования Неверный тег <ref>; для сносок streamingmedia-2017-08-30 не указан текст
  41. 41,0 41,1 41,2 41,3 41,4 41,5 41,6 Ошибка цитирования Неверный тег <ref>; для сносок ittiam-ibc не указан текст
  42. Ошибка цитирования Неверный тег <ref>; для сносок VP10 не указан текст
  43. 43,0 43,1 43,2 Ошибка цитирования Неверный тег <ref>; для сносок ibc2018-talk-codec-wars не указан текст
  44. 44,0 44,1 Ошибка цитирования Неверный тег <ref>; для сносок Streaming Media 2017-10-11 не указан текст
  45. Ошибка цитирования Неверный тег <ref>; для сносок feldman-obmc не указан текст
  46. Ошибка цитирования Неверный тег <ref>; для сносок Han Saxena Melkote Rose 2011 не указан текст
  47. Ошибка цитирования Неверный тег <ref>; для сносок negge-depth-packt не указан текст
  48. Ошибка цитирования Неверный тег <ref>; для сносок negge-depth-slides не указан текст
  49. Шаблон:Cite web
  50. Шаблон:Cite web
  51. 51,0 51,1 Ошибка цитирования Неверный тег <ref>; для сносок rtp не указан текст
  52. Ошибка цитирования Неверный тег <ref>; для сносок golem20160609 не указан текст
  53. Ошибка цитирования Неверный тег <ref>; для сносок elecard_comparison не указан текст
  54. Шаблон:Cite web
  55. Ошибка цитирования Неверный тег <ref>; для сносок ozer_compares_hevc не указан текст
  56. 56,0 56,1 Ошибка цитирования Неверный тег <ref>; для сносок comparison_by_hhi не указан текст
  57. Ошибка цитирования Неверный тег <ref>; для сносок Netflix не указан текст
  58. 58,0 58,1 Ошибка цитирования Неверный тег <ref>; для сносок Baumgartner 2019 не указан текст
  59. Ошибка цитирования Неверный тег <ref>; для сносок MSU2017-1 не указан текст
  60. Ошибка цитирования Неверный тег <ref>; для сносок MSU2017-2 не указан текст
  61. Шаблон:Cite web
  62. Шаблон:Cite web
  63. Ошибка цитирования Неверный тег <ref>; для сносок ozer-sept-2020 не указан текст
  64. Шаблон:Cite web
  65. Шаблон:Cite web
  66. Шаблон:Cite web
  67. Шаблон:Cite web
  68. Ошибка цитирования Неверный тег <ref>; для сносок isobmff не указан текст
  69. Ошибка цитирования Неверный тег <ref>; для сносок matroska не указан текст
  70. Ошибка цитирования Неверный тег <ref>; для сносок matroska merge не указан текст
  71. Ошибка цитирования Неверный тег <ref>; для сносок mpegts не указан текст
  72. Шаблон:Cite web
  73. Ошибка цитирования Неверный тег <ref>; для сносок WebM Container Guidelines не указан текст
  74. Шаблон:Cite web
  75. Ошибка цитирования Неверный тег <ref>; для сносок webm initial commit не указан текст
  76. 76,0 76,1 Ошибка цитирования Неверный тег <ref>; для сносок rav1e-github не указан текст
  77. Ошибка цитирования Неверный тег <ref>; для сносок libaom matroska не указан текст
  78. Ошибка цитирования Неверный тег <ref>; для сносок netflix-royaltyfree-2016 не указан текст
  79. Ошибка цитирования Неверный тег <ref>; для сносок netflix-feb-2020 не указан текст
  80. Ошибка цитирования Неверный тег <ref>; для сносок netflix-nov-2021 не указан текст
  81. Ошибка цитирования Неверный тег <ref>; для сносок youtubeapp не указан текст
  82. Шаблон:Cite web
  83. Шаблон:Cite web
  84. Шаблон:Cite web
  85. Шаблон:Cite web
  86. Шаблон:Cite web
  87. Шаблон:Cite web
  88. Шаблон:Cite web
  89. Шаблон:Cite web
  90. 90,0 90,1 Ошибка цитирования Неверный тег <ref>; для сносок vimeo-lightread не указан текст
  91. Шаблон:Cite news
  92. Ошибка цитирования Неверный тег <ref>; для сносок twitch-AV1-2019 не указан текст
  93. Шаблон:Cite web
  94. Шаблон:Cite web
  95. Шаблон:Cite web
  96. 96,0 96,1 Ошибка цитирования Неверный тег <ref>; для сносок lca2019 encoding speed не указан текст
  97. Ошибка цитирования Неверный тег <ref>; для сносок Armasu 2019 не указан текст
  98. Ошибка цитирования Неверный тег <ref>; для сносок Introducing SVT-AV1 не указан текст
  99. Шаблон:Cite web
  100. Шаблон:Cite web
  101. Шаблон:Cite web
  102. Ошибка цитирования Неверный тег <ref>; для сносок dav1d не указан текст
  103. Ошибка цитирования Неверный тег <ref>; для сносок Kempf Kempf 2018 не указан текст
  104. Ошибка цитирования Неверный тег <ref>; для сносок dav1d-0.3-release не указан текст
  105. Ошибка цитирования Неверный тег <ref>; для сносок jklempfrelease не указан текст
  106. Ошибка цитирования Неверный тег <ref>; для сносок firefox67-release не указан текст
  107. Шаблон:Cite web
  108. 108,0 108,1 108,2 Ошибка цитирования Неверный тег <ref>; для сносок cisco-bav не указан текст
  109. 109,0 109,1 Ошибка цитирования Неверный тег <ref>; для сносок cisco-frog не указан текст
  110. Шаблон:Cite web
  111. Ошибка цитирования Неверный тег <ref>; для сносок two-orioles-website не указан текст
  112. 112,0 112,1 Ошибка цитирования Неверный тег <ref>; для сносок ngcodec-encoder не указан текст
  113. Ошибка цитирования Неверный тег <ref>; для сносок socionext-fpga не указан текст
  114. Ошибка цитирования Неверный тег <ref>; для сносок visionular не указан текст
  115. Ошибка цитирования Неверный тег <ref>; для сносок medium не указан текст
  116. Ошибка цитирования Неверный тег <ref>; для сносок MozHacks 05 2019 не указан текст
  117. Шаблон:Cite web
  118. Шаблон:Cite web
  119. Ошибка цитирования Неверный тег <ref>; для сносок Slashdot2223241 не указан текст
  120. Шаблон:Cite web
  121. Ошибка цитирования Неверный тег <ref>; для сносок Techdows 2018 не указан текст
  122. Ошибка цитирования Неверный тег <ref>; для сносок Opera 57 не указан текст
  123. 123,0 123,1 Ошибка цитирования Неверный тег <ref>; для сносок Slashdot0213211 не указан текст
  124. Шаблон:Cite web
  125. Шаблон:Cite web
  126. 126,0 126,1 Шаблон:Cite web
  127. 127,0 127,1 Шаблон:Cite web
  128. 128,0 128,1 Шаблон:Cite web
  129. Ошибка цитирования Неверный тег <ref>; для сносок Tung 2018 не указан текст
  130. Шаблон:Cite web
  131. Шаблон:Cite web
  132. Ошибка цитирования Неверный тег <ref>; для сносок potplayer не указан текст
  133. Ошибка цитирования Неверный тег <ref>; для сносок K-Lite не указан текст
  134. Шаблон:Cite web
  135. Шаблон:Cite web
  136. Шаблон:Cite web
  137. Шаблон:Cite web
  138. Шаблон:Cite web
  139. Ошибка цитирования Неверный тег <ref>; для сносок handbrake не указан текст
  140. Шаблон:Cite web
  141. Ошибка цитирования Неверный тег <ref>; для сносок bitmovin не указан текст
  142. Ошибка цитирования Неверный тег <ref>; для сносок Larabel 2018-03-20 не указан текст
  143. Ошибка цитирования Неверный тег <ref>; для сносок phoronix-obs-beta не указан текст
  144. Ошибка цитирования Неверный тег <ref>; для сносок Serea 2018 не указан текст
  145. Ошибка цитирования Неверный тег <ref>; для сносок google-duo не указан текст
  146. Шаблон:Cite web
  147. Ошибка цитирования Неверный тег <ref>; для сносок androidQbeta не указан текст
  148. Ошибка цитирования Неверный тег <ref>; для сносок android10 не указан текст
  149. Ошибка цитирования Неверный тег <ref>; для сносок android10release не указан текст
  150. 150,0 150,1 Шаблон:Cite web
  151. 151,0 151,1 151,2 151,3 Шаблон:Cite web
  152. Шаблон:Cite web
  153. Шаблон:Cite web
  154. Шаблон:Cite web
  155. Шаблон:Cite web
  156. https://www.xilinx.com/content/dam/xilinx/publications/product-briefs/1978700-alveo-ma35d-product-brief.pdf
  157. Ошибка цитирования Неверный тег <ref>; для сносок Aufranc не указан текст
  158. Шаблон:Cite web
  159. Ошибка цитирования Неверный тег <ref>; для сносок broadcom-bcm7218x не указан текст
  160. Шаблон:Cite web
  161. Ошибка цитирования Неверный тег <ref>; для сносок chipsnmedia не указан текст
  162. 162,0 162,1 162,2 Шаблон:Cite web
  163. Шаблон:Cite web
  164. 164,0 164,1 Шаблон:Cite web
  165. 165,0 165,1 Шаблон:Cite web
  166. 166,0 166,1 Шаблон:Cite web
  167. 167,0 167,1 Шаблон:Cite web
  168. Шаблон:Cite web
  169. Шаблон:Cite web
  170. Шаблон:Cite web
  171. Шаблон:Cite web
  172. 172,0 172,1 Ошибка цитирования Неверный тег <ref>; для сносок :0 не указан текст
  173. Шаблон:Cite web
  174. Шаблон:Cite web
  175. Шаблон:Cite web
  176. Шаблон:Cite web
  177. Шаблон:Cite web
  178. Шаблон:Cite web
  179. 179,0 179,1 179,2 Шаблон:Cite web
  180. 180,0 180,1 180,2 Шаблон:Cite web
  181. 181,0 181,1 Шаблон:Cite web
  182. Шаблон:Cite web
  183. Шаблон:Cite web
  184. 184,0 184,1 Шаблон:Cite web
  185. 185,0 185,1 Шаблон:Cite web
  186. 186,0 186,1 Шаблон:Cite web
  187. Шаблон:Cite web
  188. 188,0 188,1 Ошибка цитирования Неверный тег <ref>; для сносок realtek-4k-decoder не указан текст
  189. 189,0 189,1 Ошибка цитирования Неверный тег <ref>; для сносок realtek-8k-decoder не указан текст
  190. 190,0 190,1 Ошибка цитирования Неверный тег <ref>; для сносок AnandTechRTD2893 не указан текст
  191. 191,0 191,1 Ошибка цитирования Неверный тег <ref>; для сносок cnx-rk3588 не указан текст
  192. Шаблон:Cite web
  193. Шаблон:Cite web
  194. Шаблон:Cite web
  195. Шаблон:Cite web
  196. Ошибка цитирования Неверный тег <ref>; для сносок allegro-4k-encoder не указан текст
  197. Ошибка цитирования Неверный тег <ref>; для сносок allegro-e210 не указан текст
  198. Ошибка цитирования Неверный тег <ref>; для сносок amphionsemi не указан текст
  199. Ошибка цитирования Неверный тег <ref>; для сносок cnx-software не указан текст
  200. Ошибка цитирования Неверный тег <ref>; для сносок cnx-software.com2019 не указан текст
  201. Ошибка цитирования Неверный тег <ref>; для сносок anandtech не указан текст
  202. Ошибка цитирования Неверный тег <ref>; для сносок lgnewsroom не указан текст
  203. Ошибка цитирования Неверный тег <ref>; для сносок theverge не указан текст
  204. Шаблон:Cite web
  205. Шаблон:Cite web
  206. Шаблон:Cite web
  207. Шаблон:Cite web
  208. Шаблон:Cite web
  209. Шаблон:Cite web
  210. Шаблон:Cite web
  211. Шаблон:Cite web
  212. Шаблон:Cite web
  213. Шаблон:Cite web
  214. Шаблон:Cite web
  215. Шаблон:Cite web
  216. Шаблон:Cite web
  217. Шаблон:Cite web
  218. Шаблон:Cite web
  219. Шаблон:Cite tweet
  220. Шаблон:Cite web
  221. Шаблон:Cite web
  222. Шаблон:Cite web
  223. Шаблон:Cite web
  224. Шаблон:Cite web
  225. Шаблон:Cite web
  226. https://www.intel.com/content/www/us/en/newsroom/news/core-ultra-client-computing-news-1.html
  227. Ошибка цитирования Неверный тег <ref>; для сносок sisvel-mux не указан текст
  228. 228,0 228,1 228,2 Ошибка цитирования Неверный тег <ref>; для сносок cnet-1050 не указан текст
  229. 229,0 229,1 Ошибка цитирования Неверный тег <ref>; для сносок sisvel-slc не указан текст
  230. Ошибка цитирования Неверный тег <ref>; для сносок aom-statement не указан текст
  231. Шаблон:Cite web
  232. Шаблон:Cite news
  233. Шаблон:Cite news
  234. Шаблон:Cite web
  235. Ошибка цитирования Неверный тег <ref>; для сносок aomediacodec.github.io av1-avif не указан текст