New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 782971 link

Starred by 1 user
Status: Fixed
Owner: ----
Closed: Nov 2017
Cc:
█ sandeepkumars@chromium.org
nyerramilli@chromium.org
█ msrchandra@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

AudioContext with latencyHint "playback" is very choppy with mutli-channel opus audio file on Android

Reported by james.jd...@gmail.com, Nov 9 2017 
Steps to reproduce the problem:
Create an AudioContext with {latencyHint:"playback"} to hear choppy audio. Remove hint option entirely to hear smooth playback. Multichannel opus data may or may not be a factor in this bug.

What is the expected behavior?
Expected latencyHint:"playback" should increase latency to allow for smoother playback; opposite effect seems to occur.

What went wrong?
Supplying latencyHint:"playback" option produces the opposite of its intended purpose, making audio playback choppy.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 61.0.3163.98  Channel: stable
OS Version: 7.0
Flash Version: 

Enjoy the single-file reproducible test case :).

I encoded a small sample of an 8-channel opus audio file in a data-uri which is the main driver of the file size being 476K uncompressed.

Click the play control on the <audio> element.

Comment out line 14 `opts.latencyHint = "playback";` to omit the latencyHint option to hear the smooth playback audio (default case) on android. The supplied version includes the latencyHint to demonstrate the bug.
test.html.gz
345 KB Download

Comment 1 by pnangunoori@chromium.org, Nov 9 2017

Labels: Needs-triage-Mobile

Comment 2 by sandeepkumars@chromium.org, Nov 9 2017

Cc: msrchandra@chromium.org nyerramilli@chromium.org sandeepkumars@chromium.org
Labels: Triaged-Mobile Needs-Feedback
@james.jdunne: Thanks for the report.

Could you please upgrade your Chrome to the latest stable #62.0.3202.84 and check and let us know as issue is not seen in latest stable #62.0.3202.84?

Thanks!!

Comment 3 by james.jd...@gmail.com, Nov 9 2017 

The issue appears to be resolved in 62. Thanks
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 9 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by rtoy@chromium.org, Nov 9 2017

Status: Fixed (was: Unconfirmed)
Per c#3, closing as fixed.
►

Sign in to add a comment