- From: Russell McClellan <russell@motu.com>
- Date: Fri, 26 Apr 2013 16:29:20 -0400
- To: "public-audio@w3.org WG" <public-audio@w3.org>
On Apr 25, 2013, at 1:18 PM, bugzilla@jessica.w3.org wrote: > - Corollary: need to document (if this is true) that currentTime advances > monotonically by a time quantum equal to the block size, as each block is > synthesized. This is important because if true it implies that > ScriptProcessingNode JS code may consult currentTime instead of > event.playbackTime, and that the latter is no longer needed since it's always > equal to currentTime. As a developer, I don't understand this idea at all. ScriptProcessorNodes may (and do in all current implementations) have additional latency above and beyond the rest of the audio graph. That is, the global "block currently being processed" (whatever that means) will in general not have any defined relationship to the playback time of the current script processor block. Doing as you suggest here would make it impossible for developers to synchronize javascript processing to other audio graph processing. Thanks, -Russell
Received on Friday, 26 April 2013 20:30:14 UTC