- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Apr 2023 08:42:52 +0000
- To: public-webrtc-logs@w3.org
If we can get alignment on this being a control surface for target jitter buffer delay rather than "playout" then the the API would be more testable. If the name is also wrong (playoutDelayHint vs playoutDelay), what do you think about changing the name to desiredJitterBufferDelay or something like that? (Avoiding the word "target" because the internal target is already exposed as [jitterBufferTargetDelay](https://w3c.github.io/webrtc-stats/#dom-rtcinboundrtpstreamstats-jitterbuffertargetdelay) and this value is not necessarily the same as the one the app asked for) -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/12#issuecomment-1504891246 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 April 2023 08:42:54 UTC