Intent to Prototype: WebRTC encoded transform - Clone and Modify functions

206 views

Skip to first unread message

Harald Alvestrand

unread,

Nov 29, 2022, 3:33:07 AM11/29/22

to blink-dev

Summary

Add features to the WebRTC Encoded Transform API that allow: - Creating frames - Cloning frames - Manipulating frame metadata Background: A number of use cases have been identified that require the manipulation of WebRTC encoded media without decoding them first. These include: - Sending data that has been encoded previously - Sending data that has been received in encoded form - Receiving data in encoded form and storing it These will be supported by the new functions. Issue link: https://github.com/w3c/webrtc-nv-use-cases/issues/77

Blink component

Blink>WebRTC

Motivation

These features are needed to support use cases that involve manipulation of encoded video / audio frames beyond inline processing on a single RTCPeerConnection. Use cases: https://github.com/w3c/webrtc-nv-use-cases/issues/77

Initial public proposal

https://github.com/w3c/webrtc-encoded-transform/pull/164

TAG review

TAG review status

Pending

Risks

Interoperability and Compatibility

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

Debuggability

Is this feature fully tested by web-platform-tests?

No (not yet)

Flag name

TBA

Requires code in //chrome?

False

Tracking bug

https://crbug.com/1393964

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5116073827893248

This intent message was generated by Chrome Platform Status.

Reply all

Reply to author

Forward

0 new messages