File tree Expand file tree Collapse file tree 1 file changed +7
-10
lines changed Expand file tree Collapse file tree 1 file changed +7
-10
lines changed Original file line number Diff line number Diff line change @@ -331,7 +331,7 @@ dictionary RTCEncodedVideoFrameMetadata {
331331 unsigned long synchronizationSource;
332332 octet payloadType;
333333 sequence<unsigned long> contributingSources;
334- DOMHighResTimeStamp captureTime;
334+ long long captureTimestamp; // microseconds
335335};
336336</pre>
337337
@@ -367,18 +367,15 @@ dictionary RTCEncodedVideoFrameMetadata {
367367 </p>
368368 </dd>
369369 <dt>
370- <dfn>captureTime </dfn> of type <span class=
371- "idlMemberType"> DOMHighResTimeStamp </span>
370+ <dfn>captureTimestamp </dfn> of type <span class=
371+ "idlMemberType"> long long </span>
372372 </dt>
373373 <dd>
374374 <p>
375- For video frames coming from a local source, this is the time at which
376- the frame was captured by the camera.
377- For video frames coming from remote source, the capture time is based on the RTP
378- timestamp of the frame and estimated using clock synchronization.
379- This is best effort and can use methods like using RTCP SR as specified in
380- RFC 3550 Section 6.4.1, or by other alternative means if use by RTCP SR isn’t feasible.
381- As defined in VideoFrameCallbackMetadata.
375+ For video frames coming from a local device, this is the timestamp in microseconds
376+ at which the frame was captured by the camera.
377+ This will have the same value as the basis for VideoFrameCallbackMetadata's captureTime
378+ field.
382379 </p>
383380 </dd>
384381</dl>
You can’t perform that action at this time.
0 commit comments