- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Mar 2024 22:31:24 +0000
- To: public-webrtc-logs@w3.org
How does this stack up against just optimizing the obvious/inoptimal API? E.g. ```js // Let relayPc be the PC used to relay frames to the next peer. const [sender] = relayPc.getSenders(); // Let recvPc be the receiving PC recvPc.ontrack = ({receiver}) => await sender.replaceTrack(receiver.track); sender.transform = new RTCRtpScriptTransform(worker, {}); ``` Browsers could detect when the input is a `receiver.track` and forward received RTCEncodedVideoFrames directly on the sender transform's `writable` (skipping decode and re-encode) where JS can modify metadata. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/198#issuecomment-2005161154 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 March 2024 22:31:25 UTC