commit | c592e766a062aa6c2ea5dbe20237b71f5848c6ba | [log] [tgz] |
---|---|---|
author | Qiu Jianlin <jianlin.qiu@intel.com> | Fri Feb 07 01:51:03 2025 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Feb 12 00:42:55 2025 |
tree | 67ebeac19c28e16c7108ba53f3baa7902afcb2fa | |
parent | 902bc24b6f9094138dd3524b9fe321f9a7fe9fa8 [diff] |
Reland "Follow pref order for codec fallback." This is a reland of commit 1ad3e14e9981772554a848c5034c7c555680aef7 The original CL removes all sending streams since all codec types has been attempted for encoding and we have no other codecs to fallback to. However some downstream applications will still attempt to set the codec preferences even all send streams have been removed. As a result, we follow previous logic to keep the send streams, to avoid the regression. Original change's description: > Follow codec preference order for sending codec fallback. > > When encoder selector is not enabled, currently we always fallback to > VP8 no matter how the codec preference is setup. Update to follow codec > preference order for the fallback. > > Bug: chromium:378566918 > Change-Id: Ia3fbfc9d407683ef7b3d6246af7e9ec58535dc89 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/370707 > Reviewed-by: Erik Språng <sprang@webrtc.org> > Reviewed-by: Henrik Boström <hbos@webrtc.org> > Commit-Queue: Jianlin Qiu <jianlin.qiu@intel.com> > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#43566} Bug: chromium:378566918, b/384725754 Change-Id: Ifd48b30b80ae51c3ede9391ed62e8ce408864aa0 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/374852 Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Commit-Queue: Jianlin Qiu <jianlin.qiu@intel.com> Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> Cr-Commit-Position: refs/heads/main@{#43874}
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.