- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Oct 2021 07:25:35 +0000
- To: public-webrtc-logs@w3.org
> 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. True. That is probably worth pointing out in webrtc-pc (and should be asserted with a test) But you don't need to do this if the UA is granted some flexibility (while allowing enough control) > Also, I think there are two different scenarios: [...] Agree. I also assume that client and server announce and negotiate scalability modes out of band (coming back to the above, why check after sdp negotiation if you can ignore it and set what is appropriate) There is a third scenario: if you do replaceTrack and replace camera with screenshare the libwebrtc implementation will behave very different. If the UA is constrained to a single encoding via scalabilityMode should there be an error? -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/50#issuecomment-953573374 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 October 2021 07:25:37 UTC