| 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 recorded RTC event log, which is stored in | 
|  | 8 protobuf format. Such logs are generated in multiple ways, e.g. by | 
|  | 9 Chrome through the chrome://webrtc-internals page. | 
|  | 10 | 
|  | 11 The script has been tested to work in python versions 3.4.1 and 2.7.6, | 
|  | 12 but should work in all python versions for which there is a version | 
|  | 13 of the dependencies. | 
|  | 14 | 
|  | 15 Dependencies | 
|  | 16 ------------ | 
|  | 17 | 
|  | 18 The analyzer script needs *numpy* (http://www.numpy.org/) and | 
|  | 19 *matplotlib* (http://matplotlib.org/). | 
|  | 20 | 
|  | 21 A version of Protocol Buffers is needed as well. One is distributed | 
|  | 22 along with WebRTC in `thirdparty/protobuf/python`. This tool also | 
|  | 23 needs a file `rtc_event_log_pb2.py` which is automatically generated | 
|  | 24 from `webrtc/call/rtc_event_log.proto` and placed in | 
|  | 25 `out/<TARGET>/pyproto/webrtc/call/` with every WebRTC compilation. To | 
|  | 26 use it, WebRTC needs to be compiled before using this tool. | 
|  | 27 | 
|  | 28 An alternative to compiling WebRTC is to install your own version of | 
|  | 29 Protocol Buffers and `protoc`, the Protocol Buffer compiler. | 
|  | 30 | 
|  | 31 If you use your own version of protobuf, generate the python file in | 
|  | 32 this folder with | 
|  | 33 | 
|  | 34    protoc -I $WEBRTC_ROOT/webrtc/call $WEBRTC_ROOT/webrtc/call/rtc_event_log.pro
    to --python_out ./ | 
|  | 35 | 
| OLD | NEW | 
|---|