Sergey Silkin 42bf2c670c Put current send codec to front of codecs list in RTP sender parameters
WebRTC can switch encoder on-fly when encoder fails or by request from
encoder selector. Putting the current send codec to the front of the
codecs list provides a simple way for apps to know what is actually
used without retrieving stats.

Bug: webrtc:13572
Change-Id: Iaaa5f7ad8667f59016dc92bff9e9a57a7425ef44
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/246500
Reviewed-by: Mirta Dvornicic <mirtad@webrtc.org>
Reviewed-by: Erik Språng <sprang@webrtc.org>
Commit-Queue: Sergey Silkin <ssilkin@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#35723}
2022-01-18 14:36:33 +00:00
2021-11-03 14:59:46 +00:00
2022-01-18 10:54:23 +00:00
2022-01-18 13:46:37 +00:00
2021-01-20 15:01:07 +00:00
2021-12-08 08:53:00 +00:00
2021-07-22 16:41:26 +00:00
2021-11-29 07:27:52 +00:00
2022-01-11 14:12:54 +00:00
2021-12-08 08:53:00 +00:00
2021-08-12 18:37:10 +00:00
2021-12-08 08:53:00 +00:00
2020-07-13 11:42:07 +00:00
2021-08-23 13:37:55 +00:00
2021-12-16 17:45:31 +00:00

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

Description
No description provided
Readme 255 MiB
Languages
C++ 88.6%
C 3.3%
Java 3%
Objective-C++ 1.9%
Python 1.9%
Other 1%