- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 May 2021 08:09:25 +0000
- To: public-webrtc-logs@w3.org
Additional thoughts on existing API vs. what we are trying to achieve: - Current API is basically letting web apps do video buffering through canvas. This is all in the hands of the web app, does not expose any underlying memory or buffers from pool, which is great from a compatibility standpoint, but at the cost of being not very efficient (memory copy and format conversion, timing info...) - We envision a more optimised/lower level API where we want to remove some of the memory copies, format conversions and timing issues. This is potentially good for perf but has additional risks that we should mitigate in the API design, hence why we should not think of current API/status quo as something more than an inspiration. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/23#issuecomment-843856036 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 May 2021 08:09:59 UTC