mediacapture-extensions
mediacapture-extensions copied to clipboard
w3c
Extensions to Media Capture and Streams by the WebRTC Working Group
From https://github.com/w3c/mediacapture-main/issues/669#issuecomment-605114117: > @henbos Specifically on removing required constraints, note that Chrome [today implements](https://jsfiddle.net/jib1/2pnmjz57/) [`info.getCapabilities()`](https://w3c.github.io/mediacapture-main/getusermedia.html#input-specific-device-info) which gives the site capability information about _all_ devices after gUM. > > That API...
I couldn't find anything in the specification regarding the origin that a track is attributed to. I suspect that all browsers have settled on a model that is sensible, but...
Current approach suggests to test all possible constraint combinations and use the combination that has the lowest fitness distance. This is difficult to implement and provides sometimes interesting but maybe...
As supplement to a previous ticket I posted a broader API suggestions, and it was suggested these would be a good 'issue' in their own right for discussion. I've tried...
Visit a new web site in Chrome, Safari, or Edge, & do something requiring camera + microphone: They'll say the site wants to _"use your camera and microphone"_, without saying...
Current specification supports channelCount https://rawgit.com/w3c/mediacapture-main/master/getusermedia.html#def-constraint-channelCount but this is not sufficient when the track contains more than two channels. In those cases, a channelLayout is also required [1]. [1] https://en.wikipedia.org/wiki/Surround_sound
