- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Sat, 10 Aug 2024 01:39:05 +0000
- To: public-webrtc-logs@w3.org
@orphis @pthatcher I think there may be two different scenarios here: 1. WebRTC encoder/decoder used for simulcast with SDP to add/remove RIDs 2. WebCodecs encoder/decoder used (e.g. for scenarios not supported in WebRTC such as mixed-codec simulcast, or spatial scalability with layer refresh, made possible by Erik's [proposed encoder API](https://github.com/w3c/webcodecs/issues/285). In scenario 1, the browser will add/drop simulcast layers. In scenario 2, the application will drop/add layers, based on the BWE and stats, and to avoid confusion on the SFM, will need to properly set RTP header extensions like the VLA and DD. Over time, scenario 2 might get more sophisticated such as support spatial scalability, custom RTCP such as [LRR](https://datatracker.ietf.org/doc/draft-ietf-avtext-lrr/). -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-rtptransport/issues/64#issuecomment-2278930076 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 10 August 2024 01:39:07 UTC