Utterly Voice icon image Utterly Voice title image

Troubleshooting

If you encounter any issues, this page will help you fix them.

Utterly Voice Will Not Start link icon

There are multiple reasons that Utterly Voice may not start correctly:

  • If you do not have write permissions in the directory where you installed Utterly Voice, the application will fail to start, and a popup will explain the issue. Just move the application folder to a location that gives you write permissions.
  • If Utterly Voice cannot detect your default microphone, it will fail to start. Double check that you have configured your microphone correctly.
  • If your problem is not fixed by one of the above, Get Help.

No Utterances Are Recognized link icon

This is probably due to Setup issues or Microphone issues.

Recognition Error Rate Is Very High link icon

See the Improve Recognition page for advice.

Mouse and Keyboard Commands Do Not Work for Certain Applications link icon

Certain applications and some Windows settings interfaces run as administrator. If Utterly Voice is not running as administrator, it does not have permission to control input for administrator applications. This is due to the Windows User Interface Privilege Isolation. If you need to use Utterly Voice for applications that run as administrator, you must also run Utterly Voice as administrator.

To always run an application as administrator, you can follow the Microsoft instructions. Note that you can apply these steps to either shortcuts on your desktop or the actual executable file. You could create one shortcut that runs as administrator and another that does not.

Note that this will pop up a warning every time you start the application. If you want to get rid of the pop up, you should be able to use the task scheduler to run Utterly Voice every time you log on, and specify that the application should run with highest privileges. See step one instructions here. When setting up that task, you should create a trigger for when you log on.

The "show links" command uses the Vimium browser extension.

If this command never works, make sure you have followed the instructions to install and configure this extension.

If this command occasionally does not work, this is probably due to a minor bug in the extension itself, which is a third party extension. To work around this issue, say "cancel" if the Utterly Voice "browser navigate" exclusive mode is still active, then say "reload page", which will reload the current page and reset the Vimium extension for that page.

In addition, if you say "show links" while the cursor is in an editable text field, the extension will not work as expected. You have to remove focus from the text field first. In this case, you can use the "show force links" command, which presses "escape" to remove focus before running the extension.

Many Commands Suddenly Not Working link icon

Check the "Modes" list in the user interface. If there is a single exclusive mode there, this means that the only commands being processed are those that the exclusive mode allows. For most exclusive modes, you just need to say "cancel" to exit the exclusive mode.

Check the "States" list in the user interface. If you currently have a key or mouse button held, many commands will behave strangely, unless they are expecting the key or button to be held. This might happen if you say "hold shift" to select text, then forget to say "release shift".

YAML Errors link icon

If you edit a settings file, and Utterly Voice displays an error about the file at startup, you probably entered invalid YAML. The easiest way to find the problem in your file, is to use an online YAML validation tool. These tools will show you exactly where the problem is. There are many tools that perform this. One recommended tool is YAML Lint.

Get Help link icon

To ask questions about the application, use our Google Group or Reddit community. If you are not receiving email messages, be sure to check your spam folder.

If you experience any errors that you cannot resolve, you can also contact us privately via the email address on the about page. Please provide a detailed description of the problem, and attach a log file that was captured when the problem occurred. This log file is named log.txt, and it is found in the application directory. Every time the application starts, the log file is overwritten. Be sure that your log file does not contain any confidential information before sending it to us.