- From: Jakob Ivarsson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Mar 2024 13:07:44 +0000
- To: public-webrtc-logs@w3.org
> once the constraint is removed the delay can change too quickly in unknown direction Remove it iteratively in steps until the right delay is achieved? Could you explain in more detail why removing a delay constraint is not possible? > Really hard to maintain sync in such conditions. In the example above the streams are already out of sync? > In my vision how it can work is that all buffers are forced to specific delay (setting min and max) at the same moment according to worse jitterBufferMinimumDelay monitored from webrtc stats. Network latency / jitter and audio device latency will be different for different devices and can change over time, so the delay needs to be adjusted continuously and independently (as in different streams will have different delay settings to achieve sync) anyway? -- GitHub Notification of comment by jakobivarsson Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/199#issuecomment-2007133260 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 March 2024 13:07:45 UTC