- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Nov 2024 08:48:51 +0000
- To: public-webrtc-logs@w3.org
CSRC polling is widely deployed to convey participant information when the same receivers are used to receive different audio/video at different point in the call, e.g: - For "virtual audio ssrc" you need to know who is speaking in order to display the audio meter on the right participant video tile. - For "virtual video ssrc" you need to know who is in the video in order to display the correct participant name on the correct video tile. Since both of these things can quickly change, this is timing sensitive. Today's API forces apps to poll at high frequency, which is neither ergonomic or efficient. > I'm reluctant to introduce any new API that works around that functionality until Chrome fixes it I'd like to decouple the need for "onunmute" with the need for the above described use case. So @jan-ivar, assuming we had already implemented "onunmute" and assuming developers still wanted an event for CSRC changes, would you be for or against adding it? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/230#issuecomment-2482304402 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 November 2024 08:48:52 UTC