commit | 7e7e805d3b48377fd4487940be7707c8855ea447 | [log] [tgz] |
---|---|---|
author | Shuhai Peng <shuhai.peng@intel.com> | Mon Oct 11 10:24:01 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 11 11:32:17 2021 |
tree | e201f49298615e1e4028472a7b5811cdad4eb6e3 | |
parent | 49c59ca8063366e8cc36c3d5d597da09a2aaf54f [diff] |
video: Re-configure scalers when encoder info changed. Encoder info will be modified at runtime. In fact, we should reduce the number of 'full' ReconfigureEncoder(). If only need subset of it at runtime, consider handle it in VideoStreamEncoder::EncodeVideoFrame(). Consider two cases: Re-configure scalers when encoder info changed. Consider two cases: 1. When the status of the scaler changes from enabled to disabled, if we don't do this CL, scaler will adapt up/down to trigger an unnecessary full ReconfigureEncoder() when the scaler should be banned. 2. When the status of the scaler changes from disabled to enabled, if we don't do this CL, scaler will not work until some code trigger ReconfigureEncoder(). In extreme cases, the scaler doesn't even work for a long time when we expect that the scaler should work. This CL aims to make scalers work properly when encoder info changed. BUG: None Change-Id: Iec17730b5fac5e642c0fb2d9b11c5b7434f0a220 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/233384 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35175}
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.