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

Use canvas desynchronized rendering #154

Open
germain-gg opened this issue May 3, 2019 · 3 comments
Open

Use canvas desynchronized rendering #154

germain-gg opened this issue May 3, 2019 · 3 comments

Comments

@germain-gg
Copy link
Contributor

It looks like a new WebGLContextAttribute has been introduced. It is called desynchronized and it will optimise in some cases the rendering by bypassing some steps in the redering pipeline.

Interestingly this can create some issues with the alpha option, which is something we should take in consideration when looking at #153 . It will only be a problem if alpha and desynchronized are both set to true and some DOM elements are stacked on top of the canvas element. Which will be very hard to detect within VideoContext and quite hard to explain in an error message.

More info: Low-latency rendering with the desynchronized hint

@PTaylour
Copy link
Contributor

PTaylour commented May 7, 2019

Thanks @gsouquet I'll take a look :)

@PTaylour
Copy link
Contributor

@gsouquet have you used this attribute at all since we last spoke? The demo is impressive.

@germain-gg
Copy link
Contributor Author

We are actually using that in prod for one of our video.
Will try to create a PR for VideoContext. The good news is that we already use preserveDrawingBuffer

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