Index: tools/py_event_log_analyzer/README |
diff --git a/tools/py_event_log_analyzer/README b/tools/py_event_log_analyzer/README |
new file mode 100644 |
index 0000000000000000000000000000000000000000..c92479fc8e96cd80f18e9b56364d7f1f08fa8379 |
--- /dev/null |
+++ b/tools/py_event_log_analyzer/README |
@@ -0,0 +1,23 @@ |
+This file describes how to set up and use the RTP log analyzer. |
+ |
+First build the tool with |
+ |
+ 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!
|
+ |
+The tool is built by default, so |
+ |
+ ninja -C out/my_build |
+ |
+is enough. |
+ |
+After building, run the tool as follows: |
+ |
+ ./out/my_build/rtp_analyzer.sh <rtc event log> |
+ |
+where <rtc event log> is a recorded RTC event log, which is stored in |
+protobuf format. Such logs are generated in multiple ways, e.g. by |
+Chrome through the chrome://webrtc-internals page. |
+ |
+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
|
+but should work in all python versions for which there is a version |
+of the dependencies. |