0.1.1

Tacspeak - speech recognition for gaming

v0.1.1 - minor update

This release doesn't include a pre-trained model download, but a pre-trained model is required to run Tacspeak!
Please download / use the pre-trained model from the 0.1 release.
download model from 0.1 release

Changes:

• added optional arg "--print_mic_list" that will help with setting "input_device_index" (if required)
• Ready or Not grammar module - added alt word "secure" for search the room. disabled individual team member commands (waiting on keybinds)

---

Additional info:

If you're having issues with audio devices, and setting the default in Windows doesn't help, you can now run ./tacspeak.exe --print_mic_list in Powershell or command prompt to help with setting input_device_index.

• This will list all of the audio devices found on your system, and can be useful for figuring out the correct index number for the input_device_index setting in ./tacspeak/user_settings.py.
• A far easier option to try first is to set the correct default recording device in Windows Sound Settings.

Also related info - the underlying model that Tacspeak currently uses is based on "16-bit Signed Integer PCM 1-channel 16kHz" audio. Tacspeak tries to convert the incoming audio from your device to this format, but if it's too much for a single CPU core to convert in real-time it may fall over.

• I've had no issues using Tacspeak with a 48kHz, 16-bit, 2-channel microphone array and also using a Rode AI-1 and Podmic at 48kHz, 24-bit, 1-channel.
• If, for example, your device is recording at 144kHz, or something a single core on your CPU can't handle, it will likely display errors in the console.