| commit | 24192c267a40eb7d6b1850489ccdbf7a84f8ff0f | [log] [tgz] |
|---|---|---|
| author | Ivo Creusen <ivoc@webrtc.org> | Fri Jul 12 17:00:25 2019 +0200 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Jul 12 16:18:31 2019 +0000 |
| tree | e518875c3e732e638cbbccfa3a835afd4fbfa87e | |
| parent | e95b57cdfc4a4deb9e15363adfb18eff736e3230 [diff] |
Revert "Add plumbing of RtpPacketInfos to each AudioFrame as input for SourceTracker." This reverts commit 3e8ef940fe86cf6285afb80e68d2a0bedc631b9f. Reason for revert: This CL causes a performance regression in NetEq, see https://bugs.chromium.org/p/chromium/issues/detail?id=982260. Original change's description: > Add plumbing of RtpPacketInfos to each AudioFrame as input for SourceTracker. > > This change adds the plumbing of RtpPacketInfo from ChannelReceive::OnRtpPacket() to ChannelReceive::GetAudioFrameWithInfo() for audio. It is a step towards replacing the non-spec compliant ContributingSources that updates itself at packet-receive time, with the spec-compliant SourceTracker that will update itself at frame-delivery-to-track time. > > Bug: webrtc:10668 > Change-Id: I03385d6865bbc7bfbef7634f88de820a934f787a > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/139890 > Reviewed-by: Stefan Holmer <stefan@webrtc.org> > Reviewed-by: Minyue Li <minyue@webrtc.org> > Commit-Queue: Chen Xing <chxg@google.com> > Cr-Commit-Position: refs/heads/master@{#28434} TBR=kwiberg@webrtc.org,stefan@webrtc.org,minyue@webrtc.org,chxg@google.com Bug: webrtc:10668, chromium:982260 Change-Id: I5e2cfde78c59d1123e21869564d76ed3f6193a5c Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/145339 Reviewed-by: Ivo Creusen <ivoc@webrtc.org> Commit-Queue: Ivo Creusen <ivoc@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28561}
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.