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
{{ message }}
Repository navigation
Commit 2f46fe3
Browse filesBrowse the repository at this point in the historyBrowse files
@@ -308,7 +308,7 @@ function paintFrameToCanvas(videoFrame) { ... }
308
308
// Returns an object { audioEncoder, videoEncoder }.
309
309
// Encoded outputs sent immediately to app provided muxer.
310
310
asyncfunctionbuildAndConfigureEncoders() {
311
-
// Encoded outputs immmediately sent on the wire.
311
+
// Encoded outputs immediately sent on the wire.
312
312
let audioEncoder =newAudioEncoder({ output: sendAudio, error: onCodecError });
313
313
let videoEncoder =newVideoEncoder({ output: sendVideo, error: onCodecError });
314
314
@@ -367,7 +367,7 @@ The user agent should take great care to efficiently handle expensive resources
367
367
368
368
Many codecs and encoder/decoder implementations are highly configurable. WebCodecs intends to support most of the configuration options available in codecs today to efficiently allow for advanced use cases.
369
369
370
-
A codec may be reconfigured at any time while the codec state is not "closed". Chunks/Frames passed to decode() or encode() will be decoded/encoded according to most recent preceeding call to configure().
370
+
A codec may be reconfigured at any time while the codec state is not "closed". Chunks/Frames passed to decode() or encode() will be decoded/encoded according to most recent preceding call to configure().
371
371
372
372
WebCodecs defines a set of configuration parameters that may be used with any codec. Codec-specific parameters are defined by the codec's registration in https://www.w3.org/TR/webcodecs-codec-registry/. Support for specific settings may be implementation-specific. Supported configurations may be feature-detected using the static IsConfigSupported() methods.
373
373
@@ -385,7 +385,7 @@ All of these things could be fixed by adding expanding the MSE API to explicitly
385
385
386
386
### Integrating with WhatWG Streams
387
387
388
-
An earlier design defined Encoders and Decoders as TrasformStreams from the WhatWG Streams specification. This is an appealing model; codecs are conceptually transformers with a stream of inputs and outputs. But implementing basic codec controls (configure, flush, reset) on top of Streams led to complicated designs and we were not able to hide that complexity from users (more details [here](https://docs.google.com/document/d/10S-p3Ob5snRMjBqpBf5oWn6eYij1vos7cujHoOCCCAw/edit?usp=sharing)). We've opted to instead define the codec interfaces as described above. Users can wrap these interfaces in Streams when desired.
388
+
An earlier design defined Encoders and Decoders as TransformStreams from the WhatWG Streams specification. This is an appealing model; codecs are conceptually transformers with a stream of inputs and outputs. But implementing basic codec controls (configure, flush, reset) on top of Streams led to complicated designs and we were not able to hide that complexity from users (more details [here](https://docs.google.com/document/d/10S-p3Ob5snRMjBqpBf5oWn6eYij1vos7cujHoOCCCAw/edit?usp=sharing)). We've opted to instead define the codec interfaces as described above. Users can wrap these interfaces in Streams when desired.
0 commit comments