RTCRtpCodecParameters clock rate nullable? #500

Closed
robin-raymond opened this Issue Apr 24, 2016 · 2 comments

Projects

None yet

2 participants

@robin-raymond
Contributor

clockRate of type unsigned long
Codec clock rate expressed in Hertz, null if unset.

It's not nullable. I think it should just say:

Codec clock rate expressed in Hertz; clock rate is defaulted if unset.

... or something like that....

@aboba aboba added the 1.1 label Apr 25, 2016
@aboba
Contributor
aboba commented Apr 25, 2016

Related to Issue #503

Can we say that it would default to the value included in RTCRtpCodecCapability.clockRate ?

@aboba aboba added a commit that referenced this issue Apr 25, 2016
@aboba aboba RTCRtpCodecParameters clock rate nullable
Fix for Issue #500
182eeaa
@aboba aboba added the PR exists label Apr 25, 2016
@robin-raymond
Contributor

Better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment