| commit | c1cc6a36b2fe646d284dd80680f6dbb905d8a207 | [log] [tgz] |
|---|---|---|
| author | Philipp Hancke <phancke@microsoft.com> | Wed Jan 03 15:47:05 2024 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 01 13:11:09 2024 |
| tree | 0bd0566a0254fba5b195556e95d67273443d8359 | |
| parent | 89cf26f1e0532130745f648cf16b1fb8af2f6b4f [diff] |
sdp: backfill default codec parameters for AV1 as required by https://aomediacodec.github.io/av1-rtp-spec/#72-sdp-parameters Also unify usage of profile fmtp parameter. Most notably this causes SDP answers to include the default values. These default values correspond to libaom's default values for AV1E_SET_TARGET_SEQ_LEVEL_IDX, AV1E_SET_TIER_MASK as used in https://source.chromium.org/chromium/chromium/src/+/main:third_party/libaom/source/libaom/aom/aomcx.h and g_profile in aom_codec_enc_cfg https://source.chromium.org/chromium/chromium/src/+/main:third_party/libaom/source/libaom/aom/aom_encoder.h;l=415;drc=b58207f5aecc39db7d3da766e7d171e5d2c3598e Note: AV1 is inconsistently cased in variable/struct/method/class names. The canonical casing should probably be "Av1" since it is an acronym standing for "AOMedia Video 1". BUG=webrtc:15703 Change-Id: I11864b7666fea906cd1a0759c7ad45997beab90e Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/331360 Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Philipp Hancke <phancke@microsoft.com> Cr-Commit-Position: refs/heads/main@{#41654}
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.