876a3dc88a
This CL fixes 2 issues that affect NetEq simulations. - When using event logs with multiple SSRCs, it does not make sense to use more than a single SSRC. If the user does not provide an SSRC filter, we should use the first SSRC we find and no others. - It is possible for event logs to have a gap in the middle, and sometimes we don't store/mark the gap properly. If is possible to detect gaps by looking at the wallclock time delta between getAudio events. These should be 10 ms nominally, so values greater than 1000 should never happen and indicate an error. Bug: webrtc:11855 Change-Id: Idc3b8a7902be4159da48b063ef5c5c82fd484071 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/181940 Reviewed-by: Jakob Ivarsson <jakobi@webrtc.org> Commit-Queue: Ivo Creusen <ivoc@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31960}
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.