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 | |
kwiberg-webrtc
2016/06/09 12:27:20
Inconsistent indentation. You use four spaces belo
aleloi
2016/06/10 14:12:03
thanks!
| |
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 <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 The script has been tested to work in python versions 3.4.1 and 2.7.6, | |
kwiberg-webrtc
2016/06/09 12:27:20
Is this true? Didn't you state elsewhere that only
aleloi
2016/06/10 14:12:03
Well, the truth is that it works in py-2 if you ma
| |
22 but should work in all python versions for which there is a version | |
23 of the dependencies. | |
OLD | NEW |