This plugin is based on the original VoiceTrigger plugin written by Almadiel.
It utilises Unity's KeywordRecognizer which listens to speech input and compares the spoken keyword, or words, to a predefined list before triggering the associated event(s)."
This will satisfy the needs of most VAM users, but if you require a plugin that supports both KeywordRecognizer, and the more complex, GrammarRecognizer I would recommend the excellent SpeechRecognition plugin by MacGruber.
This plugin was designed specifically with the VR user in mind, but will work equally well in Desktop mode.
It can be attached to any atom, or used as a scene plugin.
Features of the plugin:
Optional logging of all plugin operations to VAM's message log. Useful when setting up voice triggers.
Display of both the active microphone, and a list of available microphones in the plugin's UI.
Please ensure that the microphone you intend to use with this plugin is set as the Windows default microphone.
This is vital, as the plugin will not work unless you do !
Trigger Add, Edit, and Rename functions in the plugin UI, with a Confirm or Cancel option for each.
User defined minimum Confidence Level settings of Low, Medium and High for command recognition.
For a command to be recognized, Confidence Level must be equal to, or above the set minimum level.
An optional Head Up Display (HUD) provides visual feedback of recognized commands. Useful when testing commands.
An optional HUD warning on loss of VAM window focus. Window focus is essential for the recognizer to work, and it's not obvious in VR when another application steals focus. A loss of focus warning will always be sent to the message log, regardless of HUD setting.
As in Almadiels original, The plugin repurposes the trigger action panels "Name" field, to enter and store the voice commands which trigger each event.
Defined triggers can have a single command, or multiple alternatives for the same command, any one of which will trigger the same event action, or multiple actions if more than one event is defined for the trigger.
A single event action can be defined for a trigger, or multiple event actions, not necessarily requiring a command word, can be added. So long as at least one event action has a command defined, the trigger will be active and listening.
Please note: The dependencies listed are all for the plugin demo scene. The plugin itself has none.
If you like this plugin, please come back and leave a 'Like' and maybe even leave a review to help others in the community.
Try adding the plugin to an 'Empty' atom in a new blank scene, add your commands and save as a subscene if it's just the plugin and commands you want to save.