VP8

From Infogalactic: the planetary knowledge core
(Redirected from Libvpx)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

For other uses, see VP8 (disambiguation).
VP8
VP8 logo
Developed by Google
Initial release September 13, 2008
Type of format Compressed video
Contained by WebM, Matroska
Extended from VP7
Extended to VP9
Standard RFC6386
libvpx (VP8 codec library)[1][2][3]
Developer(s) Google
Initial release May 18, 2010
Stable release 1.3.0[4] / November 25, 2013; 10 years ago (2013-11-25)
Development status Active
Written in C
Operating system Unix-like (including GNU/Linux, Mac OS X), Windows
Type Video codec
License New BSD license[5]
Website webmproject.org

VP8 is a video compression format owned by Google and created by On2 Technologies as a successor to VP7.

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.[6] That same year, Google also released libvpx, the reference implementation of VP8, under a BSD license.[7]

VP8 is currently supported by Opera, Firefox, Chrome, and Chromium.[8]

History

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

After Google acquired On2 in February 2010,[11] 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.[12]

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.[13][14][15] 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,[16] from which they derived the Theora codec. In June 2010, Google amended the VP8 codec software license to the 3-clause BSD license[5][7][17] after some contention over whether the original license was actually open source.[18][19][20]

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.[25]

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.[26][27] 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.[28]

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

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

Implementations

Encoding

Currently, libvpx is the only[citation needed] software library capable of encoding VP8 video streams.[32] An encoder based on the x264 framework called xvp8 is under development by the x264 team.[33] The WebM Project hardware team in Finland released an RTL hardware encoder for VP8 that is available at no cost for semiconductor manufacturers.[34][35]

In a comparison done in May 2011, the libvpx encoder was found to be slow compared to common H.264 encoders and used up to 213% more data for the same quality video, when used in videoconferencing applications.[36]

A Video for Windows wrapper of the VP8 codec based on the Google VP8 library (FourCC: VP80) is available.[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.[42][43] TATVIK Technologies announced a VP8 decoder that is optimized for the ARM Cortex-A8 processor.[44] Marvell's ARMADA 1500-mini chipset has VP8 SD and HD hardware decoding support (used in Chromecast).[45] Intel has full VP8 decoding support built into their Bay Trail chipsets.[46] Intel Broadwell also adds VP8 hardware decoding support.[47]

Related formats

WebM

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

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 audio.[53][54] Internet Explorer 9 will support VP8 video playback if the proper codec is installed.[55] Android is WebM-enabled from version 2.3 - Gingerbread.[56] Since Android 4.0, VP8 could be read inside mkv[57] and WebM could be streamed.[58] Adobe also announced that the Flash Player will support VP8 playback in a future release.[59]

WebP

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Main article: WebP

On September 30, 2010 Google announced WebP, their new image format, on the Chromium blog.[60] 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 all of the VP8 patents it owns under a royalty-free public license.[61][62]

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."[63]

Google's claims that VP8 offers the "highest quality real-time video delivery"[64] 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.[65]

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.[66] 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 VP-8 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.[67]

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ https://code.google.com/p/webm/source/browse/CHANGELOG?repo=libvpx
  5. ↑ 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ VP8 Bitstream Specification License
  7. ↑ 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ http://www.webmproject.org/license/
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ The Free Library (2002-08-01) On2 Signs Pact With Xiph.org to Develop/Support VP3, Retrieved on 2009-08-16
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ http://www.fosspatents.com/2013/03/setback-for-googles-vp8-nokia-refuses.html
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ http://www.nvidia.com/docs/IO/116757/Tegra_4_GPU_Whitepaper_FINALv2.pdf
  39. ↑ https://plus.google.com/+WebRTCorg/posts/VXXwACq3wv6
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Engadget
  46. ↑ Anandtech Bay Trail review
  47. ↑ http://www.phoronix.com/scan.php?page=news_item&px=MTYzNDA
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ https://developer.android.com/about/versions/android-4.0-highlights.html#DeveloperApis
  58. ↑ https://developer.android.com/guide/appendix/media-formats.html
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Frequently Asked Questions, the WebM project

External links

Retrieved from "https://infogalactic.com/w/index.php?title=VP8&oldid=723128390"