zqz/platform-external-webrtc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Leveraging the skew in API call order to a boost AEC3 signal realignment

Browse Source 
This CL resets the AEC3 realignment functionality when a significant
and persistent skew in the number of render and capture API calls is
detected.

Bug: chromium:811658,webrtc:8879
Change-Id: Ib5c727b38f427da2a7d25eac7c939a17bdaabe74
Reviewed-on: https://webrtc-review.googlesource.com/52260
Reviewed-by: Gustaf Ullberg <gustaf@webrtc.org>
Commit-Queue: Gustaf Ullberg <gustaf@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#21997}
This commit is contained in:
Per Åhgren
2018-02-13 12:59:33 +01:00
committed by Commit Bot
parent 45cc890560
commit 4712776bf4
6 changed files with 125 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/audio_processing/aec3/block_processor.cc
View File

@ -101,6 +101,7 @@ void BlockProcessorImpl::ProcessCapture(
if (!capture_properly_started_) {
capture_properly_started_ = true;
render_buffer_->Reset();
delay_controller_->Reset();
}
} else {
// If no render data has yet arrived, do not process the capture signal.
@ -213,6 +214,7 @@ void BlockProcessorImpl::BufferRender(
RenderDelayBuffer::BufferingEvent::kNone);
render_properly_started_ = true;
delay_controller_->LogRenderCall();
}
void BlockProcessorImpl::UpdateEchoLeakageStatus(bool leakage_detected) {