commit | e73f847bc53b227cb7cf88f7f9d1ba19c3d86108 | [log] [tgz] |
---|---|---|
author | Zijie He <zijiehe@chromium.org> | Thu Oct 19 01:25:08 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Oct 19 01:25:08 2017 |
tree | dc915c977ab2a4bec3e6486cef13fd6edb68f6da | |
parent | 1de4bccb0ea32f5c5bd82d7d48553c11f88659a3 [diff] |
[Chromoting] Set min-bitrate of video channel to 0 According to SendSideBandwidthEstimation, https://cs.chromium.org/chromium/src/third_party/webrtc/modules/bitrate_controller/send_side_bandwidth_estimation.cc?rcl=033ea5f77140eef0c2defd4bd668de5dac9af3ea&l=392 the bitrate_bps won't be smaller than min_bitrate_configured_, i.e. the field set by x-google-min-bitrate. This behavior is wrong or at least not what we have expected in WebrtcTransport: when the bandwidth is fully used by video channel, returning x-google-min-bitrate as the bitrate from OnTargetBitrateChanged() is not expected. I have verified this change on my machine, and it partially resolves the laggy issue. Bug: chromium:769391 Change-Id: I2c87a78af63b508b5f8b25b77e171c92a10c7426 Reviewed-on: https://chromium-review.googlesource.com/726312 Commit-Queue: Zijie He <zijiehe@chromium.org> Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org> Cr-Commit-Position: refs/heads/master@{#509960}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .