- From: Max Solodovnikov via GitHub <sysbot+gh@w3.org>
- Date: Thu, 29 Sep 2022 06:38:18 +0000
- To: public-webrtc-logs@w3.org
(https://github.com/w3c/webrtc-encoded-transform/pull/132/commits/36c965efd25a6e48bf938ebe0e349d367f8355e2) removed ability to request keyframes on a sequence of RIDs. This imposes some unnecessary limitations, as now when applications need to request keyframes on N (N>1 && N<MAX_RIDS) RIDs, to guarantee video fluidity for a wide range of receivers, they can no longer do this optimally. With currently proposed API, application willing to request keyframes on 2 RIDs will need to either call into API 2 times (providing RID N and RID M as arguments), or 1 time (providing no arguments). Choosing between the 2 will require applications to know implementation details and limitations, which is not always possible. E.g. if user agent emits keyframes on all RIDs even when asked for a single RID, applications should prefer option 1. If user agent emits keyframes only on specific RIDs, application should prefer option 2. Having applications to implement such heuristic is something we can easily avoid, by offering a more flexible API that **ALWAYS** takes sequence of RIDs. -- GitHub Notification of comment by solmaks Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/143#issuecomment-1261833153 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 29 September 2022 06:38:20 UTC