# Audio quality so bad. so much echo noise

**URL:** <https://discourse.lynckia.com/t/audio-quality-so-bad-so-much-echo-noise/251>\
**Category:** Uncategorized\
**Created:** [August 7, 2014, 1:53pm UTC](https://discourse.lynckia.com/t/audio-quality-so-bad-so-much-echo-noise/251 "2014-08-07T13:53:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hui\_zhang](https://avatars.discourse-cdn.com/v4/letter/h/cdc98d/32.png) [@hui\_zhang](https://discourse.lynckia.com/u/hui_zhang)\
**Post date:** [August 7, 2014, 1:53pm UTC](https://discourse.lynckia.com/t/audio-quality-so-bad-so-much-echo-noise/251/1 "2014-08-07T13:53:50Z")

</div>

I used this constrains

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

as this stackoverflow says

> <https://stackoverflow.com/questions/24316607/webrtc-aec-not-working-for-chrome-application>

no help

---

<div class="post-metadata">

**Author:** ![hui\_zhang](https://avatars.discourse-cdn.com/v4/letter/h/cdc98d/32.png) [@hui\_zhang](https://discourse.lynckia.com/u/hui_zhang)\
**Post date:** [August 12, 2014, 5:34am UTC](https://discourse.lynckia.com/t/audio-quality-so-bad-so-much-echo-noise/251/2 "2014-08-12T05:34:44Z")

</div>

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](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.

---

<div class="post-metadata">

**Author:** ![Jeremy\_Noring](https://avatars.discourse-cdn.com/v4/letter/j/977dab/32.png) [@Jeremy\_Noring](https://discourse.lynckia.com/u/Jeremy_Noring)\
**Post date:** [August 8, 2014, 7:30pm UTC](https://discourse.lynckia.com/t/audio-quality-so-bad-so-much-echo-noise/251/3 "2014-08-08T19:30:37Z")

</div>

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](http://stackoverflow.com/questions/24316607/webrtc-aec-not-working-for-chrome-application)
> 
> no help