libvpx

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

libvpx
Screenshot
Vpxenc --verbose.svg
Developer(s)Google
Initial releaseMay 18, 2010
Stable release
1.7.0[1] / January 4, 2018; 10 months ago (2018-01-04)
Repository Edit this at Wikidata
Written inC, assembly
Operating systemUnix-like (including Linux, FreeBSD and Mac OS X), Windows
TypeVideo codec
LicenseNew BSD license
WebsiteOfficial website

libvpx is a free software video codec library from Google and the Alliance for Open Media (AOMedia). It serves as the reference software implementation for the video coding formats VP8 and VP9, and for AV1 a special fork named libaom that was stripped of backwards compatibility.

As free software it is published also in source code under the terms of the revised BSD license. It ships with the commandline tools vpxenc/aomenc and vpxdec/aomdec that build on its functionality.

History[edit]

libvpx originates from the video codec company On2 Technologies that sold its first software codec in mid-90s.

libvpx was released as free software by Google in 2010 after the acquisition of On2 Technologies for an estimate of over 120 million US dollars.[2]

In June 2010, Google amended the VP8 codec software license to the 3-clause BSD license[3][4][5] after some contention over whether the original license was actually open source.[6][7][8]

Google was criticised for dumping untidy code with bad documentation for the initial release of libvpx and developing behind closed doors without involving the community in the process.[9] The development process was opened after the release of VP9.

Preliminary support for VP9 was added to libvpx on June 17, 2013. It was officially introduced with the release of version 1.3 on December 2, which also supports lossless compression.[10]

In April 2015, Google released a significant update to its libvpx library, with version 1.4.0 adding support for encoding VP9 with 10-bit and 12-bit bit depth, 4:2:2 and 4:4:4 chroma subsampling (VP9 profiles 1, 2, and 3), and VP9 multithreaded decoding/encoding.[11]

Versions 1.5 (November 2015) and 1.6 (July 2016) delivered significant speedups, both for encoding and decoding.

Features[edit]

libvpx implements single-pass and two-pass encoding modes, with either bitrate or quality target settings.

libvpx offers an asymmetric codec – with encoding taking much longer than decoding – and options for configuring encoding expense independently from decoding complexity. A lookahead of up to 25 frames can be configured, which improves compression efficiency but introduces latency and thereby hurts real-time performance.

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.

libvpx supports Rec. 601, Rec. 709, Rec. 2020, SMPTE-170, SMPTE-240, and sRGB color spaces.

Performance[edit]

Bitrate control in the single-pass mode is considered broken and doesn't offer effective control over the target bitrate.[12][13] Bitrate control is considered bad even for the constant quality mode.[14]

At high resolutions (e.g., UHD) VP9 encoded by libvpx for VOD applications provides a significant improvement over H.264 encoded by x264.[15] HEVC encoded by x265 may achieve even better quality,[15] but the royalty-free nature of VP9 makes it a compelling option for delivering high resolution video on supported platforms.

Decoding performance is relatively slow, partially in order to keep the code base easier to maintain.[16] Compared to the initial release of libvpx, ffvp8 from the FFmpeg project improved performance by 22 to over 66%.[9] In 2016, alternative VP9 decoders still achieved 25–50% faster decoding.[12][17]

Technology[edit]

libvpx is written in C and assembly language. It does not have complete SIMD coverage as of 2015.[16]

Usage[edit]

libvpx is used by major OTT video services including YouTube, Netflix, Amazon, JW Player, Brightcove, and Telestream, among which are the biggest sources of internet traffic with Netflix alone accounting for nearly a third of all internet traffic in the United States as of 2017.[18][19][20]

There are alternatives for decoding VP8 and VP9, both commercial and closed source as well as open source. For encoding there are only commercial alternatives and some unfinished experimental software for VP8 including xvp8 as of 2016.

References[edit]

  1. ^ "CHANGELOG - webm/libvpx - Git at Google". chromium.googlesource.com.
  2. ^ "Google Closes On2 Technologies Acquisition". investor.google.com. Archived from the original on June 5, 2010. Retrieved 24 July 2017.
  3. ^ "Changes to the WebM Open Source License". Retrieved 2010-06-04.
  4. ^ "Software License". Retrieved 2010-06-04.
  5. ^ Koleszar, John (2010-06-04). "LICENSE: update with latest text". WebM VCS repository.
  6. ^ Kerner, Sean Michael (2010-05-25), Is VP8 open source?, InternetNews
  7. ^ Metz, Cade (2010-05-24), Google open codec 'not open,' says OSI man, The Register
  8. ^ Phipps, Simon (2010-05-24), WebM: Missing The Assurances Open Source Needs?, ComputerworldUK[permanent dead link]
  9. ^ a b Fiona Glaser, 23 July 2010: Announcing the world's fastest VP8 decoder: ffvp8
  10. ^ Michael Larabel (Phoronix), 28. November 2013: Libvpx 1.3.0 "Forest" Supports VP9. New Enhancements
  11. ^ Michael Larabel (2015-04-03). "libvpx 1.4.0 Brings Faster VP9 Encode/Decode". Phoronix. Retrieved 2015-04-03.
  12. ^ a b Jan Ozer, Juni 2016: VP9 Finally Comes of Age, But Is it Right for Everyone?
  13. ^ Dan Grois, Detlev Marpe, Tung Nguyen, Ofer Hadar, "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 (San Diego, California) 9217, doi:10.1117/12.2073323, http://proceedings.spiedigitallibrary.org/proceeding.aspx?articleid=1910369 
  14. ^ "VP9 Encoding Guide - wiki". wiki.webmproject.org.
  15. ^ a b Cock, Jan De; Mavlankar, Aditya; Moorthy, Anush; Aaron, Anne (2016-09-27). "A large-scale video codec comparison of x264, x265 and libvpx for practical VOD applications". 9971. International Society for Optics and Photonics: 997116. doi:10.1117/12.2238495.
  16. ^ a b Ronald Bultje (FFmpeg): VP9 encoding/decoding performance vs. H.264/HEVC, presentation from the VideoLAN Dev Days 2015 in Paris, France
  17. ^ "The world's fastest VP9 decoder: ffvp9 - Ronald S. Bultje". blogs.gnome.org.
  18. ^ Jan Ozer (May 24, 2016): Netflix Discusses VP9-Related Development Efforts
  19. ^ Sandvine: The Global Internet Phenomena Report: 1H 2013
  20. ^ Spangler, Todd (2016-06-22). "Netflix Chews Up Less Bandwidth, as Amazon Video Streaming Surges". Variety. Retrieved 2017-12-20.