Developers › A Journal from Behind the Trenches
VP8 (WebM) submitted to the IETF
Earlier this month, it seems that VP8 was submitted as an informational document to the IETF:
VP8 Data Format and Decoding Guide
By J. Bankoski, P. Wilkins, Y. Xu of Google, Inc.
Naturally, Google's irrevocable, royalty-free license still applies.
If you are not familiar with the difference between VP8 and WebM, VP8 is the actual video compression format, while WebM is a multimedia container format based on Matroska, which consists of VP8 for video, Vorbis for audio.
It's important to note that this doesn't necessarily make VP8 a standard (at least yet), since informational IETF documents can basically be "anything".
VP8 Data Format and Decoding Guide
By J. Bankoski, P. Wilkins, Y. Xu of Google, Inc.
Naturally, Google's irrevocable, royalty-free license still applies.
If you are not familiar with the difference between VP8 and WebM, VP8 is the actual video compression format, while WebM is a multimedia container format based on Matroska, which consists of VP8 for video, Vorbis for audio.
It's important to note that this doesn't necessarily make VP8 a standard (at least yet), since informational IETF documents can basically be "anything".
Readers' comments 7
Left under the original article, as archived.
About this article
| Published in | A Journal from Behind the Trenches |
|---|---|
| Date | January 20, 2011 |
| Author | Haavard |
| Tags | ietf, webm, vp8, google |
| Original | Internet Archive |
João EirasThursday, January 20, 2011 4:43:16 PM
Tenno SeremelThursday, January 20, 2011 6:49:46 PM
FransThursday, January 20, 2011 7:56:50 PM
Originally posted by Tenno Seremel:
Clearly.
Cutting SpoonThursday, January 20, 2011 9:55:24 PM
Given the current bugs in x86 VP8 Chroma, and certain other incorrectable implementation flaws, I wonder how much complexity is required to emulate these flaws in a dedicated decoder logic?
Still, with even this much it should be possible for most browsers to view WebM content before the end of the year. Market penetration of embedded VP8 decoders will show us just how affordable the new chips really are.
DillonFriday, January 21, 2011 6:00:37 AM
Originally posted by xErath:
One of the things that makes it difficult to write a 3rd party encoder, or to even be sure the code you're submitting for an update to the reference encoder is bitstream-correct
Ruarí ØdegaardFriday, January 21, 2011 7:22:24 AM
Cutting SpoonFriday, January 28, 2011 1:58:13 AM