New issue
Advanced search Search tips

Issue 773541 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug



Sign in to add a comment

AEC3 fails to detect the echo path delay in reverberant environments with moderate echo return loss

Project Member Reported by peah@chromium.org, Oct 11 2017

Issue description

For some setups located in reverberant rooms AEC3 fails to detect the echo path delay. In particular this seems to happen in setups where the echo is relatively weak in the microphone signal.
 

Comment 1 by peah@chromium.org, Oct 11 2017

Labels: OS-Android OS-Chrome OS-iOS OS-Linux OS-Mac OS-Windows
Labels: -OS-iOS
Is this finished?

Comment 5 by peah@chromium.org, Oct 19 2017

Labels: Merge-Request-63
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 20 2017

Labels: -Merge-Request-63 Hotlist-Merge-Approved Merge-Approved-63
Your change meets the bar and is auto-approved for M63. Please go ahead and merge the CL to branch 3239 manually. Please contact milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by gov...@chromium.org, Oct 20 2017

Please merge your change to M63 branch 3239 by 4:00 PM PT today, Friday so we can take it in for next M63 dev release. Thank you.

Comment 8 by peah@chromium.org, Oct 20 2017

Sorry, my mistake. This actually made it into M63, so no merge needed.

Comment 9 by peah@chromium.org, Oct 20 2017

Labels: -Hotlist-Merge-Approved -Merge-Approved-63
Status: Fixed (was: Assigned)

Sign in to add a comment