commit | b08882b625ea245ea1b42c2436c8acc17d9306a1 | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Tue Jan 07 09:11:17 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Jan 07 09:55:54 2020 |
tree | bef6eac5013cf8a655e9454cf5b849a357cb5acc | |
parent | 29e14e6aaeb6176c81c96420e354e6124f424ea3 [diff] |
Refactor out VideoStreamEncoder's overuse logic to separate module. This CL puts the VideoStreamEncoder's current adaptation logic inside the new class OveruseFrameDetectorResourceAdaptationModule. The intention is not to change any behavior, only to move code. Future CLs should step by step decrease the coupling between OveruseFrameDetectorResourceAdaptationModule, VideoStreamEncoder and the VideoStreamEncoder's QualityScaler by introducing more abstract interfaces. This is not done in this CL because it is large enough as it is, but the long term goal is to make it possible to replace the existing overuse module with a different implementation. This CL relies on existing tests exercising the VideoStreamEncoder, but part of making overuse logic modular should include testing each module separately as well as continued integration testing of the VideoStreamEncoder. Bug: webrtc:11222 Change-Id: I316a174adfd00d60cdd224a23a5f616efd235d13 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/161953 Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Evan Shrubsole <eshr@google.com> Cr-Commit-Position: refs/heads/master@{#30163}
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 http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.