3 ms·
WebRTC is being develop by IETF and W3C both of whom have very strong preferences for royalty-free (and otherwise RAND-Z/RF) standards. Why would you imagine th
by ZeroGravitas 14y ago
WebRTC is being develop by IETF and W3C both of whom have very strong preferences for royalty-free (and otherwise RAND-Z/RF) standards. Why would you imagine they would pick an MPEG codec?
Maybe the low-delay wideband voice and audio codec also developed by IETF under the same requirements (both technical and royalty-wise) would fit better?
And, on the topic at hand, have Microsoft made any public statement about their support for that codec, despite the fact that it was co-developed by their Skype purchase? Only vague murmurings that the alternative standard discussed here shouldn't be "tied to a single codec". Note the masterful misdirection that would make you thing that WebRTC was "tied to a single codec" when in fact you can use any codec you like, you just have to support Opus (best in class, yet RF) and G.711 (old and busted for legacy interop) to help ensure interoperability.
The fact that the simple logic of this seems somehow underhand to you is a testament to the great political job that Microsoft, Apple, Nokia and others have done in the web codec arena where a codec, which could never be adopted under W3C rules, has come to seem like the obvious choice when really it was a bold attempt to subvert the W3C into not specifying a royalty-free codec so that a royalty-encumbered de-facto standard of their choice would fill the gap that was left.