commit 87271e814e9c2e517d31bb496e2b628d6cc31de8
author chcunningham <chcunningham@chromium.org> Fri Mar 23 18:03:50 2018
committer Commit Bot <commit-bot@chromium.org> Fri Mar 23 18:03:50 2018
tree 2dcc5de68ed72b2365685c89719579cde9188b66
parent 79a0b39380971cfcd7ddee9e0da2305da15a743c

Add UMA for audio splicing overlapped buffer duration type

Buffer estimation paths were annotated to give info about which
estimation method was used. The decisions about how to act on estimated
buffers remain unchanged (for now).

Hopefully UMA data will show that splicing on top of buffers with
estimated duration is quite rare. This would give us confidence to
dissable this sort of splicing.

Once disabled, we could transition WebM audio buffer duration estimation
to use max-of-buffers-so-far (no longer in fear of over-triggering
splicing), which resolves the linked bug.

For buffers with duration type kConstantEstimate (all buffers had same
duration), the idea (down the road) is to treat this as if its not an
estimate at all and continue to allow splicing.

Bug: 396634
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Icbe930cf013c24b05e033fd2aa5d5b7f83bf9ac6
Reviewed-on: https://chromium-review.googlesource.com/967514
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Chrome Cunningham <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#545514}