Camera track's framerate setting can be too high when using competing capabilities
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
People
(Reporter: pehrsons, Unassigned)
Details
Scenario:
Request two streams for a single camera device such that the two streams pick different native capabilities from the device. For simplicity (simpler logic) one can use resizeMode: "none" for both.
If the stream with the lower resolution picked a capability with a higher framerate than the other stream's capability, we expose the higher framerate as a setting but open the device with the higher resolution capability.
If there is a capability with the higher resolution and higher framerate, we pick that, but if the higher resolution only comes at lower framerate (e.g. due to USB bw limitations), we end up with the misleading track settings.
This may also cause unexpected results with constraints like frameRate: {min: 60} succeeding and then still only rendering, say, 30fps.
Description
•