WebM: The video codec of HTML 5
WebM originally comprises a container based on Matroska and the VP8 video codec developed by On2 and acquired by Google. Which then created VP9, a better codec, supported by all actors in electronics.
For audio, the free Vorbis codec is used.
Th WebM project was developed jointly by Google (which brings VP8/VP9), Mozilla and Opera and then main actors of the Web rallied to this format, that will become the codec of the HTML 5 <video> tag.
Adobe has announced a support in the Flash player.
Microsoft supports WebM next to H.264 in Internet Explorer 9 if the user adds the codec itself.
Manufacturers of graphics processing units (for computer, cameras) will implement the codec: AMD for processors and graphics units, ARM for processors for mobile, Nvidia for GPUs, Intel will includes support to WebM to its chips if the format become popular, Texas Instruments for processors, and many others ...
The leading provider of video in the world, Youtube, has already started to put online videos in the VP8 format. It is possible to see them through a search on the site with an additional parameter:
Obviously you need a compatible browser.
The question of patents
The most common codec, H.264, which is considered better than the open source theora codec is the subject of patents holds by the MPEG/LA which charges very high annual fees for streaming videos in this format.
Note that software patents that restrict utilisation of such codecs are valid only in the U.S. and South Korea.
However it is enough to prohibit the adoption of H.264 by Firefox even if an independent project was launched to a version of Firefox supporting it for the rest of the world.
With the arrival of WebM which is freely licensed, of quality close to § H.264, browsers have a free codec to implement for the <video> tag.
On May 4, 2010, the license has been redefined to separate the copyright on the code that is now under the BSD license, and the patent on the codec that keeps a clause against litigations. This clause prohibits its use for who is suing it for patent infringement.
In March 2013, Google signed an agreement with MPEG LA, which owns the rights to H.264 for patents it holds and which would eventually be used in VP8 and successors, and this free users of VP8 of any constraint when these patents.
This is not an acknowledgment that VP8 infringes on any of the patents, Google said.
VP8 is it a copy of H.264?
When Steve Jobs was asked about what are the plans of Apple with respect to WebM, he just put a link in response to a technical analysis of VP8 (the page linked is now removed).
Go to "Addendum C: Summary for the lazy" for a summary.
Is VP8 better than H.264? This comparison was made by a programmer of H.264. Is it objective?
Actually there are some contradictions in the analysis:
That’s right: this software is even older than x264!
In short, it seems to have been released too early.
VP8 is simply way too similar to H.264.
So, the codec is older than H.264, was released too early and finally it is a copy of H.264!
The site of the WebM project, to convert a video in that format, provides the FFmpeg encoder with a patch to add VP9 to the list of formats.
Since April 2015 it is used by Youtube and increases resolution video with the same bandwidth. But it will be really usable with hardware acceleration coming in graphics cards.
The VP9 SDK lets you add functions for encoding and decoding in the VP9 format to applications.
- Youtube HTML 5. Use HTML 5 on Youtube.
- Overview. (PDF).
Nokia against VP8
It announces that it does not offer FRAND license (low cost license to essential technologies) and will prosecute any VP8 user. It has already started with a lawsuit against HTC in Germany.
Nokia defends its point of view
Nokia believes that open and collaborative efforts for standardization are in the best interests of consumers, innovators and the industry as a whole. (...) As a result, we have taken the unusual step of declaring to the Internet Engineering Task Force that we are not prepared to license any Nokia patents which may be needed to implement its RFC6386 specification for VP8, or for derivative codecs.The firm said nothing about the "pay" side of the codec that is actually all that interest users who do not care if it was designed collaboratively or by a single company, provided it is fast! The Web needs for a free (of rights) codec, nothing more.