
In production code, the maximum number of packets is by default set to 200, so we should adopt the same behavior in tests. Bug: None Change-Id: I415790b7cd9fb170ea7ac94685cc6bbe14efac4d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/178744 Reviewed-by: Sam Zackrisson <saza@webrtc.org> Commit-Queue: Ivo Creusen <ivoc@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31646}
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
.