| commit | 02956feb2dc3ebdaa612c5c41f52011ce437d467 | [log] [tgz] |
|---|---|---|
| author | Henrik Boström <hbos@webrtc.org> | Tue Feb 25 09:35:03 2020 +0100 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Feb 25 09:52:13 2020 +0000 |
| tree | 34dd6c37cc1d5a0afdd8bfdff2904cb876d2bb99 | |
| parent | 414da244f00cf84ba4e02d3d855a73fc42fbe887 [diff] |
[Overuse] Can[Increase/Decrease][Resolution/FrameRate]? Adapting up or down is currently a "Maybe Adapt" method. In the future we will want to be able to decide which stream to adapt, and as such we need to be able to tell if a stream is able to do so. This takes us one step in that direction, by refactoring OveruseFrameDetectorResourceAdaptationModule::VideoSourceRestrictor's methods to follow a simple pattern: - What is the next step? GetHigherFrameRateThan, GetLowerFrameRateThan, GetHigherResolutionThan, GetLowerResolutionThan - Can we adapt? CanIncreaseFrameRate, CanDecreaseFrameRate, CanIncreaseResolution, CanDecreaseResolution - Do adapt! IncreaseFrameRateTo, DecreaseFrameRateTo, IncreaseResolutionTo, DecreaseResolutionTo Hopefully this makes the code easier to follow. This CL changes the "Request Higher/Lower" methods to take the target as input instead of implicitly calculating the target from the current input resolution or frame rate. Bug: webrtc:11222 Change-Id: If625834e921a24a872145105f5d553fb8f9f1795 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168966 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@{#30600}
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.