- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Jan 2021 08:26:58 +0000
- To: public-webrtc-logs@w3.org
The approach pioneered by WebCodec is that the frame has a destroy() method, and an API requirement that destroy() has to be called before the frame is released; if the frame is passed to a MediaStreamTrackGenerator, this will be handled by the generator. The practical limit on outstanding frames in the Chrome implementation seems to be somewhere larger than 3, but less than 10. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mediacapture-insertable-streams/issues/6#issuecomment-762683130 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 January 2021 08:27:00 UTC