- From: youennf via GitHub <noreply@w3.org>
- Date: Wed, 04 Jun 2025 19:22:18 +0000
- To: public-webrtc-logs@w3.org
I think we can rediscuss this topic at a WebRTC WG meeting given this new information. The proposal could be something like: - When applyConstraints promise gets resolved, only samples generated for the new configuration are submitted to track sinks. It is ok for some samples of the new configuration to have already been submitted. - When configurationchange event fires, only samples generated for the newly changed configuration are submitted to track sinks. It is ok for some samples of the newly changed configuration to have already been submitted. - Similarly, after the `onmute` event fires, no sample is submitted to track sinks as long as the source stays muted. As of the `unmute` event, I would be tempted to not require synchronization until we have a usecase. - Testing done with MSTP. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/1017#issuecomment-2941176896 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 June 2025 19:22:19 UTC