Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 This file describes how to set up and use the RTP log analyzer. | |
| 2 | |
| 3 Run the tool as follows: | |
| 4 | |
| 5 python rtp_analyzer.py <rtc event log> | |
| 6 | |
| 7 where <rtc event log> is a protobuf dump of the RTC event stream. Such | |
|
ivoc
2016/05/24 11:50:17
I recommend rephrasing this a bit, for example: wh
aleloi
2016/05/24 15:54:39
Done.
| |
| 8 dumps are generated by Chrome through chrome://webrtc-internals | |
|
ivoc
2016/05/24 11:50:17
I would rephrase to make it more clear that there
aleloi
2016/05/24 15:54:39
Done.
| |
| 9 | |
| 10 The script has been tested to work in python versions 3.4.1 and 2.7.6, | |
| 11 but should work in all python versions for which there is a version | |
| 12 of the dependencies. | |
| 13 | |
| 14 Dependencies | |
| 15 ------------ | |
| 16 | |
| 17 The analyzer script needs *numpy* (http://www.numpy.org/) and | |
| 18 *matplotlib* (http://matplotlib.org/). These libraries can probably be | |
|
ivoc
2016/05/24 11:50:17
I don't think it's safe to assume all of our users
aleloi
2016/05/24 15:54:39
Done.
| |
| 19 installed with your systems package manager, e.g. | |
| 20 | |
| 21 sudo apt-get install python-numpy python-matplotlib | |
| 22 | |
| 23 in Debian-based systems | |
| 24 | |
| 25 If you use python 2, you also need *enum34* | |
|
ivoc
2016/05/24 11:50:17
This might be a small/personal thing, but I prefer
aleloi
2016/05/24 15:54:39
Done.
| |
| 26 (https://pypi.python.org/pypi/enum34) and *future* | |
| 27 (https://pypi.python.org/pypi/future). These packages can be installed | |
| 28 through pip, (https://docs.python.org/2.7/installing/). | |
| 29 | |
| 30 You also need a version of Protocol Buffers. One is distributed along | |
|
ivoc
2016/05/24 11:50:17
Same here, I would recommend: A version of the Pro
aleloi
2016/05/24 15:54:39
Done.
| |
| 31 with WebRTC in `thirdparty/protobuf/python`. This tool also needs a | |
| 32 file `rtc_event_log_pb2.py` which is automatically generated from | |
| 33 `webrtc/call/rtc_event_log.proto` and placed in | |
| 34 `out/<TARGET>/pyproto/webrtc/call/` with every WebRTC compilation. To | |
| 35 use it, you have to compile WebRTC before using this tool. | |
|
ivoc
2016/05/24 11:50:17
To generate it, WebRTC should be compiled before u
aleloi
2016/05/24 15:54:39
Done.
| |
| 36 | |
| 37 An alternative to compiling WebRTC is to install your own version of | |
| 38 Protocol Buffers and the `protoc`, the Protocol Buffer compiler. On | |
|
ivoc
2016/05/24 11:50:17
"the" should be removed here, so: ...Buffers and '
aleloi
2016/05/24 15:54:39
Done.
| |
| 39 Debian-based systems, it is | |
|
ivoc
2016/05/24 11:50:17
Again, too linux/debian specific. Would remove: On
aleloi
2016/05/24 15:54:39
Done.
| |
| 40 | |
| 41 sudo apt-get install protobuf-compiler python-protobuf | |
| 42 | |
| 43 If you use your own version of protobuf, generate the python file in | |
| 44 this folder with | |
| 45 | |
| 46 protoc -I $WEBRTC_ROOT/webrtc/call $WEBRTC_ROOT/webrtc/call/rtc_event_log.pro to --python-out ./ | |
| 47 | |
| OLD | NEW |