OLD | NEW |
| (Empty) |
1 This file describes how to set up and use the RTP log analyzer. | |
2 | |
3 First build the tool with | |
4 | |
5 ninja -C out/my_build webrtc:rtp_analyzer | |
6 | |
7 The tool is built by default, so | |
8 | |
9 ninja -C out/my_build | |
10 | |
11 is enough. | |
12 | |
13 After building, run the tool as follows: | |
14 | |
15 ./out/my_build/rtp_analyzer.sh [options] <rtc event log> | |
16 | |
17 where <rtc event log> is a recorded RTC event log, which is stored in | |
18 protobuf format. Such logs are generated in multiple ways, e.g. by | |
19 Chrome through the chrome://webrtc-internals page. | |
20 | |
21 Options: | |
22 -h, --help show this help message and exit | |
23 --dump_header_to_stdout | |
24 print header info to stdout; similar to rtp_analyze | |
25 --query_sample_rate always query user for real sample rate | |
26 | |
27 The script has been tested to work in python versions 3.4.1 and 2.7.6, | |
28 but should work in all python versions. | |
29 | |
30 Working versions of NumPy (http://www.numpy.org/) and matplotlib | |
31 (http://matplotlib.org/) are needed to run this tool. See this link | |
32 with installation instructions (http://www.scipy.org/install.html). | |
OLD | NEW |