Improve wraparound handling in the render time extrapolator.
This was actually working as intended, but as r3970 changed when render timestamps were extrapolated to when a frame was taken out for decoding, the wraparound could have happened in the Update() step before it had happened in the ExtrapolateLocalTime() step. This causes render timestamps to be generated 13 hours into the future.
TEST=trybots
BUG=1787
R=mflodman@webrtc.org
Review URL: https://webrtc-codereview.appspot.com/1497004
git-svn-id: http://webrtc.googlecode.com/svn/trunk@4055 4adac7df-926f-26a2-2b94-8c16560cd09d
diff --git a/webrtc/modules/video_coding/main/source/timing.cc b/webrtc/modules/video_coding/main/source/timing.cc
index 5b2cd0c..91aed14 100644
--- a/webrtc/modules/video_coding/main/source/timing.cc
+++ b/webrtc/modules/video_coding/main/source/timing.cc
@@ -57,17 +57,11 @@
}
void
-VCMTiming::Reset(int64_t nowMs /* = -1 */)
+VCMTiming::Reset()
{
CriticalSectionScoped cs(_critSect);
- if (nowMs > -1)
- {
- _tsExtrapolator->Reset(nowMs);
- }
- else
- {
- _tsExtrapolator->Reset();
- }
+
+ _tsExtrapolator->Reset();
_codecTimer.Reset();
_renderDelayMs = kDefaultRenderDelayMs;
_minTotalDelayMs = 0;