- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Dec 2023 14:09:07 +0000
- To: public-webrtc-logs@w3.org
> If we are able to provide a good migration path via stats, that might work. [video deliveredframes](https://w3c.github.io/mediacapture-extensions/#dom-mediastreamtrackvideostats-deliveredframes) can be used with a timer-based approach to shim existing Chromium muting events for video tracks. Alternatively, shipped rvfc can already be used to detect that frames are not flowing. This probably makes video the easier one to migrate first. [audio deliveredframes](https://w3c.github.io/mediacapture-extensions/#dom-mediastreamtrackaudiostats-deliveredframes) can be used for microphone tracks, AudioWorklet might most probably expose 0 in case of missing audio frames. This approach does not require to create new APIs and allows web applications to fine tune their own detection heuristics. @guidou, do you think this migration path would work? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1853987106 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 13 December 2023 14:09:09 UTC