- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Mar 2024 23:03:00 +0000
- To: public-webrtc-logs@w3.org
> The RTCRtpScriptTransformer.readable is transferable, so could be posted to a worklet within the current shape. This produces a _"[readable side in another realm](https://streams.spec.whatwg.org/#transferrable-streams)"_, where the original realm feeding that readable is the dedicated worker provided by the webpage, at least in current implementations of that surface. > requiring apps to copy data & metadata in a DedicatedWorker before going to the worklet / after returning from it. Can't the app just transfer the frame.[data](https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedaudioframe-data) ArrayBuffer instead? i.e. not a copy. I'd be interested to see the numbers. > Transferring the readablestream to the worklet would mean frames could be delivered directly there. This sounds like https://github.com/whatwg/streams/issues/1124. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/226#issuecomment-1986543409 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 March 2024 23:03:02 UTC