Tommi 3cc68ec32e Report stats from ChannelReceive::GetAudioFrameWithInfo at 1Hz.
This is a change from the previous 100Hz frequency.
Also changing the  locks slightly in AcmReceiver so that grabbing the
neteq lock right after we've let it go, isn't necessary inside of
AcmReceiver::GetAudio and also to avoid grabbing the neteq lock while
holding the AcmReceiver lock.

Bug: webrtc:12868
Change-Id: If6ee35f3dca20eb5bdbc615123aa099ccecf57c5
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/221371
Commit-Queue: Tommi <tommi@webrtc.org>
Reviewed-by: Minyue Li <minyue@webrtc.org>
Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org>
Reviewed-by: Markus Handell <handellm@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#34258}
2021-06-09 18:41:47 +00:00
..
2019-07-08 13:45:15 +00:00
2019-12-13 10:06:07 +00:00
2019-07-08 13:45:15 +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.