| commit | 84a3759825ec3bcba104196148be15aabc258a08 | [log] [tgz] |
|---|---|---|
| author | sprang <sprang@webrtc.org> | Fri Feb 10 15:04:27 2017 |
| committer | Commit bot <commit-bot@chromium.org> | Fri Feb 10 15:04:27 2017 |
| tree | 8f783c4ecabcc349994ab0066e0e139ae12f4112 | |
| parent | e9ad271db4e0e2b3df8b21ca93e727c24838ffcf [diff] |
Change rtc::VideoSinkWants to have target and a max pixel count The current method with max_pixel_count and max_pixel_count_step_up, where only one should be used at a time and this first signaling an inclusive upper bound and other other an exclusive lower bound, makes for a lot of confusion. I've updated this to have a desired target and a maximum instead. The source should select a resolution as close to the target as possible, but no higher than the maximum. I intend to also add similar frame rate settings in an upcoming cl. BUG=webrtc:4172,webrtc:6850 Review-Url: https://codereview.webrtc.org/2672793002 Cr-Commit-Position: refs/heads/master@{#16533}
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. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.