Use backticks not vertical bars to denote variables in comments for /rtc_base
Bug: webrtc:12338 Change-Id: I72fcb505a92f03b2ace7160ee33d555a977eddfd Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/226955 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/master@{#34587}
This commit is contained in:
committed by
WebRTC LUCI CQ
parent
22a6b2dcad
commit
96e3b991da
@ -88,7 +88,7 @@ int64_t TimestampAligner::UpdateOffset(int64_t capturer_time_us,
|
||||
// offset, the filter is reset. This could happen, e.g., if the
|
||||
// capturer's clock is reset, cameras are plugged in and out, or
|
||||
// the application process is temporarily suspended. Expected to
|
||||
// happen for the very first timestamp (|frames_seen_| = 0). The
|
||||
// happen for the very first timestamp (`frames_seen_` = 0). The
|
||||
// threshold of 300 ms should make this unlikely in normal
|
||||
// operation, and at the same time, converging gradually rather than
|
||||
// resetting the filter should be tolerable for jumps in capturer's time
|
||||
@ -124,10 +124,10 @@ int64_t TimestampAligner::ClipTimestamp(int64_t filtered_time_us,
|
||||
time_us = prev_translated_time_us_ + kMinFrameIntervalUs;
|
||||
if (time_us > system_time_us) {
|
||||
// In the anomalous case that this function is called with values of
|
||||
// |system_time_us| less than |kMinFrameIntervalUs| apart, we may output
|
||||
// `system_time_us` less than `kMinFrameIntervalUs` apart, we may output
|
||||
// timestamps with with too short inter-frame interval. We may even return
|
||||
// duplicate timestamps in case this function is called several times with
|
||||
// exactly the same |system_time_us|.
|
||||
// exactly the same `system_time_us`.
|
||||
RTC_LOG(LS_WARNING) << "too short translated timestamp interval: "
|
||||
"system time (us) = "
|
||||
<< system_time_us << ", interval (us) = "
|
||||
|
||||
Reference in New Issue
Block a user