- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 23 Mar 2021 09:08:32 +0000
- To: public-webrtc-logs@w3.org
> adjust send stream bitrate and trigger key frame right after. 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. 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. > It would be great if we could avoid bundling KF API with insertable streams or any other mechanisms involving heavy per-packet processing, as the latter has impact on power and performance. I agree it would be cumbersome to use, not sure about power impact if frames are not mutated. Cost might be reduced to two thread hops. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-804739935 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 09:08:35 UTC