18:23:35 RRSAgent has joined #immersive-web 18:23:40 logging to https://www.w3.org/2023/10/31-immersive-web-irc 18:23:49 Zakim has joined #immersive-web 18:26:01 Chair: yonet 18:26:25 Agenda: https://github.com/immersive-web/administrivia/blob/main/meetings/wg/2023-10-31-Immersive_Web_Working_Group_Teleconference-agenda.md 18:47:49 Topic: https://github.com/immersive-web/depth-sensing/issues/37 18:59:18 present+ 19:01:18 lgombos has joined #immersive-web 19:02:02 bajones has joined #Immersive-Web 19:03:01 cabanier has joined #immersive-web 19:03:06 present+ 19:05:14 bialpio has joined #immersive-web 19:07:03 present+ 19:07:10 present+ 19:07:23 dylan has joined #immersive-web 19:07:33 present+ 19:07:46 Zakim, choose a victim 19:07:46 Not knowing who is chairing or who scribed recently, I propose cabanier 19:07:53 present+ Laszlo_Gombos 19:08:13 scribenick: lgombos 19:08:40 q+ 19:08:57 atsushi has joined #immersive-web 19:09:10 cabanier: depth sensing, working on exposing depth sensor.. wondering if this attribute is still needed 19:09:19 ack bialpio 19:09:53 bialpio: in our implementation arcore does not care about device orientiation, so mapping is needed between the coordinates, this is the source of this attribute 19:10:39 cabanier: landscape texture, turn the phone, how would that look 19:11:22 bialpio: need to take a look at the spec or the code.. chromium getdepth method has some description 19:12:15 bialpio: xrview coordinates.. multiply with a matric, and get depth buffer (in meters) 19:13:30 cabanier: in our case the depth api returns fov and views.. in our case we try to build it on top of what openxr api returns 19:13:44 bialpio: when you have depth texture, we do not specify the units 19:13:45 Topic: https://github.com/immersive-web/depth-sensing/issues/43 19:14:13 cabanier: when you get the information from teh system, you get swapchain and depth near and far 19:14:46 cabanier: .. depending how you do it pixels might not match 19:15:02 bialpio: even fov is different 19:16:01 bialpio: we have rawvaluetometers.. 19:16:05 cabanier: for us it is always 1 19:16:47 cabanier: when you create projection matrixes, you use fov and depth near and depth far.. there are default values that experience can replace 19:17:34 bialpio: z values are key.. 19:17:51 cabanier: experience shoudl use the same z values as the system 19:18:19 cabanier: I think two approaches - one we return is as new attribute or second completely ignore the session values 19:18:32 bialpio: lets continue discussion on the bug 19:19:07 bialpio: I though resolution of z values could be encoded into rawvaluetometers 19:19:54 Topic: https://github.com/immersive-web/real-world-geometry/issues/40 19:20:27 cabanier: several web developers run into this.. there is a method to recapture the planes 19:20:57 cabanier: it takes a few sec to warm up.. what is long enough ? there should be a signal for "for sure no meshes" 19:21:44 cabanier: what can we do here ? maybe a new event ? 19:22:12 q+ 19:22:22 ack bajones 19:22:56 q+ 19:23:07 bajones: feels like an event..current you expect to poll ? 19:23:09 cabanier: yes 19:23:50 bajones: wonder what the event should be for ? maybe it should be some kind of "update finished event" 19:24:49 bajones: in some system these surfaces are precumputed at the time webxr session created 19:25:21 bajones: in some other system, surfaces are continuously discovered .. need to consider different platforms 19:26:01 cabanier: I also want to make sure we support several systems, including android 19:26:20 ack bialpio 19:26:21 cabanier: if there is an event, than we do not need to look at every frame 19:27:28 bialpio: are we changing the api to be event based (this was considered in the past) ? 19:28:29 bialpio: at least this particular problem, maybe there should be an opt-in to subscribe to this event 19:28:51 bajones: on android scanning never really completes 19:29:27 bajones: conserned about portability of webxr content if we introduce this optional event based api 19:29:53 q+ 19:30:09 cabanier: if it is an event, than content would wait for it to complete 19:30:09 Have to drop here, but FYI XR Access is doing a community discussion on Captioning on Nov 15th. Should have some interesting problem solving around 3D positional metadata for 360 degree captions. https://xraccess.org/community-discussion-captions/ 19:30:27 Thanks all, feel free to reach out anytime on accessibility-related issues - dylan@xraccess.org 19:30:58 bajones: is it reasonable if e.g. on Meta platform the content automatically opt-in for this event ? 19:31:02 cabanier: not really 19:31:51 cabanier: proposal: "needs room setup" event 19:32:13 cabanier: not sure how muti-room would work in webxr 19:32:50 bajones: if it is really just "needs room setup" than we could consider an attribute instead of an event 19:33:24 bajones: event is still also fine 19:33:46 ack bialpio 19:34:00 bialpio: bikeshed "inital room capture" or "room capture needed" 19:34:34 bialpio: is this intent to fire only when openxr finished scanning .. 19:34:48 cabanier: no.. 19:35:06 bialpio: can you arbitrary start a new capture any time 19:35:07 cabanier: yes 19:35:38 bialpio: in the spec "initiate room capture" can be only run once per webxr session 19:36:02 bajones: maybe the event is stated as "room capture is newly avaiable".. 19:36:24 q? 19:36:39 cabanier: if we want to add multi-room support, we anyways need to update current spec 19:37:16 bajones: if the method is "initialize room capture".. maybe the event is "room capture uninitialized" 19:38:05 cabanier: we shoudl try to avoid a website continuously call this.. 19:38:42 Topic: https://github.com/immersive-web/layers/issues/304 19:39:30 cabanier: when you ask for multiple textures we only support left and right.. so only work devices with 2 screens 19:40:00 bajones: algorithm itself is just for 2 views 19:40:35 bajones: we want to expand spec for multiple views per eye (not just 1) 19:41:21 cabanier: the layers spec does not mention left/right eye for secondary views 19:42:06 cabanier: I do not think anybody implemented secondary views 19:42:18 bajones: we put it in the spec as we knew HW is coming 19:42:56 cabanier: for sure we need to improve the spec and need a proposal to review 19:43:39 cabanier: pico headset implemented webxr layers.. Meta is not the only implementation 19:43:58 https://xraccess.org/community-discussion-captions/ 19:44:48 yonet: if there are WG issues, we schedule a meetign in 2 weeks.. 19:45:11 Thank you lgombos 19:45:24 rrsagent, publish minutes 19:45:25 I have made the request to generate https://www.w3.org/2023/10/31-immersive-web-minutes.html atsushi 19:45:44 rrsagent, make log public 19:45:52 Thank you Atsushi 19:46:01 meeting: Immersive Web WG/CG call 19:46:19 agenda: https://github.com/immersive-web/administrivia/blob/main/meetings/wg/2023-10-31-Immersive_Web_Working_Group_Teleconference-agenda.md 19:46:36 present+ yonet 19:46:40 rrsagent, publish minutes 19:46:42 I have made the request to generate https://www.w3.org/2023/10/31-immersive-web-minutes.html atsushi 19:47:43 previous meeting: https://www.w3.org/2023/10/17-immersive-web-minutes.html 19:48:32 rrsagent, publish minutes 19:48:34 I have made the request to generate https://www.w3.org/2023/10/31-immersive-web-minutes.html atsushi