EvanBalster

Hello — Pardon the slow reply. No, our software does not incorporate any voice chat function and all record/replay functions are carefully managed. Our team is proficient in sound design and DSP, and we can deal with any acoustic echo or feedback-loop issues that arise.

In case a driver developer should happen to see this thread, here is the relevant Microsoft documentation: https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/audio-signal-processing-modes Raw mode is listed right at the top of the page.

Hello — (I started an earlier thread in the Audio SDK forum, but this issue is unrelated to spatial audio so I'm posting in general support.) We're making SoundSelf, an accessible voice-driven experience for Vive. The player interacts with the game by making sustained tonal sounds with their voice. However, Vive's noise suppression algorithm identifies any sustained sound (>.75s) as background noise, and cuts it (-40-60dB) from the signal. In our case, this means Vive is deleting player input — making our experience unplayable. Like most voice-recognition technologies, our te

Our product is designed to work with all current OpenVR headsets including Vive and Vive Pro. The driver for the Vive microphone should implement WASAPI raw mode, or some other method allowing applications to bypass its noise suppression.

Hello — We're making SoundSelf, an accessible voice-driven experience for Vive. The player interacts with the game by making sustained sounds with their voice. However, Vive's noise suppression algorithm identifies any sustained sound longer than 3/4 of a second as background noise, and attenuates it by 40-60 dB. Unfortunately, this makes our game unplayable on the Vive platform — the player's input is being deleted. Like other voice-perception technologies, our technology works best with unprocessed audio. Windows 10 includes a "raw" flag in its audio API for voice recognition app