- From: vitaly-castLabs via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Aug 2024 14:28:53 +0000
- To: public-webrtc-logs@w3.org
I wonder if it's the right place complain about mandatory `controller.enqueue` (https://github.com/webrtc/samples/blob/gh-pages/src/content/insertable-streams/endtoend-encryption/js/worker.js#L81)? My use case is that I get AES-encrypted audio/video frames from WebRTC and feed them into the browser via MSE, which is a one-way process and I never get decrypted frames back. Hence I have nothing to enqueue, but if I don't enqueue anything, most WebRTC implementations will start firing PLIs non-stop -- GitHub Notification of comment by vitaly-castLabs Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/106#issuecomment-2278079922 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 August 2024 14:28:54 UTC