- From: Eldar Rello via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Mar 2024 11:26:06 +0000
- To: public-webrtc-logs@w3.org
Removing the delay constraint isn't really an option. With just A and B the example is of course very simplistic. There can be N streams to synchronise and once the constraint is removed the delay can change too quickly in unknown direction. Really hard to maintain sync in such conditions. Also figuring out which buffers require constraint and which do not in a given moment doesn't sound like something, which could work reliably. 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. Very simple. -- GitHub Notification of comment by eldarrello Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/199#issuecomment-2006932093 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 11:26:07 UTC