From bc07d40eebec6dc331f10f5991c8a8949bdecefc Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Fri, 27 May 2022 18:46:23 +0200 Subject: [PATCH] event log analyzer: log rtp timestamps in question MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit and fix a typo BUG=None Change-Id: Ie286c52cbdfbc0269d92503c46b805bfdf5bb556 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/264151 Reviewed-by: Björn Terelius Commit-Queue: Philipp Hancke Cr-Commit-Position: refs/heads/main@{#37042} --- rtc_tools/rtc_event_log_visualizer/analyzer.cc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/rtc_tools/rtc_event_log_visualizer/analyzer.cc b/rtc_tools/rtc_event_log_visualizer/analyzer.cc index f94adc28f6..59f64efb78 100644 --- a/rtc_tools/rtc_event_log_visualizer/analyzer.cc +++ b/rtc_tools/rtc_event_log_visualizer/analyzer.cc @@ -150,7 +150,9 @@ absl::optional EstimateRtpClockFrequency( } RTC_LOG(LS_WARNING) << "Failed to estimate RTP clock frequency: Estimate " << estimated_frequency - << " not close to any stardard RTP frequency."; + << " not close to any standard RTP frequency." + << " Last timestamp " << last_rtp_timestamp + << " first timestamp " << first_rtp_timestamp; return absl::nullopt; }