W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2011

Re: Mozilla/Cisco API Proposal

From: Timothy B. Terriberry <tterriberry@mozilla.com>
Date: Tue, 12 Jul 2011 08:14:10 -0700
Message-ID: <4E1C64C2.6000307@mozilla.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
> could help the codec perform at its optimum). And this set could be
> irrelevant for a new generation of codecs. "audio" vs "voip" is just one
> example, and it is specific for one codec. I think the general trend also is

On the contrary, things like AGC and noise suppression are independent 
of _any_ codec (at least they are in the WebRTC stack Google 
open-sourced). Opus implements a few more things internally, but there's 
no reason in principle why those things couldn't be done outside the 
codec as well. The point is that this switch is the difference between, 
"Please actively distort the input I give you to make it sound 
'better'," vs. "Please preserve the original input as closely as 
possible," and that semantic has little to do with the actual codec.
Received on Tuesday, 12 July 2011 15:14:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 July 2011 15:14:35 GMT