- From: bdrtc via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Apr 2023 12:53:55 +0000
- To: public-webrtc-logs@w3.org
> > I don't have insight into how the RTX timers work, but my naive assumption is that WebRTC should do sensible things related to what the size of the jitter buffer is, so why should it matter why the jitter buffer increased. The API is just one thing that affects jitter buffer, but there are other things too. Nothing special about this API in that sense > > Given that we have changed the `playoutDelay` to the `jitterbufferDepth` I think it would be good to reference that the increase of the buffer should also affect to the retransmissions and packet loss recovery mechanism in place, if not increasing the buffer depth has only effects in controlling the playout delay and I would prefer to stick to the old name. rtx-time was added in webrtc 111 release, when setting jitterbufferTarget, user may change rtx-time together via sdp. this is [ rtx-time issue](https://bugs.chromium.org/p/webrtc/issues/detail?id=12420) -- GitHub Notification of comment by bdrtc Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/160#issuecomment-1520105370 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 April 2023 12:53:56 UTC