- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Oct 2021 06:18:38 +0000
- To: public-webrtc-logs@w3.org
I think it would be interesting to know an use case for this. What benefits does a developer get by using the webcodec codec instead of the webrtc built it? Missing H264/AVC with temporal scalability is an implementation issue of the browsers, but it is fully supported by the webrtc API. On the other side, we won't be able to support a WebCodec codec (let's say AAC) that the webrtc stack do not support as it has to be able to do the RTP packetization, and as you say, the bitrate control of webcodec is much loose than the required in webrtc. So I fail to see any advantage to it. -- GitHub Notification of comment by murillo128 Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/121#issuecomment-934101604 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 5 October 2021 06:18:40 UTC