-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[webgl] allow direct WebGL tensor creation/retrieval using texture handle #3937
Comments
This would be really great!! :) You might need to be able to share a WebGL context with the user's application. Not sure if this would be a new API function or wrapped into something else. The user will probably know which canvas or OffscreenContext will want to use TFJS data, and could pass a reference to TFJS. Just a thought... Previous discussion @ #1607. |
Would also need a similar setup for WebGPU in the future :-) |
Hi guys! |
The |
we are in the process to unify the texture to tensor API across webgl and webgpu, please stay tuned. |
Thanks a million for your answer. I have a hope now 😃 |
Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information
Describe the feature and the current behavior/state.
For ML models that involve media processing (i.e. bodypix model), there are couple places where expensive data copying could happen:
Proposing two new tensor APIs to solve above problems, these APIs target tensors that are located on WebGL backend:
Will this change the current api? How?
This would not change any of the current APIs, and the proposed APIs shall throw exception for tensors that are not on WebGL backend.
Who will benefit with this feature?
Media processing pipeline that utilize TFJS for model execution with WebGL acceleration.
Any Other info.
The text was updated successfully, but these errors were encountered: