Skip to content

RtpRetransmissionBuffer: consider the case of packet with newest timestamp but "old" seq number - #1039

Merged
ibc merged 4 commits into
v3from
rtpretransmissionbuffer-handle-newest-timestamp-with-old-seq
Mar 29, 2023
Merged

ibc merged 4 commits into
v3from
rtpretransmissionbuffer-handle-newest-timestamp-with-old-seq

Conversation

@ibc

@ibc ibc commented Mar 29, 2023

Copy link
Copy Markdown
Member

Fixes #1037

Details:

  • We must consider the case in which, due for example to huge packet loss, received packet has higher timestamp but "older" seq number than the newest packet in the buffer and, if so, use it to clear too old packets rather than the newest packet in the buffer.
  • Bonus track: restore buffer size to 2500 since increasing it didn't indeed help (it shouldn't help as proven).

…stamp but "old" seq number

Fixes #1037

### Details:

- We must consider the case in which, due for example to huge packet loss, received packet has higher timestamp than the newest packet in the buffer and, if so, use it to clear too old packets rather than the newest packet in the buffer.
- Bonus track: restore buffer size to 2500 since increasing it didn't indeed help (it shouldn't help as proven).
@ibc

ibc commented Mar 29, 2023

Copy link
Copy Markdown
Member Author

Amazing that CI didn't happen in this PR. Merging anyway.

@ibc
ibc merged commit 5823632 into v3 Mar 29, 2023
@ibc
ibc deleted the rtpretransmissionbuffer-handle-newest-timestamp-with-old-seq branch March 29, 2023 16:31
@nazar-pc

Copy link
Copy Markdown
Collaborator

GitHub Actions is having issues today: https://status.github.com/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

High packet loss after upgrading to 3.11.16 version

3 participants