Ilya Nikolaevskiy 00a1bcb441 Ensure that unset capture timestamp wouldn't cause incorrect SR rtp timestamps
If for some reason capture timestamp is unset, the default value of 0 would be
passed to RtcpSender. This will cause rtp timestamps to grow at double the rate
in Sender Reports because it has time since the last frame capture as a term.

Bug: none
Change-Id: I2fe09dabef6b0957fb504deaa06393dedc4a9e70
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/162481
Reviewed-by: Danil Chapovalov <danilchap@webrtc.org>
Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#30105}
2019-12-17 12:03:24 +00:00
2019-12-02 09:30:51 +00:00
2018-10-05 14:40:21 +00:00
2019-12-10 12:08:56 +00:00
2019-10-28 12:27:50 +00:00
2019-07-08 13:45:15 +00:00
2017-09-15 04:25:06 +00:00
2018-12-18 12:30:58 +00:00
2019-10-08 12:20:39 +00:00
2017-09-15 04:25:06 +00:00
2018-07-23 15:28:48 +00:00
2017-09-15 04:25:06 +00:00
2019-09-03 14:55:43 +00:00
2019-12-11 08:08:58 +00:00
2019-11-11 14:58:20 +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 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.

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%