- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Dec 2023 14:47:22 +0000
- To: public-webrtc-logs@w3.org
> "this source is producing silence and I don't know why" It is hard to make progress without precisely knowing how/when Chrome is firing mute events on capture tracks. I understand that Chrome's intent is to currently use mute to notify web applications that a capture track is potentially malfunctioning. Is that correct? That seems valuable information to provide to the web page. AIUI, this is one of MediaStreamTrack stats goal, though a dedicated API might make web developers life easier. For video, MediaStreamTrack stats is hopefully sufficient to detect these malfunctioning cases. For audio, it is unclear whether MediaStreamTrack stats is enough, maybe this should get fixed. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1864600892 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 December 2023 14:47:25 UTC