Can't use additional voices for Text to Speech using Microsoft Speech. Hi I'm trying to install additional voices for Windows 7 narrator and other Text to Speech. Tts voices Windows 7 - Free Download Windows 7 tts voices - Windows 7 Download - Free Windows7 Download.

There are multiple problems with setting a default TTS Voice in Windows Server 2008 R2 and Windows 7 64 bit edition. The Control Panel TTS Voice option lists only properly registered 64 bit Voices.

Microsoft's Anna is the only 64 bit Voice that is supplied with the operating systems. Loquendo's Kate, which is probably the highest quality TTS Voice that is currently available, has both 32 and 64 bit versions. Kate is difficult to obtain in small quantities and is very expensive.

The next best alternative is believed to be the Acapela-Group Voice Heather. It is only currently available in a 32 bit version for the Windows operating systems. (64 bit Heather is available for Apple's Snow Leopard).

There is a fix that permits the display of all installed Voices and the selection of any as the system default Voice. This is to execute: C: Windows SysWOW64 Speech SpeechUX sapi.cpl rather than using the Control Panel TTS Voice selection. Gta Myriad Island Cheats For Pc. This fix works properly except for one unfortunate problem.

The Visual C/C++ statement hr = m_cpVoice.CoCreateInstance( CLSID_SpVoice ); correctly sets up a Voice object regardless of the default system Voice. The Visual Basic statement Voice = New SpeechLib.SpVoice results in a system hang or program abort if the default Voice has been set to anything other than a properly registered 64 bit Voice like Anna. 'Try Catch' doesn't catch this error. Note that Set Voice = CreateObject('SAPI.SpVoice') also fails with the same error. There is no easy solution to this problem. It may, however, be less of concern as more 64 bit TTS Voices become available.

First, Microsoft should certainly change the Control Box TTS selection to use the same code as 'C: Windows SysWOW64 Speech SpeechUX sapi.cpl'. Second, Microsoft should correct the problem with the way in which The Visual Basic statement 'Voice = New SpeechLib.SpVoice' functions. There is no reason for this not to have the same capability as its Visual C/C++ counterpart. Third, application programs that use TTS could be written completely in Visual C/C++, the creation of the Voice object could be in an Visual C ActiveX control or a wrapper could be used to access CoCreateInstance. Fourth, it may be possible to modify the Voice registry entries so that 32 bit Voices work with the Control Panel TTS listing.

It is easy to modify the registry so that the Voices are displayed. There is, however, a consistent error message regarding a failure of audio output. The TTS registry entries are generally well documented.

Unfortunately, there are multiple entries for which there is no publicly available documentation. This plus a lack of technical assistance from either the third party vendors of TTS Voices or Microsoft makes it impossible to resolve the registry entry problem at this time. These registry issues are not a concern when you use 'C: Windows SysWOW64 Speech SpeechUX sapi.cpl'. Fifth, One important reason for being able to change the system default TTS Voice is to provide an alternate Voice choice for programs like MapPoint which automatically select the system default Voice. There is no other user option for changing MapPoint's Voice. There is a MapPoint registry key at HKEY_CURRENT_USER Software Microsoft MapPoint 17.0 USA PreferredTTSEngine that looks as if the TTS Voice can be selected. Unfortunately, there is no documentation for this entry and changing the Voice name doesn't override the system default Voice.