VP8

VP8 is an open and royalty free video compression format created by On2 Technologies as a successor to VP7 and owned by Google from 2010.

For other uses, see VP8 (disambiguation).
VP8
Developed byGoogle
Initial releaseSeptember 13, 2008
Type of formatCompressed video
Contained byWebM, Matroska
Extended fromVP7
Extended toVP9
StandardRFC6386
Open format?Yes (specification under CC-by)[1]

In May 2010, after the purchase of On2 Technologies, Google provided an irrevocable patent promise on its patents for implementing the VP8 format, and released a specification of the format under the Creative Commons Attribution 3.0 license.[1] That same year, Google also released libvpx, the reference implementation of VP8, under the revised BSD license.[2]

Opera, Firefox, Chrome, and Chromium support playing VP8 video in HTML5 video tag.[3] Internet Explorer officially supports VP8 with a separate codec.[4] According to Google VP8 is mainly used in connection with WebRTC and as a format for short looped animations, as a replacement for the Graphics Interchange Format (GIF).[5]

VP8 can be multiplexed into the Matroska-based container format WebM along with Vorbis and Opus audio. The image format WebP is based on VP8's intra-frame coding. VP8's direct successor, VP9, and the emerging royalty-free internet video format AV1 from the Alliance for Open Media (AOMedia) are based on VP8.[6]

Features

VP8 only supports progressive scan video signals with 4:2:0 chroma subsampling and 8 bits per sample. In its first public version, On2's VP8 implementation supports multi-core processors with up to 64 cores simultaneously. At least in the implementation (from August 2011), VP8 is comparatively badly adapted to high resolutions (HD). With only three reference frame buffers needed, VP8 enables for decoder implementations with a relatively small memory footprint. The format features a pure intra mode, i.e. using only independently coded frames without temporal prediction, to enable random access in applications like video editing.

Technology

VP8 is a traditional block-based transform coding format. It has much in common with H.264, e.g. some prediction modes.[7] At the time of first presentation of VP8, according to On2 the in-loop filter[8] and the Golden Frames[9] were among the novelties of this iteration. The first definition of such a filter is already found in the H.263 standard, though, and Golden Frames were already in use in VP5[10] and VP7.[11]

The discrete cosine transform (DCT) on 4×4 blocks and the Hadamard transform (WHT) serve as basic frequency transforms. A maximum of three frames can be referenced for temporal prediction: the last Golden Frame (may be an intra frame), alternate reference frame, and the directly preceding frame. The so-called alternate reference frames (altref) can serve as reference-only frames for displaying them can be deactivated. In this case the encoder can fill them with arbitrary useful image data, even from future frames, and thereby serve the same purpose as the b-frames of the MPEG formats.[12] Similar macroblocks can be assigned to one of up to four (even spatially disjoint) segments and thereby share parameters like the reference frame used, quantizer step size, or filter settings. VP8 offers two different adjustable deblocking filters that are integrated into the codec loops (in-loop filtering). Many coding tools use probabilities that are calculated continuously from recent context, starting at each intra frames. Macro blocks can comprise 4×4, 8×8, or 16×16 samples. Motion vectors have quarter-pixel precision.

History

VP8 was first released by On2 Technologies on September 13, 2008, as On2 TrueMotion VP8, replacing its predecessor, VP7.[13][14]

After Google acquired On2 in February 2010,[15] calls for Google to release the VP8 source code were made. Most notably, the Free Software Foundation issued an open letter on March 12, 2010, asking Google to gradually replace the usage of Adobe Flash Player and H.264 on YouTube with a mixture of HTML5 and a freed VP8.[16]

On May 19, 2010, at its Google I/O conference, Google released the VP8 codec software under a BSD-like license and the VP8 bitstream format specification under an irrevocable free patent license.[17][18][19] This made VP8 the second product from On2 Technologies to be opened, following their donation of the VP3 codec in 2002 to the Xiph.Org Foundation,[20] from which they derived the Theora codec.

In February 2011, MPEG LA invited patent holders to identify patents that may be essential to VP8 in order to form a joint VP8 patent pool. As a result, in March the United States Department of Justice (DoJ) started an investigation into MPEG LA for its role in possibly attempting to stifle competition.[21][22] In July 2011, MPEG LA announced that 12 patent holders had responded to its call to form a VP8 patent pool, without revealing the patents in question,[23] and despite On2 having gone to great lengths to avoid such patents.[24]

In November 2011, the Internet Engineering Task Force published the informational RFC 6386, VP8 Data Format and Decoding Guide.

In March 2013, MPEG LA announced that it had dropped its effort to form a VP8 patent pool after reaching an agreement with Google to license the patents that it alleges "may be essential" for VP8 implementation, and granted Google the right to sub-license these patents to any third-party user of VP8 or VP9.[25][26] This deal has cleared the way for possible MPEG standardisation as its royalty-free internet video codec, after Google submitted VP8 to the MPEG committee in January 2013.[27]

In March 2013, Nokia asserted a patent claim against HTC and Google for the use of VP8 in Android in a German court;[28] however, on August 5, 2013 the webm project announced that the German court has ruled that VP8 does not infringe Nokia's patent.[29]

Nokia has made an official intellectual property rights (IPR) declaration to the IETF with respect to the VP8 Data Format and Decoding Guide listing 64 granted patents and 22 pending patent applications.[30]

Implementations

libvpx
Main article: libvpx

The reference implementation of a VP8 (and VP9) codec is found in the programming library libvpx which is released as free software. It has a mode for one-pass and two-pass encoding, respectively, while the one-pass mode is known as being broken and not offering effective control over the target bitrate.[31][32]

Currently, libvpx is the only software library capable of encoding VP8 video streams.[33] An encoder based on the x264 framework called xvp8 is under development by the x264 team.[34]

Encoding

A Video for Windows wrapper of the VP8 codec based on the Google VP8 library (FourCC: VP80) is available.[35]

The WebM Project hardware team in Finland released an RTL hardware encoder for VP8 that is available at no cost for semiconductor manufacturers.[36][37]

The Nvidia Tegra mobile chipsets have full VP8 hardware encoding and decoding (since Tegra 4).[38]

Nexus 5 could use hardware encoding[39]

Decoding

libvpx is capable of decoding VP8 video streams.[40]

On July 23, 2010, Fiona Glaser, Ronald Bultje, and David Conrad of the FFmpeg Team announced the ffvp8 decoder. Through testing they determined that ffvp8 was faster than Google's own libvpx decoder.[41] The WebM Project hardware team released an RTL hardware decoder for VP8, that is releasable to semiconductor companies at zero cost.[37][42] TATVIK Technologies announced a VP8 decoder that is optimized for the ARM Cortex-A8 processor.[43] Marvell's ARMADA 1500-mini chipset has VP8 SD and HD hardware decoding support (used in Chromecast).[44] Intel has full VP8 decoding support built into their Bay Trail chipsets.[45] Intel Broadwell also adds VP8 hardware decoding support.[46]

Operating system support
VP8 support by different operating systems
Microsoft Windows macOS BSD / Linux Android OS iOS
Codec support Yes Third-party apps only Yes Yes Third-party apps only
Container support On Windows 10 Anniversary Update (1607):
WebM (.webm is not recognised; requires pseudo extension)
Matroska (.mkv)

On Windows 10 October 2018 Update (1809):
WebM (.webm is recognised officially)

 WebM (.webm)
Matroska (.mkv)		 WebM (.webm)
Matroska (.mkv)		 WebM (.webm)
Matroska (.mkv)		 WebM (.webm)
Matroska (.mkv)
Notes On Windows 10:
- On Anniversary Update (1607), limited support is available in Microsoft Edge (via MSE only) and Universal Windows Platform apps.

- On April 2018 Update (1803) with Web Media Extensions preinstalled, Microsoft Edge (EdgeHTML 17) supports VP8 videos embedded in <video> tags.

- On October 2018 Update (1809), VP9 Video Extensions is preinstalled. It enables encoding of VP8 and VP9 content on devices that don’t have a hardware-based video encoder.[47]

 No native support in the macOS native multimedia framework. - - Support introduced in Android 2.3.3+

- Streamable in Android 4.0+

 No native support in the iOS native multimedia framework.

WebM
Main article: WebM

Also on May 19, 2010, the WebM Project was launched, featuring contributions from "Mozilla,[48] Opera,[49][50] Google[51] and more than forty other publishers, software and hardware vendors" in a major effort to use VP8 as the video format for HTML5.[52] In the WebM container format, the VP8 video is used with Vorbis or Opus audio.[53][54] Internet Explorer 9 will support VP8 video playback if the proper codec is installed.[4] Android is WebM-enabled from version 2.3 - Gingerbread.[55] Since Android 4.0, VP8 could be read inside mkv[56] and WebM could be streamed.[57] Adobe also announced that the Flash Player will support VP8 playback in a future release.[58]

WebP
Main article: WebP

On September 30, 2010 Google announced WebP, their new image format, on the Chromium blog.[59] WebP is based on VP8's intra-frame coding and uses a container based on Resource Interchange File Format (RIFF).

Comparison with H.264

While H.264/MPEG-4 AVC contains patented technology and requires licenses from patent holders and limited royalties for hardware, Google has irrevocably released the VP8 patents it owns under a royalty-free public license.[17][60]

According to a comparison of VP8 (encoded with the initial release of libvpx) and H.264 conducted by StreamingMedia, it was concluded that "H.264 may have a slight quality advantage, but it's not commercially relevant" and that "Even watching side-by-side (which no viewer ever does), very few viewers could tell the difference". They also stated that "H.264 has an implementation advantage, not a technology advantage."[61]

Google's claims that VP8 offers the "highest quality real-time video delivery"[62] and Libvpx includes a mode where the maximum CPU resources possible will be used while still keeping the encoding speed almost exactly equivalent to the playback speed (realtime), keeping the quality as high as possible without lag. On the other hand, a review conducted by streamingmedia.com in May 2010 concluded that H.264 offers slightly better quality than VP8.[63]

In September 2010 Fiona Glaser, a developer of the x264 encoder, gave several points of criticism for VP8, claiming that its specification was incomplete, and the performance of the encoder's deblocking filter was inferior to x264 in some areas.[64] In its specification, VP8 should be a bit better than H.264 Baseline Profile and Microsoft's VC-1. Encoding is somewhere between Xvid and VC-1. Decoding is slower than FFmpeg's H.264, but this aspect can hardly be improved due to the similarities to H.264. Compression-wise, VP8 offers better performance than Theora and Dirac. According to Glaser, the VP8 interface lacks features and is buggy, and the specification is not fully defined and could be considered incomplete. Much of the VP8 code is copy-pasted C code, and since the source constitutes the actual specification, any bugs will also be defined as something that has to be implemented to be in compliance.

In 2010, it was announced that the WebM audio/video format would be based on a profile of the Matroska container format together with VP8 video and Vorbis audio.[54]

gollark: New versions of TLS are meant to prevent that and osmarks.tk has support all the way up to TLS 1.3.
gollark: In ye olden SSL, apparently if your private key was leaked you could then retroactively decrypt traffic or something.
gollark: I don't think they can crack them "if needed" given modern forward-secrecy-capable TLS stuff.
gollark: I'm at least pretty confident that the NSA doesn't have access to communication between osmarks.tk and anyone who's using a modern browser to access it.
gollark: Oh. Aren't they quite large?

See also
  • List of open source codecs

References
  1. "VP8 Bitstream Specification License". WebM Project. Retrieved 30 January 2012.
  2. "Changes to the WebM Open Source License". Retrieved 2010-06-04.
  3. "Nokia lines up patents against VP8 video codec". Archived from the original on 28 May 2013. Retrieved 2013-03-25.
  4. Dean Hachamovitch (Microsoft) on March 16, 2011 on IEBlog: HTML5 Video Update—WebM for IE9
  5. Alex Converse (Google), September 19, 2015: New video compression techniques under consideration for VP10 – presentation at the VideoLAN Dev Days 2015 in Paris
  6. Zimmerman, Steven (15 May 2017). "Google's Royalty-Free Answer to HEVC: A Look at AV1 and the Future of Video Codecs". XDA Developers. Archived from the original on 14 June 2017. Retrieved 10 June 2017.
  7. "On2 VP8 - MultimediaWiki". wiki.multimedia.cx.
  8. "Loop Filter". Archived from the original on September 18, 2008. Retrieved February 22, 2010.
  9. "Golden Frames". Archived from the original on October 22, 2008. Retrieved February 22, 2010.
  10. description of VP5 on MultimediaWiki
  11. "On2's TrueMotion VP7 Video Codec". July 11, 2008. Archived from the original on March 23, 2010. Retrieved May 29, 2010.
  12. Yaowu Xu, 27. Mai 2010: Inside WebM Technology: The VP8 Alternate Reference Frame
  13. Glen Dickson (2008-09-16). "IBC2008: On2 Touts New Codec for Web Video". Broadcasting & Cable. Retrieved 2009-09-11.
  14. On2 Technologies (2008-09-13). "On2 Technologies Unveils New Advanced Video Compression Format". Digital TV. Retrieved 2012-01-30.
  15. "Google Closes On2 Technologies Acquisition" (Press release). Mountain View, California, USA: Google Inc. 2010-02-19. Retrieved 2013-03-22.
  16. Wilson, Holmes (2010-03-12). "Open letter to Google: free VP8, and use it on YouTube". Free Software Foundation.
  17. Google. "Additional IP Rights Grant (Patents)". Google. Retrieved 2010-06-04.
  18. "The WebM Project - Licenses". www.webmproject.org.
  19. Parr, Ben (2010-05-19), Google Makes Major Announcements at Google I/O, mashable.com
  20. The Free Library (2002-08-01) On2 Signs Pact With Xiph.org to Develop/Support VP3, Retrieved on 2009-08-16
  21. Catan, Thomas (4 March 2011), Web Video Rivalry Sparks U.S. Probe, The Wall Street Journal
  22. Cheng, Jacqui (4 March 2011). "Report: DoJ looking into possible anti-WebM moves by MPEG LA". Ars Technica. Condé Nast Digital. Retrieved 8 March 2011.
  23. Jan Ozer (2011-07-26). "WebM Patent Fight Ahead for Google?". StreamingMedia.com.
  24. Daffara, Carlo (25 May 2010), An analysis of WebM and its patent risk – updated, carlodaffara.conecta.it
  25. "Google and MPEG LA make a deal over VP8 codec - Update". The H. Archived from the original on 8 December 2013. Retrieved 10 March 2013.
  26. "Google and MPEG LA Announce Agreement Covering VP8 Video Format" (PDF). 7 March 2013.
  27. "VP8 could become MPEG standard". The H. Archived from the original on 8 December 2013. Retrieved 10 March 2013.
  28. "Patent clouds remain over VP8: Google points to FRAND option, Nokia alleges infringement in court". 2013-03-08.
  29. "Good News from Germany". 2013-08-05. Retrieved 2013-08-19.
  30. "Setback for Google's VP8: Nokia refuses to commit patents to royalty-free or FRAND licensing". www.fosspatents.com.
  31. Grois, Dan; Marpe, Detlev; Nguyen, Tung; Hadar, Ofer (2014), "Comparative assessment of H.265/MPEG-HEVC, VP9, and H.264/MPEG-AVC encoders for low-delay video applications", Proceedings of SPIE – Applications of Digital Image Processing XXXVII, Applications of Digital Image Processing XXXVII (in German), San Diego, California, 9217, pp. 92170Q, doi:10.1117/12.2073323
  32. Jan Ozer, June 2016: VP9 Finally Comes of Age, But Is it Right for Everyone?
  33. WebM VP8 Encoder [VP8 SDK], The WebM Project
  34. xvp8 at GitHub
  35. "Google VP8 Video For Windows codec". Optima SC Inc. Retrieved 2 September 2011.
  36. Introducing "Anthill," the First VP8 Hardware Encoder IP Release, WebM Project
  37. WebM Video Hardware RTLs, WebM Project
  38. NVIDIA Tegra 4 Family GPU Architecture (PDF)
  39. "The Nexus 5. A beautiful phone that includes powerful hardware based VP8 vide..."
  40. VP8 SDK - WebM VP8 Decoder, WebM Project
  41. Glaser, Fiona (2010-07-23), Diary Of An x264 Developer: Announcing the world's fastest VP8 decoder, archived from the original on 2010-09-30, retrieved 2012-01-04
  42. Availability of WebM (VP8) Video Hardware IP Designs, WebM Project
  43. Tatvik Announces High Performance VP8 Video Decoder Optimized For Cortex-A8 Using ARM NEON Technology, tatvik.com, 2011-03-09
  44. "Marvell flaunts its Armada 1500-mini CPU powering Chromecast, lists codecs".
  45. Klug, Anand Lal Shimpi, Brian. "The Bay Trail Preview: Intel Atom Z3770 Tested".
  46. "VA-API 1.3 Readies Broadwell Support, Adds VP8 Decoding - Phoronix". www.phoronix.com.
  47. HTML5 + - alltomwindows.se - Sveriges största Windows-community
  48. Blizzard, Christopher (2010-05-19), Firefox, YouTube and WebM, Mozilla
  49. Lie, Håkon Wium (2010-05-19), Welcome, WebM <video>!, Opera, archived from the original on 2011-03-21, retrieved 2014-10-30
  50. Mills, Chris (2010-05-19), Opera supports the WebM video format, Opera
  51. Bankoski, Jim (2010-05-19), WebM and VP8 land in Chromium, Google
  52. "WebM Code - Build Prerequisites". Retrieved 2010-06-02.
  53. Xiph.Org (2010-05-19). "Xiph.Org announces support for the WebM open media project". Retrieved 2010-05-20.
  54. WebM Project (2015-09-01). "WebM FAQ". Retrieved 2016-08-07.
  55. "The platform now offers built-in support for the VP8 open video compression format and the WebM open container format". Android Developers. Retrieved 16 January 2011.
  56. "Ice Cream Sandwich - Android Developers". Android Developers.
  57. "Supported media formats - Android Developers". Android Developers.
  58. Perkins, Michelle (2010-05-19), Flash Player Will Support VP8, Adobe
  59. Rabbat, Richard (2010-09-30). "WebP, a new image format for the Web". Chromium Blog. Google. Retrieved 2010-10-01.
  60. Metz, Cade (20 May 2010), Google backs open codec against patent trolls, The Register
  61. Ozer, Jan (2010). "VP8 vs. H.264" (PDF). streamingmedia.com. Retrieved 2011-03-08.
  62. "Benefits of WebM". Google. Retrieved 2011-02-13.
  63. "First Look: H.264 and VP8 Compared". streamingmedia.com. Retrieved 2011-02-13.
  64. Glaser, Fiona (2010-07-13). "First Look: H.264 and VP8 Compared". Diary Of An x264 Developer. Archived from the original on 2015-03-01. Retrieved 2013-07-01. I expect a spec will eventually be written, but it was a bit obnoxious of Google — both to the community and to their own developers — to release so early that they didn't even have their own documentation ready.

Further reading
  • Daniel Wolf, RWTH Aachen (ed.), WebM / VP8 (PDF) (in German), Aachen
  • Cassidy, Sean A. (2011-11-01). An Analysis of VP8, a new video codec for the web (M.S.). Rochester Institute of Technology. OCLC 768998565. Retrieved 2016-08-07.
  • Feller, Christian; Wuenschmann, Juergen; Roll, Thorsten; Rothermel, Albrecht (2016-09-06). Written at Ulm University. "The VP8 video codec - overview and comparison to H.264/AVC". 2011 IEEE International Conference on Consumer Electronics -Berlin (ICCE-Berlin). Berlin: IEEE: 57–61. doi:10.1109/ICCE-Berlin.2011.6031852. ISBN 978-1-4577-0233-4. ISSN 2166-6814. OCLC 759377866.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.