Troubleshooting voice related problems

Moderator: Jim Bretti

Post Reply
Jim Bretti
Posts: 1558
Joined: Wed Oct 29, 2003 11:07 am
Contact:

Troubleshooting voice related problems

Post by Jim Bretti »

The purpose of this post is to help with troubleshooting some common problems we run across that are related to voice engines and/or the Sapi speech interface

Common Errors

No voices were found
This error is displayed during TextAloud startup if TextAloud is not able to find any voices on your system. A reboot may fix this, and it is also possible that reinstalling your voices may help with the error. Contact support@nextup.com for help with this problem. See the bottom of this post for instructions on sending debug information to support.

A Sapi or Engine component required by TextAloud is not installed correctly
This problem almost always indicates some type of installation problem, either with a voice engine or with some component of the Sapi speech interface. The first thing to do is to test any other voices you have installed, this will help narrow the problem down to a voice related problem, or a problem with Sapi. If the problem is with a voice engine, reinstalling the voice will frequently fix the problem. If you're seeing problems with all voices, and you're running Windows XP, you can try running the FixRegistry utility (see below).

Audio device related errors
Occasionally when trying to speak text you'll get an audio device related error. Examples are "Wave device is not supported" and "No wave out devices available on system". These kinds of errors usually means there is some kind of audio problem on your system, see the post "Troubleshooting Audio Problems" at http://nextup.com/phpBB2/viewtopic.php?f=15&t=6077

OLE Error 80040247
This error is generated by AT&T voices when something on your machine is interfering with the AT&T background process, nvdesktopproxy.exe. The problem is typically related to virus scanners and/or firewalls, and has been reported with Nod32 antivirus and Lavasoft Personal Firewall. Usually, the fix for this problem is to add executables for Natural Voices to the exclusion list of the antivirus / firewall. In a typical AT&T install, these executables are located in C:\Program Files\ATTNaturalVoices\TTS1.4\Desktop\bin. This problem can also be intermittent, so sometimes it takes some work to get it fixed completely.

OLE Error 80040014
This problem normally indicates a problem with the directory structure of the AT&T voice install. All AT&T voices must be installed using the same installation directory, using different install directories is frequently the cause of this problem. Normally, uninstalling all AT&T voices and reinstalling will fix the problem. When reinstalling, we recommend using the default installation directory, but if you need to use a different directory, be sure to use the same install directory for each AT&T voice.

OLE Error 80040018
Same as above OLE Error 80040014

OLE Error 8004503A
If you see this error on Windows 8 when using Microsoft voices, the problem generally has to do with some corrupt registry entries for the Microsoft voices. See http://nextup.com/phpBB2/viewtopic.php?f=15&t=6641 for more information.

OLE Error 80070057 - Only one top level element is allowed in an XML Document
The first thing to check for this problem is for syntax errors related to using tags. If you're using xml tags in the text to change voices, change speed, etc, TextAloud does some level of xml validation, but there are some syntax problems that can get through. So if you are using tags, check for syntax problems, and if you are using 'end tags', make sure that start and end tags are paired correctly, and there are no extra end tags in the text. Examples of end tags are </voice> and </rate>

Access violations in module LOQTTS6.dll
These errors are generated by Lo quendo voices, these voices are not supported by TextAloud at this time.

The FixRegistry Utility (Windows XP only)

If you are running Windows XP, we have a utility you can download that checks for some common sapi installation problems and repairs them. The utility is called FixRegistry, and you can download the utility from http://www.nextup.com/files/FixRegistry.zip.

Unzip the FixRegistry utility to an empty folder. Then, if your windows login does not have administrator privileges, logout and login as an administrative user. Run the FixRegistry program, and click the “Check Registry” button to scan your registry. If the utility finds any problems it can repair it will enable a Repair button. If that happens, go ahead and click Repair.

If there are any errors the utility is unable to repair, please contact support@nextup.com. In your email, included the error messages reported by FixRegistry.

If none of this helps ...

If you're still having problems, please contact support@nextup.com. If possible, it will help if you attach TextAloud debug information to your email. To attach debug information, go to the TextAloud main window, and click Help -> Open Data Folder. Locate the files TextAloudMP3.dbg, TextAloudMP31.dbg, TextAloudMP32.dbg and TextAloudMP33.dbg, and attach them to your email. If you are having problems getting TextAloud started, you can also locate the debug files by clicking the Start button on your machine, open the TextAloud folder, and click the Open Data Folder menu entry.
Jim Bretti
NextUp.com
Post Reply