-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Framerate knob for simulcast #412
Comments
How about this? partial dictionary RTCRtpEncodingParameters { maxFramerate of type unsigned long A remaining question: how is the receiver's maximum framerate determined? This could be codec-specific, because a device might support hardware decoding for one codec, but not another. Since not all codecs include a max-fr SDP parameter (e.g. VP8 does, but H.264 does not), this value cannot be determined from SDP for all codecs. Do this imply that we need to add maxFramerate as a generic codec capability in RTCRtpCodecCapability? Today, all we have is mimeType. |
Added maxFramerate to RTCRtpEncodingParameters, addressing Issue 412: #412
This issue has been flagged for discussion at the interim on Thursday, Slides placeholder: https://docs.google.com/presentation/d/1qfaxn8GMplm__s_ejMq6C3atA_pBnGXsjmAkKNIh3Ds/edit#slide=id.gf7328a83a_1_27 |
At the interim, I believe that consensus was to leave maxFramerate in the spec, and not put in another framerate knob. If so, this issue can be closed. |
The discussion at TPAC concluded that we need a knob to control framerate per stream when simulcast is used.
The text was updated successfully, but these errors were encountered: