Open guidou opened 3 months ago
Hi @guidou,
I've looked at this explainer several times and now the pull request. I have to confess that I still do not understand what it is that you are trying to achieve.
Our explainer explainer suggests that you outline use cases for the proposal, starting with end user objectives. I don't see that here, just "we would like to attach metadata to encoded frames".
I see that the WebKit issue was closed as "invalid". Should we be doing the same?
こんにちは TAG-さん!
I'm requesting a TAG review of [feature name].
[One paragraph summary of idea, ideally copy-pasted from Explainer introduction]
In some use cases, a Web application would like to have control over the metadata attached to RTC encoded frames. One example would be adjusting timestamps to introduce a delay in playout. Another one would be relaying incoming encoded data from one or more input peer connections to one or more output PeerConnections use case 3.2.2, which requires encoded frame metadata to conform with the requirements of its destination. The proposed solution consists of a constructor for encoded frames that takes data from an existing frame + customized metadata.
Note: Fully supporting use case 3.2.2 also requires an additional API for inserting encoded frames into an RTCPeerConnection, for which a separate TAG review will be requested.
Further details:
Please provide feedback here (not on https://github.com/w3c/webrtc-encoded-transform/pull/223).