Index: webrtc/system_wrappers/source/rtp_to_ntp_estimator.cc |
diff --git a/webrtc/system_wrappers/source/rtp_to_ntp_estimator.cc b/webrtc/system_wrappers/source/rtp_to_ntp_estimator.cc |
index d65bf98207a73918c21f46e5f9c7a37ae1550835..422759939a2a00c7ef396ad8ac34f56e2d340532 100644 |
--- a/webrtc/system_wrappers/source/rtp_to_ntp_estimator.cc |
+++ b/webrtc/system_wrappers/source/rtp_to_ntp_estimator.cc |
@@ -10,6 +10,7 @@ |
#include "webrtc/system_wrappers/include/rtp_to_ntp_estimator.h" |
+#include "webrtc/rtc_base/checks.h" |
#include "webrtc/rtc_base/logging.h" |
#include "webrtc/system_wrappers/include/clock.h" |
@@ -162,6 +163,9 @@ bool RtpToNtpEstimator::Estimate(int64_t rtp_timestamp, |
return false; |
} |
+ // params_.calculated should not be true unless params_.frequency_khz has been |
+ // set to something non-zero. |
+ RTC_DCHECK_NE(params_.frequency_khz, 0.0); |
kwiberg-webrtc
2017/09/01 12:53:06
Is it OK if the value is very, very close to zero?
|
double rtp_ms = |
(static_cast<double>(rtp_timestamp_unwrapped) - params_.offset_ms) / |
params_.frequency_khz + |