| commit | f05af9e0fc38702bbbf395860dc13426744f39b1 | [log] [tgz] |
|---|---|---|
| author | Taylor Brandstetter <deadbeef@webrtc.org> | Fri Mar 20 00:14:27 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Mar 24 10:48:26 2020 |
| tree | 8e7919d75d56e5b9f151c27864261c196ffed999 | |
| parent | aec63e0715ae7f0a61a72f760ee224e763d989e5 [diff] |
Revert "Remove bitratePriority from the Obj-C RTCRtpEncodingParameters wrapper." This reverts commit 86e0ea5711cfef95960ffcc8b6d918c67576e5c9. Reason for revert: The reasons for removing bitratePriority are unclear. Aside from the fact that you can't yet use it for the relative bitrate of simulcast streams, only the relative bitrate of entire tracks, it's working as intended. It differs from the standard, but only in that it's more flexible; the web standard only allows values of 0.5, 1.0, 2.0, and 4.0 while for the native API we allow any ratio. Original change's description: > Remove bitratePriority from the Obj-C RTCRtpEncodingParameters wrapper. > > This was added in CL 135122, but the bitratePriority parameter is not > standard and not implemented in a way users would expect. So it should > actually not be exposed in the Obj-C SDK. > > Bug: webrtc:10438 > Change-Id: I801ce940a32701d2703e951ef2b601c606aa2111 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/135287 > Reviewed-by: Kári Helgason <kthelgason@webrtc.org> > Commit-Queue: Anders Carlsson <andersc@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#27861} TBR=andersc@webrtc.org,kthelgason@webrtc.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: webrtc:10438 Change-Id: Ibc16b6054a1583de43a868d98683ea114bd89435 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/171140 Reviewed-by: Taylor <deadbeef@webrtc.org> Reviewed-by: Kári Helgason <kthelgason@webrtc.org> Commit-Queue: Kári Helgason <kthelgason@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30863}
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 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.