-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update on access to camera image pixels? #2
Comments
Any update, i'm interested too |
Same |
any updates on this |
My update after research is that this feature is under Dev trials on chrome for Android under WebXR. More info. can be found here - Hope this helps someone |
More specifically, this is addressed by the WebXR Raw Camera Access Module, see the draft spec and explainer. For sample code, check out this barebones example and using OpenCV ArUco marker tracking. The feature is enabled by default in Chrome Canary >= 107.0.5304.0. For current stable Chrome, you need to enable "WebXR Incubations" in chrome://flags . |
This is awesome, thanks for the info. |
@klausw thanks for the example, do you know why it isn't included in the main webxr-samples website? |
Hello,
I followed @blairmacintyre 's discussion closely regarding the access the camera image pixels when using WebXR. I am not looped in on the latest discussion happening around the spec development and hence my question here.
Currently, I am able to access the camera pose via the webXR API and tried to access the pixel data using various methods (some listed here) Understandably all access to the pixel data is blocked. Is there any way to access the image data?
I am exploring the usage of WebXR and wanted to ask if there has been any update on access to camera image. I also want to document a usecase - At Streem we use AR for customer support. A remote professional can dial in via AR and support a customer remotely. We use CV extensively and connect the video via webRTC. Hence, access to the image data is highly useful with appropriate user permission prompts obviously.
The text was updated successfully, but these errors were encountered: