https://webrtchac
om/video-constraints-2/
https://webrtchacks.com/how-to-figure-out-webrtc-camera-resolutions/
|
Try
Updated (Sep 26, 2013): According to this page; you can set following resolutions (min/max width/height):
Or Maybe:
|
分辨率最高的是WVGA:800×480 VGA为标准分辨率:640×480 WVGA 分辨率:800×480 WQVGA 分辨率:480×320 QVGA分辨率:320×240 D1 分辨率:720×576 CIF 分辨率: 352×288 QCIF 分辨率:176×144
Openwebrtc:
QCIF and QVGA are unusable and result in an oddly shaped black frame on the receiving end in Chrome.
CIF works and reduces the latency to 0.5 s or so initially, however latency gradually increases to several seconds and longer.
getUserMedia() constraints
As covered in the What happens when there’s missing media sources? post, getUserMedia() takes a constraints object. The object, as defined in the getUserMedia()W3C specification looks like this:
The spec allows mandatory and optional constraints for both minimum and maximums on:
| Object | What it does | Value options |
| Height | Specifies the video source height | Min and Max of an integer |
| Width | Specifies the video source width | Min and Max of an integer |
| FrameRate | specify how many frames to send per second | Min and Max of an integer |
| aspectRatio | height divided by width – usually 4/3 (1.33333333333) or 16/9 (1.7777777778) | Min and Max of an decimal |
| facingMode | Select the front/user facing camera or the rear/environment facing camera if available | Which camera to choose – currently user, environment, left, or right |
In addition to turning audio and video on/off all together, in practice minHeight, minWidth, maxHeight, and maxWidth variables are the most widely supported:
I have also seen reference to others that could theoretically be passed down to the libjingle media engine that powers WebRTC. These are out of scope for my camera resolution project, so I did not experiment with them.
390



被折叠的 条评论
为什么被折叠?



