Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(534)

Issue 1208313003: audio_processing: Changed kMinDiffDelayMs from 50 to 60 ms (Closed)

Created:
5 years, 5 months ago by bjornv1
Modified:
5 years, 5 months ago
Reviewers:
CC:
webrtc-reviews_webrtc.org, Andrew MacDonald, tterriberry_mozilla.com, hlundin-webrtc, kwiberg-webrtc, aluebs-webrtc
Base URL:
https://chromium.googlesource.com/external/webrtc.git@master
Target Ref:
refs/pending/heads/master
Project:
webrtc
Visibility:
Public.

Description

audio_processing: Changed kMinDiffDelayMs from 50 to 60 ms The UMA histograms WebRTC.Audio.AecSystemDelayJump and WebRTC.Audio.PlatformReportedStreamDelayJump triggers if the jump is larger than kMinDiffDelayMs. Especially WebRTC.Audio.AecSystemDelayJump is sensitive around 50 ms differences, since the granularity is 4 ms and we can get a significant amount of hits at 52 ms. Therefore, a change to 60 ms can make the logging more robust. The effect of not logging jumps in the interval 50-60 ms is of minor importance since they are not likely to affect the AEC performance. It's when we get values from ~100 ms and above that we should be worried. Tested with a local ToT Chromium build where 52, 64 and 200 ms jumps were forced. BUG=488124 TBR=henrik.lundin@webrtc.org Committed: https://chromium.googlesource.com/external/webrtc/+/d92f2674d7e99ae69b26d434b47ea0adf14aff0c

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+3 lines, -1 line) Patch
M webrtc/modules/audio_processing/audio_processing_impl.cc View 2 chunks +3 lines, -1 line 0 comments Download

Messages

Total messages: 1 (0 generated)
bjornv1
5 years, 5 months ago (2015-07-05 08:46:17 UTC) #1
Message was sent while issue was closed.
Committed patchset #1 (id:1) manually as
d92f2674d7e99ae69b26d434b47ea0adf14aff0c (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698