You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chrome seems to perform the same non-zero checks for an AudioEncoderConfig and AudioDecoderConfig. But as far as I can tell they are not covered by a WPT.
The checks for an AudioEncoderConfig were added here: #780.
The text was updated successfully, but these errors were encountered:
Yeah, we talked about harmonizing implem and tests in an issue not too long ago, but I can't find it.
For decoding, it's not 100% required to provide the sample-rate and the channel count, sometimes it's possible to determine them from the bit stream. Sometimes it is required though.
Right now a valid
AudioEncoderConfig
needs to have anumberOfChannels
and asampleRate
property greater than zero.https://w3c.github.io/webcodecs/#valid-audioencoderconfig
A similar check does not exist to validate an
AudioDecoderConfig
.https://w3c.github.io/webcodecs/#valid-audiodecoderconfig
Chrome seems to perform the same non-zero checks for an
AudioEncoderConfig
andAudioDecoderConfig
. But as far as I can tell they are not covered by a WPT.The checks for an
AudioEncoderConfig
were added here: #780.The text was updated successfully, but these errors were encountered: