webrtc/tools/py_event_log_analyzer/README - Issue 2123773002: Changes in UI and minor extra functionality for rtp_analyzer.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: webrtc/tools/py_event_log_analyzer/README

Issue 2123773002: Changes in UI and minor extra functionality for rtp_analyzer. (Closed) Base URL: https://chromium.googlesource.com/external/webrtc.git@master

Patch Set: Created 4 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

OLD	NEW
1 This file describes how to set up and use the RTP log analyzer.	1 This file describes how to set up and use the RTP log analyzer.

2	2

3 First build the tool with	3 First build the tool with

4	4

5 ninja -C out/my_build webrtc:rtp_analyzer	5 ninja -C out/my_build webrtc:rtp_analyzer

6	6

7 The tool is built by default, so	7 The tool is built by default, so

8	8

9 ninja -C out/my_build	9 ninja -C out/my_build

10	10

11 is enough.	11 is enough.

12	12

13 After building, run the tool as follows:	13 After building, run the tool as follows:

14	14

15 ./out/my_build/rtp_analyzer.sh <rtc event log>	15 ./out/my_build/rtp_analyzer.sh [options] <rtc event log>

16	16

17 where <rtc event log> is a recorded RTC event log, which is stored in	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	18 protobuf format. Such logs are generated in multiple ways, e.g. by

19 Chrome through the chrome://webrtc-internals page.	19 Chrome through the chrome://webrtc-internals page.

20	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

21 The script has been tested to work in python versions 3.4.1 and 2.7.6,	27 The script has been tested to work in python versions 3.4.1 and 2.7.6,

22 but should work in all python versions.	28 but should work in all python versions.

23	29

24 Working versions of NumPy (http://www.numpy.org/) and matplotlib	30 Working versions of NumPy (http://www.numpy.org/) and matplotlib

25 (http://matplotlib.org/) are needed to run this tool. See this link	31 (http://matplotlib.org/) are needed to run this tool. See this link

26 with installation instructions (http://www.scipy.org/install.html).	32 with installation instructions (http://www.scipy.org/install.html).

OLD	NEW

« no previous file with comments | « no previous file | webrtc/tools/py_event_log_analyzer/pb_parse.py » ('j') | no next file with comments »