New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 738323 link

Starred by 1 user
Status: Fixed
Owner:
peah@chromium.org
Closed: Jul 2017
Cc:
hlundin@chromium.org
█ tlegrand@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

The echo canceller 3 is too restrictive in the API call jitter it allows

Project Member Reported by peah@chromium.org, Jun 30 2017 
For several reasons, the AEC3 strives to minimize the internal buffer lengths. One component in that is to limit the range of jitter that can be tolerated in the call order of the render and processing API calls.

The current setting for this causes problems on some platforms.
Project Member

Comment 1 by bugdroid1@chromium.org, Jun 30 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/external/webrtc.git/+/8f9ce1d991a46e833bf637b0bb61dd52552e67fe

commit 8f9ce1d991a46e833bf637b0bb61dd52552e67fe
Author: peah <peah@webrtc.org>
Date: Fri Jun 30 10:13:21 2017

Corrected the limit on the allowed API jitter in AEC3

This CL loosens the requirement on the API jitter in APM
that can be tolerated without affecting the AEC3 performance.

BUG= webrtc:7911 , chromium:738323 

Review-Url: https://codereview.webrtc.org/2967493004
Cr-Commit-Position: refs/heads/master@{#18849}

[modify] https://crrev.com/8f9ce1d991a46e833bf637b0bb61dd52552e67fe/webrtc/modules/audio_processing/aec3/aec3_common.h

Comment 2 by peah@chromium.org, Jul 4 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment