OpusEncoderConfig `signal` and `application` parameters

Category: Multimedia
Type: Chromium catches up
Status: Enabled by default (Chrome 126)
Intent stage: None

Summary

`OpusEncoderConfig.signal` and `OpusEncoderConfig.application` were recently added to the WebCodecs spec [1]. Both parameters are mapped directly to implementation specific encoder knobs. These allow web authors to provide hints as to what type of data is being encoded, and in which context the data is being used. `signal` can be one of {"auto", "music", "voice"}. It configures the encoder for the best performance in encoding the specified type of data. `application` can be one of {"voip", "audio", "lowdelay"}. It configures the encoder to favor speech intelligibility, faithful reproduction of the original input, or minimal latency. [1] : https://github.com/w3c/webcodecs/pull/777

Standards & signals

Specification: https://w3c.github.io/webcodecs/opus_codec_registration.html#dom-opusencoderconfig-signal
Firefox: Positive — Spec change approved by Mozilla representative. For an almost identical feature, Mozilla said the "request for standards position" was not warranted, as they were active spec participants: https://github.com/mozilla/standards-positions/issues/837#issuecomment-1614666364
Safari: No signal — Review from Safari was requested on the spec change.
Web developers: No signals

View on chromestatus.com