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

Re: [webrtc-insertable-streams] Additional space in the buffer (#6)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Sun, 29 Nov 2020 15:46:49 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-735413880-1606664808-sysbot+gh@w3.org>
In raw-videoframe-land, the tendency seems to be to declare the input object immutable and create a new buffer for the output object, given that any transform has to read from the input and write to the output (two memory accesses) anyway.
The videoframe object has a destroy() operation that declares its backing store freed; I wonder if it's possible to declare a destroyAndTakeOverAndTransform() operation that creates a new frame while doing an in-place operation on the buffer.

Seems hard.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/6#issuecomment-735413880 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 29 November 2020 15:46:51 UTC

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