-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a blackFrames counter to MediaStreamTrackVideoStats #144
Comments
If some OSes already expose that information, this seems ok to me. Another question is how web application would know whether the OS supports it or not. |
I'd say that it's likely helpful to mute in this case (more efficient), *if* we ensure that the app can detect the reason. |
Some OSes do for some machines. I think muting would be useful since that would give a signal to the application to stop using the less efficient frame inspection and look at the counter.
That makes sense to me. |
Ideally, an app running on a UA that would mute in this case, would not even need to run the less efficient black-frame-detection at all. Maybe we should give the app the ability to detect that. |
Correct. @youennf 's idea of not exposing the counter on systems that don't support this would be a way to detect it. |
Are we sure a browser can always tell if the OS exposes this information or not? |
I think we can expose that the OS can potentially expose this, but I guess it's camera/laptop/driver/somethingelse specific. So this is would not be a full substitute for applications detecting black frames, but a way to do it more efficiently (and perhaps more accurately) in some cases. |
VC applications currently detect black frames by inspecting the payload of each frame.
In some cases, the system can provide information that the frames are black due to a camera occlusion.
Exposing this via a stat would allow the application to implement the same functionality with lower resource usage.
cc @youennf @jan-ivar
The text was updated successfully, but these errors were encountered: