- From: Jan-Ivar Bruaroey via GitHub <noreply@w3.org>
- Date: Tue, 15 Jul 2025 20:37:18 +0000
- To: public-webrtc-logs@w3.org
I've found no sign of more than 3 proposals in the [slide deck](https://docs.google.com/presentation/d/1HUx-gh2RlNMCjHNbTjQYvrPcLmov8Sq8MAC7sNxXbB8/edit?slide=id.g1502ae48044_0_63#slide=id.g1502ae48044_0_63). The use of polling in meetings to arrive at general agreement is at the chairs' discretion, and this WG hasn't relied on it much. I'm not aware of any objection recorded in the room or remotely. We have the option of affirming consensus on the list with a Call for Consensus. From https://github.com/w3c/webrtc-encoded-transform/pull/269#issuecomment-3059721140: > The API continues to be unusable for simulcast, see https://github.com/w3c/webrtc-encoded-transform/issues/143#issuecomment-1262202415. Your diagram appears to juxtapose an implementation that only supports per-rid generation with one that takes a custom array. In contrast, the proposed API supports leaving out the rid, which generates keyframes for all layers, which seems easily aggregated into a single call to the encoder. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/143#issuecomment-3075526230 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 July 2025 20:37:19 UTC