Ivo Creusen 67fb919b5e Handle event log parsing errors without crashing.
Instead of crashing when encountering an event log that cannot be parsed
it is better to print an error message, skip the file and continue.

Bug: webrtc:10337
Change-Id: I5dbca18e456c14e5a92af068f82e88cb17e8de9c
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/133185
Reviewed-by: Minyue Li <minyue@webrtc.org>
Commit-Queue: Ivo Creusen <ivoc@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#27727}
2019-04-24 07:49:23 +00:00
..
2019-03-19 09:46:54 +00:00
2018-06-19 14:00:39 +00:00

NetEQ RTP Play tool

Testing of the command line arguments

The command line tool neteq_rtpplay can be tested by running neteq_rtpplay_test.sh, which is not use on try bots, but it can be used before submitting any CLs that may break the behavior of the command line arguments of neteq_rtpplay.

Run neteq_rtpplay_test.sh as follows from the src/ folder:

src$ ./modules/audio_coding/neteq/tools/neteq_rtpplay_test.sh  \
  out/Default/neteq_rtpplay  \
  resources/audio_coding/neteq_opus.rtp  \
  resources/short_mixed_mono_48.pcm

You can replace the RTP and PCM files with any other compatible files. If you get an error using the files indicated above, try running gclient sync.

Requirements: awk and md5sum.