Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unset encodings in send() #523

Merged
merged 1 commit into from
Apr 28, 2016
Merged

Unset encodings in send() #523

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions ortc.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3371,6 +3371,13 @@ <h3>dictionary RTCRtpParameters</h3>
<dd>
<p>
The "encodings" or "layers" to be used for things like simulcast, Scalable Video Coding, RTX, FEC, etc.
When unset in a call to <code>send()</code>,
the browser behaves as though a single <code>encodings[0]</code> entry was provided, with
<var>encodings[0].ssrc</var> set to a browser-determined value, <var>encodings[0].active</var> set to "true",
<var>encodings[0].codecPayloadType</var> set to <var>codecs[j].payloadType</var> where <var>j</var> is the index
of the first codec that is not "cn", "dtmf", "red", "rtx" or a forward error correction codec, and all the other
<var>parameters.encodings[0]</var> attributes (e.g. fec, rtx, priority, maxBitrate, resolutionScale, etc.) unset.
When unset in a call to <code>receive()</code>, the behavior is described in Section 8.3.
</p>
</dd>
<dt>RTCRtcpParameters rtcp</dt>
Expand Down