marker-tracking
marker-tracking copied to clipboard
immersive-web
Marker / image tracking spec status
This feature has been a bit quiet recently. As far as I know the current status is that there's a prototype implementation in Chrome behind the "WebXR incubations" flag along with the draft explainer. There was interest from Microsoft (@thetuvix if I remember correctly) to consider expanding it to include QR code support.
Can we schedule some time at one of the immersive-web conf calls to talk about the status and next steps?
/agenda to discuss current status
QR image tracking and the ability to manage images while the session is running - would be a great move forward for an API. I've integrated current specs into PlayCanvas Engine, and from current tests, this is really promising and the community is excited.
Hi @Maksims,
we also integrated the image-tracking capabilities on our web-xr app. However, since a recent chrome update, image-tracking stopped working. Specifically, frame.getPose(result.imageSpace, refSpace); returns always zero position and rotation. I'm curious to know if this is happening on your side, too. I have cannot specifically pinpoint which version is breaking, but I downgraded chrome on a test smartphone to 89.0.4389.105 and I confirm its working. I tried with 91.0.4472.120 and 91.0.4472.77 and its not working.
This is Specs repo, and for implementation bugs, please use https://bugs.chromium.org/p/chromium/issues/list (for Chrome).
Hey,
any update on the spec? We did some pretty cool tests with PlayCanvas and WebXR Image Tracking and it looks super promising. We can't wait to use this in production!
@Adolar13 - there's now a proposed spec at https://immersive-web.github.io/marker-tracking/ . Note that this includes some minor renaming (i.e. "trackability" instead of "trackingScore") which don't currently match the experimental Chrome implementation, the goal is to get that straightened out once there's consensus.
/agenda to discuss proposed spec
@sergiobdrl as noted by Maksims implementation issues should be tracked in the Chromium issue tracker. See https://bugs.chromium.org/p/chromium/issues/detail?id=1224598 for the pose issue. that should be fixed as of Chrome 93.0.4564.0.
Sure, try https://arimg.glitch.me/
On Tue, Jul 20, 2021, 22:07 TomDadongHu @.***> wrote:
hey, I am new to this, is there a live demo I can learn from?. thanks.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/immersive-web/marker-tracking/issues/5#issuecomment-883892613, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKT5X2XUZJHKN3FD2DIFDLTYZIZTANCNFSM4ZT55MDQ .
I'm removing from the agenda for now since I won't be able to make it to the next group call, sorry about the confusion.
Sure, try https://arimg.glitch.me/ … On Tue, Jul 20, 2021, 22:07 TomDadongHu @.***> wrote: hey, I am new to this, is there a live demo I can learn from?. thanks. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKT5X2XUZJHKN3FD2DIFDLTYZIZTANCNFSM4ZT55MDQ .
Thanks very much, look very robust.
Related links for context:
- the current draft spec: https://immersive-web.github.io/marker-tracking/
- meeting minutes from March when we last talked about this: https://www.w3.org/2021/03/23-immersive-web-minutes.html
- focus control for handheld AR issue: https://github.com/immersive-web/webxr/issues/1210
Wondering what the status of the spec is currently. I read the March meeting notes but it wasn't clear to me what the direction was. I've played around with it and think it would be super helpful to our WebXR use (https://github.com/Smithsonian/dpo-voyager) and appreciate the privacy implications of if vs raw camera feed access. Happy to help however I can if things are moving forward.
hello @klausw Can you give us some updates for the status of the image-tracking draft. Will it be included to the standard in near future? It would be great since we could use it then also on the HoloLens (chromium edge) that is not supporting the experimental feature yet.
So the name of component is marker-tracking but the feature string for session is image-tracking ? or is it a feature string marker-tracking with difference result? Sorry for bother you but I am really confused
