New issue
Advanced search Search tips

Issue 674703 link

Starred by 1 user
Status: Verified
Owner:
rtoy@chromium.org
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Log webaudio buffer sizes on Android

Project Member Reported by rtoy@chromium.org, Dec 15 2016 
It's relatively difficult to get the hardware buffer sizes and actual callback buffer sizes on Android, so it's useful if we log this information so that it can be obtained via adb logcat.
Project Member

Comment 1 by bugdroid1@chromium.org, Dec 19 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/df4781c2f2f090d53d54e2c2b159ae2b0168f7f0

commit df4781c2f2f090d53d54e2c2b159ae2b0168f7f0
Author: rtoy <rtoy@chromium.org>
Date: Mon Dec 19 21:04:26 2016

Log WebAudio context buffer sizes on Android

It's hard to get the recommended and actual buffer sizes used for the
AudioDestination node on Android because there's such a huge range of
devices.  Log this information so that a simple "adb logcat" can
retrieve the relevant sizes.

BUG= 674703 
TEST=none

Review-Url: https://codereview.chromium.org/2583653002
Cr-Commit-Position: refs/heads/master@{#439552}

[modify] https://crrev.com/df4781c2f2f090d53d54e2c2b159ae2b0168f7f0/third_party/WebKit/Source/platform/audio/AudioDestination.cpp

Comment 2 by rtoy@chromium.org, Dec 20 2016

Status: Verified (was: Started)
A Nexus 9 now prints out that the hardware size is 128 and the callback size is 2048.

Comment 3 by rtoy@chromium.org, Dec 20 2016 

Use 'adb logcat' and search for "INFO:AudioDestination" to find the messages.
►

Sign in to add a comment