Re: [webrtc-svc] should scalabilityMode be an array scalabilityModes? (#50)

I would say that we already have a similar problem if we configure the rtp sender to use simulcast but then after negotiation the receiver is not able to do that. The application would have to query the updated parameters to be aware of the fact.

In that regard, scalability mode would work the same. You would set your svc mode based on your preferred codec, but you would have to query after the remote description is set to check if that codec is used and if the scalability mode is actually supported.

Also, I think there are two different scenarios:
- The scalability mode is supported by  a codec supported by the receiving side, but not for the negotiated preferred codec.  Should the scalability mode affect the codec chosen by the sending side?
- The scalability mode is not supported by any negotiated codec. Should we just silently fail and set the scalabilitymode to null on the encoding parameters?

Regarding the question about simulcast and svc, just minor clarification, I assume you are meaning simulcast and spatial svc, as simulcast and spatial svc would not have any issue to be supported.

On the case of simulcast and spatial svc, I think that the proposed solution was not to allow both to be set simultaneously. 



-- 
GitHub Notification of comment by murillo128
Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/50#issuecomment-951336825 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 21:14:10 UTC