Contact emails [email protected], [email protected]
Explainer https://github.com/guidou/webrtc-extensions/blob/main/encoded-source-explainer.md Specification No information provided Summary The WebRTC Encoded Transform API allows processing of encoded data from RTCPeerConnections. However, one functionality is lacking: the ability to create new encoded frames from scratch. So far, the only way to create a new frame has been to read a frame from an RTCPeerConnection. Some use cases require the ability to create frames from scratch. For example, applications that want to do encoding using WebCodecs or some other custom mechanism (eg, a WASM encoder). Blink component Blink>WebRTC>PeerConnection Web Feature ID webrtc-encoded-transform Motivation RTC Encoded Frame constructors aim to provide constructors that allow creating RTCEncodedVideoFrame and RTCEncodedAudioFrame objects from scratch, so that applications that want to perform custom encoding of RTC media using WebCodecs or other custom codecs can easily turn the result into RTC encoded frames. Initial public proposal https://docs.google.com/presentation/d/1aivu0RWAtlHpJ4dFyTPblPXGMn-ZdK9GG2xuqgcg9MQ/edit?slide=id.g3f4d73ed60e_0_0&pli=1#slide=id.g3f4d73ed60e_0_0 Goals for experimentation None Requires code in //chrome? False Tracking bug https://crbug.com/524901718 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5149398731456512?gate=6275298638299136 This intent message was generated by Chrome Platform Status. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a885478.f0bac957.7b6f1.0225.GAE%40google.com.
