[wpt-sync] Sync PR 15215 - Use oversampling to compute frame number
Categories
(Core :: Web Audio, enhancement, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 15215 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/15215
Details from upstream follow.
Raymond Toy <rtoy@chromium.org> wrote:
Use oversampling to compute frame number
When computing the frame number, round-off can happen such that the
resulting frame number is not the same as the original. To work
around this, use oversampling to compute the oversampled frame
number. Round that to the nearest frame, and then convert that back
to the desired integer frame number at the original sample rate.This won't always work, but should make the round-off errors much less
likely.Bug: 876917
Test: the-audiobuffersourcenode-interface/sub-sample-buffer-stitching.html
Change-Id: Id3658a986490d2aec07a382497bc24a4d99e416c
Reviewed-on: https://chromium-review.googlesource.com/c/1446869
Reviewed-by: Hongchan Choi \<hongchan@chromium.org>
Commit-Queue: Raymond Toy \<rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#629697}
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 1•6 years ago
|
||
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
Comment 6•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/aefbbbff5220
https://hg.mozilla.org/mozilla-central/rev/bd2ca5243573
Description
•