Skip to content

Commit 5e85d95

Browse files
fippofippo
committed
what the heck and why not
1 parent 32f00c2 commit 5e85d95

File tree

1 file changed

+112
-2
lines changed

1 file changed

+112
-2
lines changed

‎index.bs

Lines changed: 112 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -435,8 +435,61 @@ interface RTCEncodedVideoFrame {
435435
</dt>
436436
<dd>
437437
<p>
438-
The encoded frame data.
438+
The encoded frame data. The format of the data depends on the video codec that is
439+
used to encode the frame which can be determined by looking at the
440+
{{RTCEncodedVideoFrameMetadata/mimeType}}. The following table defines this for
441+
a number of codecs.
439442
</p>
443+
<table class="simple">
444+
<thead>
445+
<tr>
446+
<th>mimeType</th><th>Data format</th>
447+
</tr>
448+
</thead>
449+
<tbody>
450+
<tr>
451+
<td>
452+
video/VP8
453+
</td>
454+
<td>
455+
The data is the "uncompressed data chunk" defined in
456+
[VP8](https://datatracker.ietf.org/doc/html/rfc6386#section-9.1).
457+
The [VP8 payload descriptor](https://www.rfc-editor.org/rfc/rfc7741#section-4.1)
458+
is not accessible.
459+
</td>
460+
</tr>
461+
<tr>
462+
<td>
463+
video/VP9
464+
</td>
465+
<td>
466+
The data is a frame as described in Section 6 of [[VP9]]. The
467+
[VP9 payload descriptor](https://datatracker.ietf.org/doc/html/draft-ietf-payload-vp9#section-4.2)
468+
is not accessible.
469+
</td>
470+
</tr>
471+
<tr>
472+
<td>
473+
video/H264
474+
</td>
475+
<td>
476+
The data is a series of NAL units in Annex B format,
477+
as defined in [[ITU-T-REC-H.265]] Annex B.
478+
</td>
479+
</tr>
480+
<tr>
481+
<td>
482+
video/AV1
483+
</td>
484+
<td>
485+
The data is a series of OBUs compliant to the
486+
["low-overhead bitstream format"](https://aomediacodec.github.io/av1-spec/#low-overhead-bitstream-format)
487+
as described in Section 5 of [[AV1]].
488+
The [AV1 aggregation header](https://aomediacodec.github.io/av1-rtp-spec/#41-rtp-header-usage) is not accessible.
489+
</td>
490+
</tr>
491+
</tbody>
492+
</table>
440493
</dd>
441494
</dl>
442495

@@ -563,8 +616,65 @@ interface RTCEncodedAudioFrame {
563616
</dt>
564617
<dd>
565618
<p>
566-
The encoded frame data.
619+
The encoded frame data. The format of the data depends on the audio codec that is
620+
used to encode the frame which can be determined by looking at the
621+
{{RTCEncodedAudioFrameMetadata/mimeType}}. The following table defines this for
622+
a number of codecs.
567623
</p>
624+
<table class="simple">
625+
<thead>
626+
<tr>
627+
<th>mimeType</th><th>Data format</th>
628+
</tr>
629+
</thead>
630+
<tbody>
631+
<tr>
632+
<td>
633+
audio/opus
634+
</td>
635+
<td>
636+
The data is Opus packets, as described in
637+
[section 3](https://datatracker.ietf.org/doc/html/rfc6716#section-3)
638+
of [[OPUS]].
639+
</td>
640+
</tr>
641+
<tr>
642+
<td>
643+
audio/PCMU
644+
</td>
645+
<td>
646+
The data is a sequence of bytes of arbitrary length, where each byte is a u-law
647+
encoded PCM sample as defined by Table 2a and 2b in [[ITU-G.711]].
648+
</td>
649+
</tr>
650+
<tr>
651+
<td>
652+
audio/PCMA
653+
</td>
654+
<td>
655+
The data is a sequence of bytes of arbitrary length, where each byte is
656+
an A-law encoded PCM sample as defined by Tables 1a and 1b in [[ITU-G.711]].
657+
</td>
658+
</tr>
659+
<tr>
660+
<td>
661+
audio/G722
662+
</td>
663+
<td>
664+
The data is G.722 audio as described in [[ITU-G.722]].
665+
</td>
666+
</tr>
667+
<tr>
668+
<td>
669+
audio/CN
670+
</td>
671+
<td>
672+
The data is Comfort Noise as described in
673+
[section 3](https://www.rfc-editor.org/rfc/rfc3389#section-3) of [[RFC3389]].
674+
</td>
675+
</tr>
676+
</tbody>
677+
</table>
568678
</dd>
569679
</dl>
570680

0 commit comments

Comments
 (0)