Actually it is not. Scenario is dead simple - adjust send stream bitrate and trigger key frame right after. We do have a mechanism for adjusting bitrate of individual encodings, per encoding key frame triggering is missing fully. 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. -- GitHub Notification of comment by solmaks Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/pull/37#issuecomment-804392136 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Monday, 22 March 2021 21:02:06 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:53 UTC