Conversation
ibc
left a comment
There was a problem hiding this comment.
Can you explain rationale of these changes? Was what wrong before them?
if not check 0 rtt |
| // Tell it to the NackGenerator. | ||
| if (this->params.useNack) | ||
| { | ||
| this->nackGenerator->UpdateRtt(static_cast<uint32_t>(this->rtt)); |
There was a problem hiding this comment.
Why are you just updating current RTT value in NackGenerator only if > 0.0f? This is wrong. It means that if negative then NackGenerator will keep using its previous given RTT value.
Makes sense. |
|
I'm including some valid changes of this PR into another one. Thanks @o-u-p |
Based on PR #1076 of @o-u-p ### Details - Stop NACK timer when NACK list is empty as explained in #1076 (comment). - Avoid RTT becoming negative in `RtpStreamSend` and `RtpStreamRecv`. If so, assign it with 0.0f. - And if 0.0f, use `DefaultRtt` (100 ms) in `NackGenerator`. - Remove useless `RtpStream::hasRtt` and check `RtpStream::rtt > 0.0f` instead. - Add some brackets in condition blocks.
|
Closing this PR in favour of #1082 |
- Stop NACK timer when NACK list is empty as explained in #1076 (comment). - Avoid RTT becoming negative in `RtpStreamSend` and `RtpStreamRecv`. If so, assign it with 0.0f. - And if 0.0f, use `DefaultRtt` (100 ms) in `NackGenerator`. - Remove useless `RtpStream::hasRtt` and check `RtpStream::rtt > 0.0f` instead. - Add some brackets in condition blocks.
|
Released in mediasoup 3.11.26 |
No description provided.