The AEC3 handling of saturated echoes is overly conservative |
||||||
Issue descriptionAEC3 includes code for handling the case when the echoes are saturated. That code is, however, fairly defensive and quite conservative regarding the echo behavior during saturated echoes. The effect of this is reduced echo canceller transparency.
,
Apr 20 2018
I would like to merge this to M67 since it was not included in the rolled version of WebRTC that went into M67. The code has been active in canary for 10 days and performs well.
,
Apr 21 2018
Your change meets the bar and is auto-approved for M67. Please go ahead and merge the CL to branch 3396 manually. Please contact milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), kbleicher@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2018
Pls merge your change to M67 branch 3396 by 1:00 PM PT, Monday (04/23) so we can pick it up next M67 Dev/Beta release. Thank you.
,
Apr 23 2018
Thanks! The CL has now been merged to M67.
,
Apr 23 2018
Pls point the CL link here for M67 merge here. Thank you.
,
Apr 23 2018
The WebRTC merge was done on the CL: https://webrtc-review.googlesource.com/c/src/+/71742 A link to this issue was included in the CL description.
,
Apr 23 2018
Removing "Merge-Approved-67" per comments #5 and #7. Thank you.
,
Jun 7 2018
[bulk-edit: disregard if N/A] Can the owner please set milestone to this bug if applicable?
,
Jun 8 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by peah@chromium.org
, Apr 20 2018