Audio quality so bad. so much echo noise

I used this constrains

“audio”: {
“mandatory”: {
“googEchoCancellation”: “true”,
“googAutoGainControl”: “true”,
“googNoiseSuppression”: “true”,
“googHighpassFilter”: “true”
},

as this stackoverflow says

no help

Yes it could be fix by setting control pannel --> sound -->
microphone --> enable AEC and BF

and the quality is quite fine.

But that is not the webrtc way, and it need custom to do settings. not
continent.

could you make the goog prefix parameters take effect.

在 2014年8月9日星期六UTC+8上午3时30分38秒,Jeremy Noring写道:>

On Thursday, August 7, 2014 7:53:51 AM UTC-6, hui zhang wrote:

I used this constrains

“audio”: {
“mandatory”: {
“googEchoCancellation”: “true”,
“googAutoGainControl”: “true”,
“googNoiseSuppression”: “true”,
“googHighpassFilter”: “true”
},

as this stackoverflow says

http://stackoverflow.com/questions/24316607/webrtc-aec-not-working-for-chrome-application

no help

I’d post the bug in the webrtc project on google code. AEC is a part of
webrtc, not licode.

I have seen–on windows boxes–times where the sound driver itself has
crappy AEC that interferes with echo cancellation.

I’d post the bug in the webrtc project on google code. AEC is a part of
webrtc, not licode.

I have seen–on windows boxes–times where the sound driver itself has
crappy AEC that interferes with echo cancellation.On Thursday, August 7, 2014 7:53:51 AM UTC-6, hui zhang wrote:

I used this constrains

“audio”: {
“mandatory”: {
“googEchoCancellation”: “true”,
“googAutoGainControl”: “true”,
“googNoiseSuppression”: “true”,
“googHighpassFilter”: “true”
},

as this stackoverflow says

http://stackoverflow.com/questions/24316607/webrtc-aec-not-working-for-chrome-application

no help