Issue 11418017: Reduce high latency input buffers to 1.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 11418017: Reduce high latency input buffers to 1. (Closed)

Created:
8 years, 1 month ago by DaleCurtis

Modified:
8 years, 1 month ago

Reviewers:
scherkus (not reviewing)

CC:
chromium-reviews, feature-media-reviews_chromium.org, sail+watch_chromium.org, viettrungluu

Base URL:
svn://svn.chromium.org/chrome/trunk/src

Visibility:
Public.

More Reviews

Description

Reduce high latency input buffers to 1. Multiple buffers lead to trampling input data which is in the process of being transmitted across the shared memory. Since this API was never intended for low latency usage, clients should instead use a larger buffer size. At least 2048 @ 44.1kHz (Flash) and 1600 at 16kHz (speech recognizer). vtl will land a fix to flash along side this change to move it off of the RecommendSampleCount() method to a hard coded 2048 frame buffer. NOTRY=true BUG=157613 TEST=input is clear and crisp w/ flash @ 2048 buffer. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=168106