- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Dec 2023 14:26:19 +0000
- To: public-webrtc-logs@w3.org
> Using `track.stats` to detect frames being dropped every now and then makes sense to me, what I meant by malfunctioning in this context is that we're not getting any frames at all Using `track.stats` would work well to detect both cases I think. It could be used to predict that Chrome is about to mute the track, or am I missing something? > so from the app's point of view it is muted I understand the usefulness of conveying the mal functioning information to the web app (though it is unclear whether there is agreement on what malfunctioning actually means). I do not see any benefit of conveying this information through the muted boolean compared to conveying this information in a dedicated boolean (other than the fact that this is what Chrome is doing, which is important in itself). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1866361262 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 December 2023 14:26:21 UTC