- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Dec 2023 10:35:06 +0000
- To: public-webrtc-logs@w3.org
> if an user unplugs the camera, it's a mute event No, it should be an ended event, the OS knows the camera is gone and most probably surfaces an error to the UA. > if the cat bites off the camera cable, it's a malfunction? The OS API will tell whether the camera capture is failing or device disappeared. If the OS is not surfacing anything but frames are not coming as **_expected_**, it would be malfunction. **_expected_** covers Chrome's detection heuristics. > today mute means "I'm not getting any frames despite the track being enabled" Mal functioning though is not about not getting any frames, as can be illustrated with BT microphones where drops may happen frequently while still getting sometime some audio. I think these two signals would best be exposed independently. For instance, chances are high that the first video frame is missed when being unmuted after being muted for mal function. I wonder whether adding a malFunctioning boolean, maybe with corresponding events might be a way forward for https://github.com/w3c/mediacapture-extensions/issues/39, plus being more explicit about what muted means for capture tracks. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/982#issuecomment-1866023353 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 10:35:09 UTC