W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2022

[mediacapture-fromelement] Should RequestFrame() take a timestamp argument? (#97)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Oct 2022 07:53:34 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1416144605-1666252411-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/mediacapture-fromelement:

== Should RequestFrame() take a timestamp argument? ==
Once a frame is generated with RequestFrame(), it is going to be sent out on a MediaStreamTrack, which is eventually consumed by some destination that cares about the relative timing of the frames - so that it can play back evenly at 30 fps, for instance.

RequestFrame() will (I think) generate something that has the timestamp of when reading from the canvas completes; this can be an uneven cadence when processing for generating the canvas is different for different frames.

Should RequestFrame() take a timestamp, so that the application can control what cadence the frames appear to arrive in?

Please view or discuss this issue at https://github.com/w3c/mediacapture-fromelement/issues/97 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 October 2022 07:53:36 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC