Re: [webrtc-pc] Handling of simulcast errors

@taylor-b @pthatcherg 

1. Prior to calling createOffer(), getParameters() returns the available codecs.  After O/A, it will return the negotiated codecs.  Is it correct to assume that it is always illegal to attempt to remove all codecs?  

Are you saying that setParameters() can return a rejected promise by attempting to remove some but not all codecs?  For example, after O/A, both H.264/AVC and VP8 are in the codec list, and setParameters() attempts to remove VP8, could this result in an error if there are no more H.264/AVC hardware encoding resources?

2. My assumption has been that individual RTCRtpEncodingParameters attributes cannot result in an error unless they are out of the legal range.  For example, if you set scaleResolutionDownBy to 0.48 instead of 0.50, this won't result in an error, the browser will do the best it can.  However, the specification currently isn't very clear about this (e.g. there is no "overconstrained" condition for RTCRtpEncodingParameters). 

3. Too many encodings can be specified in sendEncodings.  Since setParameters() cannot change the number of encodings, is it possible for setParameters() to generate an error because resources to send the number of encodings originally set in sendEncodings are no longer available?  Or would this just result in degraded performance, but not an error? 

-- 
GitHub Notification of comment by aboba
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/763#issuecomment-292415568 using your GitHub account

Received on Friday, 7 April 2017 03:10:05 UTC