URL of the AudioWorklet module to load. The module must call
registerProcessor({@link processorName}, ...). Resolved relative to the document base URL.
OptionalonOptional handler invoked with messages your worklet posts back on its MessagePort — an
observation channel you define (e.g. audio levels). The session format (sample rate, channel
count) is available inside the worklet via the sampleRate global and the input array shape.
the data posted from the worklet via port.postMessage(...).
The name the processor was registered with inside moduleUrl via registerProcessor.
OptionalprocessorOptional data forwarded to your processor's constructor as options.processorOptions
(must be structured-cloneable). The shape is entirely defined by your own worklet — the SDK
only passes it through.
Registration for an AudioWorklet processor to install on the outgoing (local microphone) audio path. Despite the name, this is not a callback-style listener: the browser gives no access to the WebRTC audio thread, so all observation and in-place modification of the captured PCM happens inside a worklet you provide. This object just tells the SDK which worklet module to load and how to instantiate it.
The integrator supplies a worklet module (via moduleUrl) that calls
registerProcessor({@link processorName}, ...). Inside that processor'sprocess()callback the raw frames can be read, modified in place, or zeroed to substitute silence. The processed audio is what is sent to the remote peer.A complete, runnable example is wired into the JavaScript reference app.