This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
ScriptProcessorNode interface is an
AudioNode audio-processing module that is linked to two buffers, one containing the input audio data, one containing the processed output audio data. An event, implementing the
AudioProcessingEvent interface, is sent to the object each time the input buffer contains new data, and the event handler terminates when it has filled the output buffer with data.
The size of the input and output buffer are defined at the creation time, when the
BaseAudioContext.createScriptProcessor method is called (both are defined by
bufferSize parameter). The buffer size must be a power of 2 between
16384, that is
16384. Small numbers lower the latency, but large number may be necessary to avoid audio breakup and glitches.
If the buffer size is not defined, which is recommended, the browser will pick one that its heuristic deems appropriate.
|Number of inputs||
|Number of outputs||
|Channel count mode||
Inherits properties from its parent,
- Returns an integer representing both the input and output buffer size. Its value can be a power of 2 value in the range
No specific methods; inherits methods from its parent,
Listen to these events using
addEventListener() or by assigning an event listener to the
oneventname property of this interface:
- Fired when an input buffer of a
ScriptProcessorNodeis ready to be processed.
Also available via the
onaudioprocessevent handler property.
BaseAudioContext.createScriptProcessor() for example code.
Since the August 29 2014 Web Audio API specification publication, this feature has been deprecated. It is no longer on track to become a standard.
BCD tables only load in the browser