@@ -460,7 +460,14 @@ interface RTCEncodedVideoFrame {
460460 The encoded frame data. The format of the data depends on the video codec that is
461461 used to encode/decode the frame which can be determined by looking at the
462462 {{RTCEncodedVideoFrameMetadata/mimeType}} .
463- The following table defines this for a number of codecs.
463+ For <a href="https://w3c.github.io/webrtc-svc/">SVC</a> , each spatial layer
464+ is transformed separately.
465+ <p class="note">
466+ Since packetizers may drop certain elements, e.g. AV1 temporal delimiter OBUs,
467+ the input to an receive-side transform may be different from the output of
468+ a send-side transform.
469+ </p>
470+ The following table gives a number of examples:
464471 </p>
465472 <table class="simple">
466473 <thead>
@@ -486,8 +493,8 @@ interface RTCEncodedVideoFrame {
486493 video/VP9
487494 </td>
488495 <td>
489- The data is a frame as described in Section 6 of [[VP9]] . The
490- <a href="https://datatracker.ietf.org/doc/html/draft-ietf-payload-vp9#section-4.2">
496+ The data is a frame as described in Section 6 of [[VP9]] .
497+ The <a href="https://datatracker.ietf.org/doc/html/draft-ietf-payload-vp9#section-4.2">
491498 VP9 payload descriptor</a> is not accessible.
492499 </td>
493500 </tr>
@@ -643,7 +650,7 @@ interface RTCEncodedAudioFrame {
643650 The encoded frame data. The format of the data depends on the audio codec that is
644651 used to encode/decode the frame which can be determined by looking at the
645652 {{RTCEncodedAudioFrameMetadata/mimeType}} .
646- The following table defines this for a number of codecs.
653+ The following table gives a number of examples:
647654 </p>
648655 <table class="simple">
649656 <thead>
0 commit comments