Framerate knob for simulcast #412

Closed
stefhak opened this Issue Dec 3, 2015 · 3 comments

Projects

None yet

5 participants

@stefhak
Contributor
stefhak commented Dec 3, 2015

The discussion at TPAC concluded that we need a knob to control framerate per stream when simulcast is used.

@aboba
Contributor
aboba commented Dec 9, 2015

How about this?

partial dictionary RTCRtpEncodingParameters {
unsigned long maxFramerate;
};

maxFramerate of type unsigned long
The maximum framerate to use for this encoding.

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.

@aboba aboba added a commit that referenced this issue Dec 10, 2015
@aboba aboba Issue 412: Framerate knob for simulcast
Added maxFramerate to RTCRtpEncodingParameters, addressing Issue 412: 
#412
03a64e7
@aboba aboba added the PR exists label Dec 10, 2015
@aboba aboba was assigned by elagerway Dec 15, 2015
@elagerway
Contributor

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

@aboba
Contributor
aboba commented Jan 19, 2016

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.

@alvestrand alvestrand closed this Jan 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment