commit | 9a5de95af91bd5094ecac96d775a11baaa2cb0b3 | [log] [tgz] |
---|---|---|
author | Henrik Boström <hbos@webrtc.org> | Tue Mar 14 08:50:19 2023 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 14 12:05:24 2023 |
tree | 18f7004a0d13d35212a44ef14bc2aad9330cfa5c | |
parent | 51edb56884e6e320b8229a50f11241f6acc079d7 [diff] |
Add a flag to control legacy vs spec-compliant scalability mode. The goal of the VP9 simulcast project is that when `scalability_mode` is set, multiple encodings are always interpreted as simulcast, even if VP9 or AV1 is used. This CL makes this so, but only if the flag "WebRTC-AllowDisablingLegacyScalability" is "/Enabled/". This allows us to make "SendingThreeEncodings_VP9_Simulcast" EXPECT VP9 simulcast. When we are ready to ship we will remove the need to use the field trial, but before we ship this we'll want to revisit if SvcRateAllocator can be updated to support simulcast. (Today if we use SvcRateAllocator when VP9 simulcast is used, all encodings except the first one get bitrate=0, causing the test to fail because media is not flowing on all layers.) For now, a TODO is added. Bug: webrtc:14884 Change-Id: Ie20ae748b0c0405162f3a1b015ab94956ef83dae Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/297340 Reviewed-by: Evan Shrubsole <eshr@webrtc.org> Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Henrik Boström <hbos@webrtc.org> Reviewed-by: Philip Eliasson <philipel@webrtc.org> Cr-Commit-Position: refs/heads/main@{#39552}
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 here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.