tree e7f9f2ca709d602fb7dd1fa49e9ec5040b9bc633
parent 0e3b1ff8c4b1d9c7a2200c5a9093988413b11f34
author Evan Shrubsole <eshr@google.com> 1569408623 +0200
committer Commit Bot <commit-bot@chromium.org> 1569411472 +0000

Invalidate encoder rates on VideoStreamEncoder::ReconfigureEncoder

Without invalidation the codec configuration may not get updated. This
is prone to happen when the bandwidth is below the min or above the max
in which case the last_encoder_rate_settings_ may have not changed.

This led to a regression in b6a45dd, where last_encoder_rate_settings_
would not change the allocation or frame rate, but the frame rate would
have been set by the video adapter. Thus the frame rates were set
incorrectly, leading to lower values in the regression tests.

I have re-run this scenario against some of the metric drops and the
regression appears to be fixed.


Bug: webrtc:10126
Change-Id: I0fa6c9b71e7aff5dd80e53119db109d97eed98b6
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/154343
Commit-Queue: Evan Shrubsole <eshr@google.com>
Reviewed-by: Erik Språng <sprang@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#29301}