commit | 3453149b28dcd6e5f563f4cc8e43c51668f38b3b | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Thu Mar 12 11:41:19 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Mar 13 12:59:53 2020 |
tree | d20ce61b1a38d635c64b3339a5c2f7298e6b5ad3 | |
parent | 0569a12ecefacfbda1ad48e4723e373b713b1ae8 [diff] |
[Adaptation] Adapter: Inform the module why there is no next target. This introduces AdaptationTargetOrReason and gets rid of VideoStreamAdapter's dependency on the VideoStreamEncoderObserver. AdaptationTargetOrReason provides information about why an adaptation target could not be returned from GetAdaptUpTarget() and GetAdaptDownTarget() with the enum CannotAdaptReason and the boolean min_pixel_limit_reached. While the enum value is not used by the caller in this CL, it makes explicit reasons the adapter is allowed to reject a target. TODOs are added documenting how we want to get rid of kAwaitingPreviousAdaptation for multi-stream use cases and how kIsBitrateConstrained can be rephrased as a resource problem in the future. min_pixel_limit_reached() allows us to move the responsibility of stats reporting to the module. A TODO documents how this could be replaced by kLimitReached or similar logic in the future. Bug: webrtc:11393 Change-Id: Iffdd8ddb01641937741fac353174ea14168477ce Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/169928 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Evan Shrubsole <eshr@google.com> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30789}
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.