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
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
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No milestones specified