| commit | d4c5843bae2db419aa035abac0b2edfcba8aab70 | [log] [tgz] |
|---|---|---|
| author | Henrik Boström <hbos@webrtc.org> | Thu Sep 05 11:02:43 2024 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 05 12:11:11 2024 |
| tree | 11ce4a707589f6f69a4d7b5e6f697ccb461acf78 | |
| parent | 9463095df81b737a4be6bf10d14dab679457dd7b [diff] |
Undo recent changes to initial frame dropper, fixing a regression. A recent bugfix[1] introduced having to reconfigure the encoder in response to restrictions updating for the sake of not getting stuck at the wrong resolution in some cases. But the newly added ReconfigureEncoder() calls happened too early/often, and the initial frame dropper got confused thinking resolution changes were not in response to adaptation (restrictions) when they in fact were. The CL wrongly disabled the "reset initial frame dropper" logic, when the correct solution to this problem should have been to delay the ReconfigurationEncoder() call to the next frame (using `pending_encoder_reconfiguration_ = true`). With this delay the initial frame dropper is not confused and we can restore the old "reset" logic, fixing the regression. [1] https://webrtc-review.googlesource.com/c/src/+/360200 Bug: b/364252657 Change-Id: I6b93f4cc44eb12b1bbbda0d8d1e9906c29b615a2 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/361740 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#42961}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.