Improving recognition accuracy never hurts. Many people even have to tweak something to get a good experience. Here we show you what you can do.Contents:
A quiet room will always be better than a noisy one. A good microphone can mitigate this, but sometimes a $0 job will do. Move fans and air filters, rotate your sitting position such that air conditioning is not pointing toward the mic, close a door (and subsitute by taking more breaks for health and ventilation). Move your PC from above desk to below desk, move your PC speakers behind your mic, etc.
Make sure that you have a good microphone and sound card, as speech recognition software requires better hardware than is commonly built in to computers. Have a look at the hardware page for recommendations and correct setup.
Ensure that your voice is not tired, which will lead to poorer pronunciation.
Controlling your computer by voice can be frustrating if your accent isn’t recognized well; non-native speakers are especially prone to issues. While Talon’s engine is improving with each version, in the meantime we can adapt our pronunciation.
https://rachelsenglish.com/ is an excellent resource. It features detailed videos and discussion of the mechanics behind the various sounds. At the risk of saying the obvious: you shouldn’t try to change your accent if you don’t want to.
If only a few specific commands give you trouble, change those command words! Commands are almost exclusively mapped in
.talon files: search for all occurrences of those words, and replace them with a word of your choosing: select one that is easy to pronounce, is not too similar to anything else, and is recognized well for you.
Some important commands are specified in
.py files, like the alphabet. Changing it works the same way, but you need to be more careful about what you modify. If you are not a programmer, ask in the Talon Slack
#help channel if you are unsure!
Example: If the
tab close does not work for you (but
tab open etc. do), try out
tab wipe or
tab quit instead.
zip (letter Z) is always understood as
sit (lette I), change
ivy, or alternatively change
Talon only waits a short amount of time before trying to interpret your command. If you pause even a wee bit longer, Talon will split your utterance into separate phrases.
settings.talonfile to your user directory with the following content:
settings(): # (unstable) minimum silence time (in seconds) before speech is cut off, default 0.150 speech.timeout = 0.200
Start with the value of 0.2, just slightly higher than the default, and increase only if necessary. Beware that this setting uses a private API, and might be modified or removed in future versions. Report your issue in
#help so that we are aware that some people are still having issues with being cut off mid-command/mid-sentence.
If all the above isn’t enough, a few more heavyweight changes are still available:
spell <user.key>+instead of just
<user.key>) you again reduce the number of words to recognize, giving Talon more chance to guide recognition.
This will not help you today, but instead help to improve the talon engine for all of us in the future. You can do this by providing speech (and noise) samples:
TODO: review and extend
airfrom the alphabet; e.g., someone from the UK on the Slack uses
metworks well as a replacement for
whale, there’s also