Remove clock drift metric from NetEq.
This metric is not used anywhere and is not calculated correctly when the delay manager is in relative arrival delay mode. Bug: webrtc:10333 Change-Id: Iac79ab40b79b17802ad9d626c130e82f761bae26 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/150786 Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> Reviewed-by: Oskar Sundbom <ossu@webrtc.org> Commit-Queue: Jakob Ivarsson <jakobi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29037}
This commit is contained in:
committed by
Commit Bot
parent
5b4fcb5bf6
commit
65024d9620
@ -81,14 +81,6 @@ class DelayManager {
|
||||
// Resets the DelayManager and the associated DelayPeakDetector.
|
||||
virtual void Reset();
|
||||
|
||||
// Calculates the average inter-arrival time deviation from the histogram.
|
||||
// The result is returned as parts-per-million deviation from the nominal
|
||||
// inter-arrival time. That is, if the average inter-arrival time is equal to
|
||||
// the nominal frame time, the return value is zero. A positive value
|
||||
// corresponds to packet spacing being too large, while a negative value means
|
||||
// that the packets arrive with less spacing than expected.
|
||||
virtual double EstimatedClockDriftPpm() const;
|
||||
|
||||
// Returns true if peak-mode is active. That is, delay peaks were observed
|
||||
// recently. This method simply asks for the same information from the
|
||||
// DelayPeakDetector object.
|
||||
|
||||
Reference in New Issue
Block a user