d592575698
Previously, number of decoder threads for VP9 were always set to 8 but with a cap at number of cores. This was done since we "can't know" the resolution that will be used. With this change, we now intialize the number of threads based on resolution given in InitDecode(). If a resolution change happens in flight, it requires a keyframe. We therefore parse the header from any key frame and if it has a new resolution, we re-initialize the decoder. The number of threads used is based on pixel count. We set one thread as target for 1280x720, and scale up lineraly from there. The 8-thread cap is gone, but still limit it core count. This means for instance: 1 <= 720p, 2 for 1080p, 4 for 1440p, 9 for 4K. Bug: webrtc:11551 Change-Id: I14c169a6c651c50bd1b870c4b22bc4495c8448fd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/174460 Commit-Queue: Erik Språng <sprang@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31507}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct