- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Apr 2023 17:22:44 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-extensions: == Does playoutDelay of video affect jitter buffer of synced audio and vice versa? == The spec has [this non-normative note](https://w3c.github.io/webrtc-extensions/#dfn-maximum-allowed-delay): <img width="758" alt="image" src="https://user-images.githubusercontent.com/3136226/230648649-08b6e7f3-a87f-41e8-8d9b-b59210197fc9.png"> What does _"the largest of those hints will take precedence in synchronization mechanism"_ mean? Does it mean: 1. tracks get synced at playout without the benefit of deeper jitter buffers? 2. tracks get the same (larger) jitter buffer depth? As mentioned in #156, jitter buffer depth is JS-observable through receiver.getStats(), so we should be clear. Notes are [non-normative](https://w3c.github.io/webrtc-extensions/#conformance) in this spec, and I find no normative steps to support 2, which suggests 1. Was 1 the intent? Is 2 useful? If so, do we wish to specify it? Any downsides to doing so? Either way we should clarify. Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/157 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 7 April 2023 17:22:46 UTC