18334 2012-07-19 16:18:42 +0000 Asynchronous write 2012-10-24 09:16:46 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified All All CLOSED INVALID P2 normal TBD 1 jussi.kalliokoski crogers olivier.thereaux public-audio oldest_to_newest 71159 0 jussi.kalliokoski 2012-07-19 16:18:42 +0000 I may be wrong, but it seems to me that currently the JavaScriptNode has no way of filling the buffers asynchronously. I suggest we adopt the way that Robert's proposal did the callbacks, having a write method on the event. Allowing asynchronous writes makes sense in an environment like JS where most of the external operations are asynchronous. Also, for example if we define a DSP library that supports things such as convolution, it would be ideal for it to provide asynchronous versions of the calls as well, to make it more natural to the async flow of JS programs, not to mention that you could do concurrent overlap-add things. So for example (very simplified): var l = 2048 customNode.onaudioprocess = function (e) { var buffer = new Float32Array(l) oscillator.fillBufferAsync(buffer, function () { e.writeAudio(buffer) }) } This would also allow one to write data ahead of time. 75399 1 crogers 2012-10-05 20:23:32 +0000 I think we effectively already have an async write() in AudioBufferSourceNode.start() 75423 2 jussi.kalliokoski 2012-10-05 22:32:13 +0000 (In reply to comment #1) > I think we effectively already have an async write() in > AudioBufferSourceNode.start() That's not suitable for continuous asynchronously generated audio, but this feature is actually probably better off as custom JS buffer handling. Closing. 77028 3 olivier.thereaux 2012-10-24 09:16:46 +0000 Seeing no objection to the resolution as invalid in over 2 weeks, closing.