W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > November 2020

[webrtc-insertable-streams] Optimizing encoded frame buffer allocation and memory copies (#49)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Tue, 24 Nov 2020 09:45:14 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-749546337-1606211113-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/webrtc-insertable-streams:

== Optimizing encoded frame buffer allocation and memory copies ==
RTCEncodedAudioFrame and RTCEncodedVideoFrame both own an ArrayBuffer.
This array buffer is exposed to JavaScript by ReadableStream and consumed by WritableStream.

One important design API goal is to limit memory copies, maybe allow in-place transform of the array buffer so that there is no memory copy and no memory allocation.

One possibility would be to allow the frame array buffer to be detached after the frame is enqueued in the WritableStream.

Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/49 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 November 2020 09:45:16 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:52 UTC