- From: Max Solodovnikov via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Mar 2021 11:12:11 +0000
- To: public-webrtc-logs@w3.org
> I see. In the case of simulcast, you would like to trigger a key frame for one encoding but not the others. > The closest API surface we have here is RTCRtpSendParameters.encodings. Yes, this is what I was thinking of as well. This new parameter might need a special treatment though, as it is transient in nature. I.e. configuring it on an encoding and reading it back would not make much sense. > I would have hoped that, when we go from active=false to active=true, video encoders would start with a key frame. > Maybe this is something we could agree on. Unfortunately active=false/true might have undesirable side-effects, such as actually suspending video stream prior to generating a key frame. Idea is to be able to generate a key frame on a continuous stream. Let me reiterate the scenario, update send bitrate on an already active stream, and request KF to be generated with new bitrate constraint being effective. -- GitHub Notification of comment by solmaks Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-804817718 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 23 March 2021 11:12:12 UTC