Clarify suspend/resume on AudioContexts #361
Assignees
Milestone
Comments
|
Presumably these are not allowed or at least do nothing for an OfflineAudioContext. |
cwilso
added a commit
to cwilso/web-audio-api
that referenced
this issue
Oct 20, 2014
rogerwang
pushed a commit
to nwjs/blink
that referenced
this issue
Jan 28, 2015
WebAudio is adding a suspend()/resume() API: WebAudio/web-audio-api#361 WebAudio/web-audio-api#317 The specification is here: http://webaudio.github.io/web-audio-api/#the-audiocontext-interface http://webaudio.github.io/web-audio-api/#widl-AudioContext-suspend-Promise http://webaudio.github.io/web-audio-api/#widl-AudioContext-resume-Promise BUG=420106 TESTS=new layout tests added Review URL: https://codereview.chromium.org/697603003 git-svn-id: svn://svn.chromium.org/blink/trunk@186253 bbb929c8-8fbe-4397-9dbb-9b2b20218538
|
Merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In issue #317, there is a discussion of suspend/resume. This needs to be spec'ed out a bit more.
In particular, I think suspend and resume can be called as many times as desired without errors. The Promise returned by resume() is resolved when the audio context has started processing the audio graph again.
What happens to the context currentTime needs to explained, but I think currentTime stops advancing once suspend is called and starts advancing some time after resume has been called.
The text was updated successfully, but these errors were encountered: