- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 25 Oct 2021 20:19:31 +0000
- To: public-webrtc-logs@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-svc: == should scalabilityMode be an array scalabilityModes? == I had some questions regarding negotiation. Lets assume I set L1T3 in addTransceiver. Assuming I set L1T3 and VP8 gets negotiated: yay Assuming I set L1T3 and VP9 gets negotiated: uhm? Assuming I set L3T3 and VP8 gets negotiated: uhm? It does (generally) not make sense for VP9 to do L1T3 (there are use-cases for it) -- not touching renegotiation even. Would it make more sense to specify a list of scalability modes instead of a single one? For example that list could be ``` [L3T3, L1T3] ``` In the case VP9 is negotiated this would pick L3T3. If VP8 gets negotiated this would determine L3T3 does not make sense and fallback to L1T3 (three temporal layers which as we all know users know and like) (related, how does a sender say 'I could do simulcast or svc, pick your poison?) Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/50 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 October 2021 20:19:34 UTC