Repository navigation
Marker / image tracking spec status #5
Description
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
Reacted by croixbk, Paul Wolff, Brian Peiris and Paul Kretschel
Activity
Maksims commentedon Mar 23, 2021
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.
reconlabs-sergio commentedon Jun 28, 2021
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.Maksims commentedon Jun 28, 2021
This is Specs repo, and for implementation bugs, please use https://bugs.chromium.org/p/chromium/issues/list (for Chrome).
Adolar13 commentedon Jul 13, 2021
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!
klausw commentedon Jul 13, 2021
@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
klausw commentedon Jul 13, 2021
@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.
TomDDH commentedon Jul 21, 2021
hey, I am new to this, is there a live demo I can learn from?. thanks.
klausw commentedon Jul 21, 2021
klausw commentedon Jul 21, 2021
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.
TomDDH commentedon Jul 22, 2021
Thanks very much, look very robust.
klausw commentedon Aug 24, 2021
/agenda to discuss draft image tracking specification
klausw commentedon Sep 7, 2021
Related links for context:
gjcope commentedon Oct 14, 2021
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.
fabian-muff commentedon Mar 10, 2022
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.
Thaina commentedon Apr 7, 2022
So the name of component is
marker-trackingbut the feature string for session isimage-tracking? or is it a feature stringmarker-trackingwith difference result? Sorry for bother you but I am really confused