Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should RequestFrame() take a timestamp argument? #97

Open
alvestrand opened this issue Oct 20, 2022 · 0 comments
Open

Should RequestFrame() take a timestamp argument? #97

alvestrand opened this issue Oct 20, 2022 · 0 comments

Comments

@alvestrand
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants