New issue
Advanced search Search tips

Issue 622734 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Remove subsampling from loopStart and start()

Project Member Reported by rtoy@chromium.org, Jun 23 2016

Issue description

According to https://github.com/WebAudio/web-audio-api/issues/336 loopStart and loopEnd should be rounded to the nearest sampling point.  Chrome appears to do subsampling.

I think this snippet (for canopy) illustrates the sub-sampling that is done by chrome:

var context = new OfflineAudioContext(1, 100, 12800);
var src = context.createBufferSource();
var b = context.createBuffer(1, 3, context.sampleRate);
var d = b.getChannelData(0);
d[0] = 0;
d[1] = 1;
d[2] = 1;
src.buffer = b;
src.loop = true;
src.loopStart = 0.5 / context.sampleRate;
src.loopEnd = 2 / context.sampleRate;

src.connect(context.destination);
src.start();

The output should be the values 0 or 1, but nothing else.  Chrome currently produces 0.5 for some values.

Also check to see if start()/stop() does subsample accuracy; they should be on a frame boundary.
 

Comment 1 by rtoy@chromium.org, Oct 20 2016

See also https://github.com/WebAudio/web-audio-api/issues/915#issuecomment-248930220, which states we aren't going to change this in the spec.

Let's wait for the final resolution in the spec before doing anything about this.

Comment 2 by rtoy@chromium.org, Apr 12 2017

Status: WontFix (was: Available)
With the resolution in https://github.com/WebAudio/web-audio-api/issues/95, loopStart and loopEnd are sub-sample accurate so there's nothing for us to do.

Closing (WontFix: WAI)

Sign in to add a comment