Comments on: Let the WebRTC Codec Wars Begin! https://bloggeek.me/webrtc-codec-wars/ The leading authority on WebRTC Wed, 29 May 2024 13:16:36 +0000 hourly 1 By: Tsahi Levent-Levi https://bloggeek.me/webrtc-codec-wars/#comment-116271 Wed, 08 Aug 2012 17:44:34 +0000 http://bloggeek.me/?p=997#comment-116271 In reply to Dave Michels.

Dave,
While this might be true, Google is lacking two important browsers: IE and Safari. Without them, there’s just so much the can achieve.
Hopefully, we will end up with an alignment of a single video codec instead of multiple options.

]]> By: Dave Michels https://bloggeek.me/webrtc-codec-wars/#comment-116270 Wed, 08 Aug 2012 17:35:00 +0000 http://bloggeek.me/?p=997#comment-116270 There are standards and defacto standards. Google and others will just release WebRTC (I think they already have) with VP8 and will take off while the standards bodies are busy researching the solution.

]]> By: Tsahi Levent-Levi https://bloggeek.me/webrtc-codec-wars/#comment-116269 Wed, 08 Aug 2012 05:48:24 +0000 http://bloggeek.me/?p=997#comment-116269 In reply to Randell Jesup.

Randell,

Thanks for the update!
I am sure there are those who wish to see other voice codecs as the ones selected instead of Opus – I even have an idea of a few such vendors 🙂
It is exciting to see this move forward and I do hope you nail down the video codec soon – be it VP8 or H.264 – just not both, and not fight over it for too much time.

]]> By: Randell Jesup https://bloggeek.me/webrtc-codec-wars/#comment-116268 Wed, 08 Aug 2012 05:37:55 +0000 http://bloggeek.me/?p=997#comment-116268 The IETF rtcweb working group selected Opus + G.711 as mandatory-to-implement audio codecs, by a quite strong consensus (and the only alternative that got support was just Opus). Why G.711? To quote from the meeting “Oh my goodness, why wouldn’t you?”

The video codec issue will be brought up again at the next IETF meeting, there was no attempt to resolve it at this one.

Mozilla (not surprisingly) supports Opus+G.711 and VP8.

]]>