Re: Call for Consensus: retire current ScriptProcessorNode design & AudioWorker proposal

Olivier,

I would like to propose a slight clarification of your CfC wording just to make sure we’re all on the same page in terms of how this relates to the proposal in Issue 113. In this email, I am neither objecting to the plan nor proposing a change to the spec.

You said,
> * Replace it with an AudioWorker interface, as defined in https://github.com/WebAudio/web-audio-api/issues/113#issuecomment-51493744


Strictly speaking, the referenced proposal does not replace ScriptProcessorNode with an AudioWorker interface. Rather, it replaces the old ScriptProcessorNode interface with an new ScriptProcessorNode interface. The new-style ScriptProcessorNode employs an AudioWorker interface to effect all scripted audio processing in the audio thread.

Sorry if this appears to be hairsplitting; this point is probably obvious to everyone who’s been part of the discussion, but not everyone in the WG has participated.

…Joe

Received on Friday, 8 August 2014 17:24:51 UTC