This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17350 - (AudioProcessingEventScheduling): AudioProcessingEvent scheduling
Summary: (AudioProcessingEventScheduling): AudioProcessingEvent scheduling
Status: CLOSED WONTFIX
Alias: None
Product: AudioWG
Classification: Unclassified
Component: Web Audio API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: TBD
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 11:41 UTC by Philip Jägenstedt
Modified: 2014-10-28 17:18 UTC (History)
1 user (show)

See Also:

Attachments

Description Philip Jägenstedt 2012-06-05 11:41:13 UTC 
Audio-ISSUE-59 (AudioProcessingEventScheduling): AudioProcessingEvent scheduling [Web Audio API]

http://www.w3.org/2011/audio/track/issues/59

Raised by: Philip Jägenstedt
On product: Web Audio API

How close to AudioContext.currentTime is AudioProcessingEvent.playbackTime expected to be when the audioprocess event is fired?

May a compliant implementation fire events arbitrarily far ahead of time in an arbitrary order? Presumably Web authors will make assumptions that the event is fired as close as possible to "now", so the spec should require this.
Comment 1 Olivier Thereaux 2014-10-28 17:15:06 UTC 
Web Audio API issues have been migrated to Github. 
See https://github.com/WebAudio/web-audio-api/issues
Comment 2 Olivier Thereaux 2014-10-28 17:18:06 UTC 
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.