- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Jun 2023 08:08:07 +0000
- To: public-webrtc-logs@w3.org
Right, there is a mismatch here. The intent was to use the start algorithm that would basically wait for a frame to be available and enqueue it as soon as available, independently on the actual queue size or whether pull was called (no backpressure like on writer side). We should revise this section to align and could use readEncodedData as part of pulling data. Maybe we could revise the back pressure mechanism here, depending on what UAs actually do (Safari has no back pressure here). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/187#issuecomment-1603895231 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 June 2023 08:08:09 UTC