Audio is currently whatever is set to system default audio. Should route audio from tab into the headset.
Was also curious if we need to have this part of the spec. I think that its probably a implementation detail with no API necessary. Perhaps behavior should be defined though.
IMHO, without any changes to the spec, the audio should be routed to the HMD's output when RequestPresent is called, and return to the default output when exitPresent() is called. Are there some use cases where separate audio should be played on the HMD and desktop speakers?
Flags: needinfo?(kgilbert) → needinfo?(caseyyee.ca)
OK yeah, as long as the behavior is automagically handled by the headset/driver, I think that this is probably be fine left out of the spec. Besides audio mirroring -- which should also be supported by the headset/driver, I don't think there is any need to have a separate output for audio. It would certainly be a fancy feature, but out of scope of this discussion. I think in my particular test case, the audio routing to the headset wasn't happening properly for whatever reason. Because of this, I thought that there may be some kind of hooks required to have audio route properly to the headset.
For the case of Steam VR at least, the default audio source of the PC is switched when the user enters VR. The mirroring of audio is also handled for us, but requires the user to set this up in the Steam VR preferences.
This also seems to be the case for Oculus Rift. I don't think there is any work required here since it appears that the driver automatically handles this.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.