DescriptionVideoCapturerDelegate: Retrieve supported/in-use format(s) for constraint negotiation.
VideoCapturerDelegate uses currently a set of fixed
resolutions and frame rates for constraint negotiation.
Instead, the associated VideoCaptureImplManager is
queried first for the device format in-use; if that
in non-null, is used, otherwise the whole list of
supported formats is retrieved and used. If that last
list is also empty (platform does not support it,
such as Mac QTKit or Win DirectShow), then the by-
default set of resolutions are used.
This CL would change behaviour of scenarios in
which requested capture resolution or frame rate is
larger than the one provided by hardware, for example
Fake Video Capture Device supports only
20fps, if the Mandatory MinFps is larger than that,
the resolution algorithm will fail.
No unittests added to WebRtcGetUserMediaBrowserTest:
the unsupported format is added in
https://codereview.chromium.org/197213004/ . Rest of
the tests in the file change the gUM to request fps
between 10 and 30, since the FakeVCD supports 20, and
it would fail with a [30-30] fps range requested.
BUG=309554
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=261717
Patch Set 1 : #
Total comments: 20
Patch Set 2 : perkj@s comments #
Total comments: 6
Patch Set 3 : perkj@s comments #
Total comments: 4
Patch Set 4 : tommi@s comments. #
Total comments: 10
Patch Set 5 : perkj@s comments #
Total comments: 4
Patch Set 6 : DCHECK() and comments. #Patch Set 7 : Rebase. #Patch Set 8 : Corrected frame rate correction, min was max and opposite, in tests. #Patch Set 9 : Rebase. #Patch Set 10 : Corrected min fps from 30 to 10 in a test. #
Messages
Total messages: 31 (0 generated)
|