- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jul 2020 11:06:20 +0000
- To: public-webrtc-logs@w3.org
> Regarding the time required to adjust the delay to the new value, it is an implementation detail of NetEq. We have modified it so it converges faster (whiting 1 second) to the value set by js by adding silence or dropping packets instead of the default behavior of NetEq. > > On a side note, I would be awesome if we could add more parameters to control the jitter buffer behavior (or even completely replace it) as, at least NetEq, is not tuned correctly for several use cases. That's interesting to hear. I would like to see Chrome's NetEq implementation to converge that fast too, but have no idea about the tradeoffs of that. @minyuel FYI an external developer has made playoutDelay more responsive for audio receivers. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/46#issuecomment-661790367 using your GitHub account
Received on Tuesday, 21 July 2020 11:06:22 UTC