- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Mar 2024 15:00:51 +0000
- To: public-webrtc-logs@w3.org
> AIUI, the desire is for the web page to act a little bit like an SFU. Is the goal still to repurpose RTCRtpScriptTransform to run an SFU in JS? For example, previous choices there like RTCEncodedVideoFrame being mutable and its [serialization steps](https://w3c.github.io/webrtc-encoded-transform/#RTCEncodedVideoFrame-serialization) not copying the ArrayBuffer, was tailored to the simple frame modification use cases of encrypt/decrypt and add metadata. How do we reconcile that SFU use cases seem better served by immutable RTCEncodedVideoFrames (per the [tee problem](https://github.com/w3c/webrtc-extensions/pull/198#discussion_r1532975637)? Does not a perfect fit mean not the right surface? https://github.com/w3c/webrtc-encoded-transform/issues/134 discusses creating one from another, but it's not clear how one would go from immutable to mutable without a copy. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/198#issuecomment-2012535409 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 March 2024 15:00:52 UTC