search

croquet / microverse

Croquet Microverse (Beta)
Other
181 stars 53 forks source link

Set update rate for Dolby spatial audio to 30ms from 500ms #57

Open zfox23 opened 1 year ago

zfox23 commented 1 year ago

Trello card link

github-actions[bot] commented 1 year ago

Hello @zfox23, thanks for opening your first Pull Request. Someone will review it soon.

aranlunzer commented 1 year ago

It's clear that 500ms is unhelpfully slow, but since every invocation is a network transaction (as well as a local calculation) there is a cost to increasing the frequency. In a session with 5 users, for example, asking the server to update the spatial scene up to 150 times per second seems... over-eager. Maybe try with 100ms?

It would be nice if we could find a guideline from Dolby (or elsewhere?) on a recommended update rate. My searches haven't turned up anything yet.

yoshikiohshima commented 1 year ago

Yeah, I think we need test 30ms and 100ms at one point by ourselves also.

aranlunzer commented 1 year ago

I can see that faster rates would be important for a participant with head tracking - but I don't think we're supporting that yet, right?

yoshikiohshima commented 1 year ago

Microverse works fine with Oculus head set's head tracking.

aranlunzer commented 1 year ago

In that case, maybe we should set the rate depending on whether the user is immersed. Presumably much larger rates of angular change are possible than with the joystick-based interface.