- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Apr 2022 14:58:07 +0000
- To: public-webrtc-logs@w3.org
> how do you plan on implementing this? This is a problem with or without these changes. The spec allows implementations to trigger a key frame to all related encoders when only one is actually requested. If we wanted to go with https://bugs.chromium.org/p/webrtc/issues/detail?id=10107#c4, I think we would then remove the rid parameter entirely. Given this API is based on an initial Google proposal that was already exposing the rid parameter, there might be a possibility to fix https://bugs.chromium.org/p/webrtc/issues/detail?id=10107, at least in some cases. @alvestrand thoughts? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/132#issuecomment-1092958525 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 April 2022 14:58:08 UTC