d2ed0a4c9e
temporal_layer_thresholds_bps served only one purpose: its size was used to infer number of temporal layers. I replaced it with num_temporal_layers, which does what is says. The practical reason for this change is the need to have possibility to distinguish between cases when VP9 SVC temporal layering was/not set through field trial. That was not possible with temporal_layer_thresholds_bps[] because empty vector means 1 temporal layer. Bug: webrtc:8518 Change-Id: I275ec3a8c74e8ba409eb049878199f132a20ec51 Reviewed-on: https://webrtc-review.googlesource.com/58084 Commit-Queue: Sergey Silkin <ssilkin@webrtc.org> Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Stefan Holmer <stefan@webrtc.org> Cr-Commit-Position: refs/heads/master@{#22230}
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 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.
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