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

[zfox23]

Trello card link

[github-actions]

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

[aranlunzer]

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]

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

[aranlunzer]

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]

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

[aranlunzer]

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.