Open Ansible2 opened 2 years ago
Useful info on defining grammar files that determine what can be said. https://docs.microsoft.com/en-us/dotnet/api/system.speech.recognition.grammar?view=netframework-4.8
Decent article about specifics of the speech engine (slightly outdated) https://docs.microsoft.com/en-us/archive/msdn-magazine/2006/january/exploring-speech-recognition-and-synthesis-apis-in-windows-vista
A spec for how to use an xml doc as a grammar file https://www.w3.org/TR/speech-grammar/
A tutorial for how to do the equivalent of the xml configuration in code https://docs.microsoft.com/en-us/previous-versions/office/developer/speech-technologies/hh361659(v=office.14)
How To XML: https://docs.microsoft.com/en-us/previous-versions/office/developer/speech-technologies/hh361594(v=office.14) How To SrgsGrammar: https://docs.microsoft.com/en-us/previous-versions/office/developer/speech-technologies/hh361680(v=office.14)
Example of how one could layout a call for fire. https://web.archive.org/web/20220801065507/https://blog.refactortactical.com/blog/call-for-fire/
Goal: Add the ability to call supports with voice input, though, the implementation of this should be so generic that it could theoretically allow any input from voice to create any output to sqf (within the limits of the callExtension command).
Story: As a user, in order to more easily interface with various aspects of arma, I want to be able to provide parameters/actions based on voice input.
tech:
A decent example of this is in https://github.com/Asaayu/integrated-voice-control-system Thought this is a significantly more nuanced approach.