- From: Philipp Hancke via GitHub <noreply@w3.org>
- Date: Fri, 01 Aug 2025 23:52:29 +0000
- To: public-webrtc-logs@w3.org
> Chrome doesn't work for some reason https://github.com/fippo/simulcast-playground/commits/gh-pages/encrypted.html has worked ever since 2020, as has https://wpt.fyi/results/webrtc-encoded-transform/tentative/RTCPeerConnection-insertable-streams-simulcast.https.html?label=experimental&label=master&aligned > Or encoded frames from all layers sent through the same transform? Since the transform is per transceiver you would get the different simulcast streams on the same transform with different SSRCs (debunking the good old myth about rids and mids) on the sender side. On the receiver side the simulcast playground trick obviously means different transforms. > Either way, JS will be called once per layer, so how is JS expected to avoid calling generateKeyFrame() 3 times? What is the use-case for requesting a key frame from inside the transform? For E2EE the use-case is a new person joining the room, the key being ratcheted and (to minimize delays) generating a keyframe. This is not triggered by a frame but by an operation outside the transform. See #147 for accessing mid and rid as part of the encoded frame and the lack thereof. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/143#issuecomment-3146023578 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 August 2025 23:52:30 UTC