Re: [webrtc-encoded-transform] generateKeyFrame takes a "rid" argument, but is invoked with "rids" (#143)

> if someone receiving a low-resolution spatial layer joins a conference, this should not trigger an expensive key frame to participants on high spatial layers.

The current API (before and after the proposed change) is allowing this.

One case that seems to be suboptimal is the following (is it the one you have in mind @fippo?):
- Web application wants a key frame from layer A and layer B, it does not need one for layer C
- UA simulcast encoder is, sadly, generating a key frame for all layers whenever asked a key frame of one layer.
- If web application calls generateKeyFrame(A) and generateKeyFrame(B), will it receive twice key frames of all layers or only once?

My answer to once or twice is that this can be dealt by the implementation itself.
And the simulcast encoder issue needs to be dealt with by developers anyway.

One question to web developers is whether there is a use-case for web developers to generate a key frame for 2 layers out of 3, and the key frames needing to have the same timestamp, which is more naturally allowed by passing a sequence than calling twice the API.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/143#issuecomment-3133183620 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 29 July 2025 16:09:49 UTC