2 ms·
There seems to be widespread confusion about WebRTC already adopting VP8/Webm as a mandatory-to-implement codec. No such decision has been made. Though the two
by ZeroGravitas 14y ago
There seems to be widespread confusion about WebRTC already adopting VP8/Webm as a mandatory-to-implement codec. No such decision has been made. Though the two furthest along implementations (Chrome and Firefox), which also happen to have about a billion users between them are both pushing VP8 which might make it a defacto standard anyway.
They (IETF WebRTC) have adopted the Opus audio codec as mandatory-to-implement, which isn't officially part of WebM (though apparently Chrome 25 can play it in that container) as it's far more suited to real-time communication than Vorbis.
For the video codec, they were going to call for consensus (basically on VP8 vs H.264) but Google mysteriously suggested that the decision be delayed on the day before it was supposed to have happened, claiming to have something in the works that would solve the whole problem to everyone's satisfaction.
My wild guess (given the fact that the VP9 encoder and decoder is now available to download from mainline codebase and is beating x264 and H.265 objectively and subjectively [1] for pre-recorded content--and I'd maybe guess that even VP8 beats H.264 for standard WebRTC use cases) is that they're working out some behind the scenes political deal with other industry partners to jump straight to VP9, either by getting all relevant parties on board regardless of patent sabre-rattling, or by working something out with patent holders to neutralise that threat. Both are a bit wild as I said, the more boring explanation is that Google feared losing the call for consensus and had something brewing to sway a few swing voters but didn't have it ready in time.
[1]: http://forum.doom9.org/showthread.php?p=1611395#post1611395 http://forum.doom9.org/showthread.php?p=1611395#post1611395