- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Apr 2023 07:25:42 +0000
- To: public-webrtc-logs@w3.org
jitterBufferDelay is the _actual_ delay, the total time spent for each sample emitted by the jitter buffer. That does not need to change. The reason the actual delay may be different than the target delay, jitterBufferTargetDelay, is that when the target changes we accelerate or decelerate samples to avoid glitches. The RTCRtpReceiver.jitterBufferTarget API sets the _desired target of the app_. The reason why the API target and the current target may be different is due to, as the API describes, there could be network conditions or resource constraints that make the UA not able to achieve it right now. And the jitterBufferMinimumDelay is just exposing the internal view of what the minimum delay could be. The way I see it, there are no webrtc-stats changes needed and it all makes sense. @jan-ivar -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/753#issuecomment-1517388355 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 April 2023 07:25:43 UTC