- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Jul 2022 13:57:21 +0000
- To: public-webrtc-logs@w3.org
The use-case is codec-adaptive encryption schemes that can differentiate between VP8, VP9 and H264 for example, you will remember [this](https://bugs.chromium.org/p/webrtc/issues/detail?id=11886) long-standing issue. Doing a mapping in JS requires parsing SDP and keeping a copy of the SDP around and synchronized in the worker at all times. And would be nontrivial for unbundled cases where you can have more than one codec associated with a payload type (even though I bet this case isn't well defined in stats mimeType). At the sender side the information what encoder was used is readily available since the frame comes from there. At the receiver side one would assume the same but it turned out to be a bit more complicated to implement. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/140#issuecomment-1195520211 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 July 2022 13:57:23 UTC