sprang 40217c3718 Initial rate allocation should not use fps = 0
A recent cl (https://codereview.webrtc.org/2510583002) introduced an
issue where the initial rate allocation (call to VideoBitrateAllocator
and any associated temporal layers) uses framerate = 0 fps. This may
cause issues, including having the rate control in ScreenshareLayers
ramp up too slowly.

This CL make the initial call use VideoCodec.maxFramerate as framerate.
Also expanded unit tests.

BUG=webrtc:6301

Review-Url: https://codereview.webrtc.org/2513383002
Cr-Commit-Position: refs/heads/master@{#15166}
2016-11-21 13:42:04 +00:00
..
2016-11-16 19:11:38 +00:00
2016-11-16 19:11:38 +00:00
2016-11-15 08:58:06 +00:00
2016-09-10 05:40:34 +00:00
2016-11-16 19:11:38 +00:00
2016-11-15 08:58:06 +00:00
2016-11-15 08:58:06 +00:00
2016-11-15 08:58:06 +00:00