- From: Palak Agarwal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Oct 2023 09:57:28 +0000
- To: public-webrtc-logs@w3.org
We want to solve the use case first mentioned in [WebRTC July 2023 meeting – (SetMetadata for redundant relay PCs.)](https://www.w3.org/2023/07/18-webrtc-minutes.html#t10). Though using Data channels for this use case is possible, it adds more latency than RTP would using the proposed encoded transforms approach. In addition to this, using data channels here would require the app to write, tune and maintain its own custom jitter buffer along with defining a system to smoothly render vide from JS, which can be difficult due to timing restrictions. Though encoded transforms do not allow handling packets, we think the added latency on waiting to assemble packets to a frame is still much less than data channels and something that our use case can handle. In regards to the concern about packet loss management, this is being addressed in [Congestion control API proposal](https://github.com/w3c/webrtc-encoded-transform/pull/207) -- GitHub Notification of comment by palak8669 Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/202#issuecomment-1750319981 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 October 2023 09:57:29 UTC