You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: index.bs
+20-7Lines changed: 20 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -81,15 +81,16 @@ It uses an additional API on {{RTCRtpSender}} and {{RTCRtpReceiver}} to
81
81
insert the processing into the pipeline.
82
82
83
83
<pre class="idl">
84
-
typedef (SFrameTransform or RTCRtpScriptTransform) RTCRtpTransform;
84
+
typedef (SFrameSenderTransform or RTCRtpScriptTransform) RTCRtpSenderTransform;
85
+
typedef (SFrameReceiverTransform or RTCRtpScriptTransform) RTCRtpReceierTransform;
85
86
86
87
// New methods for RTCRtpSender and RTCRtpReceiver
87
88
partial interface RTCRtpSender {
88
-
attribute RTCRtpTransform? transform;
89
+
attribute RTCRtpSenderTransform? transform;
89
90
};
90
91
91
92
partial interface RTCRtpReceiver {
92
-
attribute RTCRtpTransform? transform;
93
+
attribute RTCRtpReceiverTransform? transform;
93
94
};
94
95
</pre>
95
96
@@ -214,7 +215,7 @@ There is no guarantee on which frame will happen the switch from the previous tr
214
215
If a web application sets the transform synchronously at creation of the {{RTCRtpSender}} (for instance when calling addTrack), the transform will receive the first frame generated by the {{RTCRtpSender}}'s encoder.
215
216
Similarly, if a web application sets the transform synchronously at creation of the {{RTCRtpReceiver}} (for instance when calling addTrack, or at track event handler), the transform will receive the first full frame generated by the {{RTCRtpReceiver}}'s packetizer.
216
217
217
-
# SFrameTransform # {#sframe}
218
+
# SFrame transforms # {#sframe}
218
219
219
220
<p>
220
221
The APIs presented in this section allow applications to process SFrame data using specific cipher suites defined in [[RFC9605]].
0 commit comments