commit 09826b0516c6a38645c08242dad22b6f48bc05e4
author Yuri Wiitala <miu@chromium.org> Mon Mar 18 16:44:48 2019
committer Commit Bot <commit-bot@chromium.org> Mon Mar 18 16:44:48 2019
tree edf992d350bab867469d9ff40522bf4f9b668f6e
parent dbd7e7bf06ea1243fdb5da3d8fe4dd8a8ac3d825

Audio Service: Simpler SnooperNode correction FPS heuristic.

There was an oversight in the old logic's "aggressive" correction path:
During device switch-over periods, when timestamps were unstable, the
resampler was being reconfigured for each and every call to Render().
This might have been part (or all?) of the cause of higher-than-expected
CPU usage seen on some machines.

The new logic in this change, instead, reconfigures the resampler in
coaser-grained steps. The code to accomplish this is also simpler. From
testing (on my three desktops, various scenarios), synchronization seems
to generally converge much more quickly and is generally more stable.

Bug: 936835, 931225
Change-Id: I01a029bdcc37e4c92ff84a22dfaac674712cac3e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1526798
Auto-Submit: Yuri Wiitala <miu@chromium.org>
Commit-Queue: Max Morin <maxmorin@chromium.org>
Reviewed-by: Max Morin <maxmorin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#641648}