web api interface
ConvolverNode
The ConvolverNode interface is an AudioNode that performs a Linear Convolution on a given AudioBuffer, often used to achieve a reverb effect. A ConvolverNode always has exactly one input and one output.
[!NOTE] For more information on the theory behind Linear Convolution, see the Convolution article on Wikipedia.
| Number of inputs | 1 |
|---|---|
| Number of outputs | 1 |
| Channel count mode | "clamped-max" |
| Channel count | 1, 2, or 4 |
| Channel interpretation | "speakers" |
Constructor
ConvolverNode()- : Creates a new
ConvolverNodeobject instance.
- : Creates a new
Instance properties
Inherits properties from its parent, AudioNode.
buffer- : A mono, stereo, or 4-channel
AudioBuffercontaining the (possibly multichannel) impulse response used by theConvolverNodeto create the reverb effect.
- : A mono, stereo, or 4-channel
normalize- : A boolean that controls whether the impulse response from the buffer will be scaled by an equal-power normalization when the
bufferattribute is set, or not.
- : A boolean that controls whether the impulse response from the buffer will be scaled by an equal-power normalization when the
Instance methods
No specific method; inherits methods from its parent, AudioNode.
Examples
The following example shows basic usage of an AudioContext to create a convolver node. You will need to find an impulse response to complete the example below. See our HolySpaceCow example for a complete, applied example.
let audioCtx = new window.AudioContext();
async function createReverb() {
let convolver = audioCtx.createConvolver();
// load impulse response from file
let response = await fetch("path/to/impulse-response.wav");
let arraybuffer = await response.arrayBuffer();
convolver.buffer = await audioCtx.decodeAudioData(arraybuffer);
return convolver;
}
// …
let reverb = await createReverb();
// someOtherAudioNode -> reverb -> destination
someOtherAudioNode.connect(reverb);
reverb.connect(audioCtx.destination);
Specifications
SpecificationsStandards references are available on the canonical MDN page.
Browser compatibility
Browser compatibilityCompatibility data is available on the canonical MDN page.