- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:30:18 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Received on Wednesday, 11 September 2013 14:34:37 UTC
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=21777#0) by Alan deLespinasse on W3C Bugzilla. Wed, 29 May 2013 20:45:25 GMT Note that ScriptProcessorNode allows having zero outputs. It makes sense to have a ScriptProcessorNode with one input and zero outputs, for example to do some kind of analysis on the audio without producing a signal. In this case the node can't be connected to an output, but obviously it should generate events. (Though currently this doesn't seem to work, at least in the stable version of Chrome.) I'm not sure it would be wrong to generate events even if there are outputs which aren't connected, considering that the event handler may have side effects. But yes, the spec should specify this. --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/203#issuecomment-24244772
Received on Wednesday, 11 September 2013 14:34:37 UTC