Jesús de Vicente Peña 01cac31d58 Fixes for the neteq_test clock.
The problem occurs when more than one call is made to the method RunToNextGetAudio. Except for the first call to that method, the clock was not properly updated on the first iteration of the inner loop in RunToNextGetAudio.

Pair: lionelk@webrtc.org

Bug: webrtc:14735
Change-Id: If6fb5c2c700b0f715f626fedf95672a56b04ab12
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/285942
Reviewed-by: Jakob Ivarsson‎ <jakobi@webrtc.org>
Commit-Queue: Jesus de Vicente Pena <devicentepena@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#38843}
2022-12-08 10:13:00 +00:00
..
2022-12-08 10:13:00 +00:00
2022-12-08 10:13:00 +00:00
2019-07-08 13:45:15 +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.