| commit | 626015d7f833818e31f175d9fb0c9ca3213f16a6 | [log] [tgz] |
|---|---|---|
| author | Anton Sukhanov <sukhanov@webrtc.org> | Mon Feb 04 23:16:06 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Feb 05 00:25:12 2019 |
| tree | c070a5ba95765f3ed6f570b6523a5b23ba5408fc | |
| parent | e22498cc3e0618f83bbe0e169507ad51b1769b2b [diff] |
Make AudioSendStream to be OverheadObserver In order to have correct overhead adjustments for ANA in AudioSendStream we need to know both transport and audio packetization overheads in AudioSendStream. This change makes AudioSendStream to be OverheadObserver instead of ChannelSend. This change is required for https://webrtc-review.googlesource.com/c/src/+/115082. This change was also suggested earlier in TODO: // TODO(solenberg): Make AudioSendStream an OverheadObserver instead. https://cs.chromium.org/chromium/src/third_party/webrtc/audio/channel_send.cc?rcl=71b5a7df7794bbc4103296fcd8bd740acebdc901&l=1181 I think we should also consider moving TargetTransferRate observer to AudioSendStream. Since AudioSendStream owns encoder and configures ANA, it makes sense to consolidate all rate (and overhead) calculation there. Added TODO to clean it up in next chanelists. Bug: webrtc:10150 Change-Id: I48791b998ea00ffde9ec75c6bca8b6dc83001b42 Reviewed-on: https://webrtc-review.googlesource.com/c/119121 Commit-Queue: Anton Sukhanov <sukhanov@webrtc.org> Reviewed-by: Fredrik Solenberg <solenberg@webrtc.org> Reviewed-by: Minyue Li <minyue@webrtc.org> Cr-Commit-Position: refs/heads/master@{#26540}
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.