W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] (AudioProcessingEventScheduling): AudioProcessingEvent scheduling (#85)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:13 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/85@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17350](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17350) Tue, 05 Jun 2012 11:41:13 GMT
> Reported by Philip J├Ągenstedt
> Assigned to 

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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/85
Received on Wednesday, 11 September 2013 14:29:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC