Voice not listed in Vista 64 Ultimate drop down

Voices aren't working properly?

Voice not listed in Vista 64 Ultimate drop down

Postby Kaliaila » Fri Dec 19, 2008 11:17 am

I've installed voices on my new computer and it is not listing them in the drop down when you go to the Text to Speech section. It only lists the Microsoft ones. The voice shows up fine in the Cepstral program but I can't seem to find it with windows. Do I need to do something different?

Windows Vista Ultimate x64 is what I am running.
Kaliaila
 
Posts: 1
Joined: Fri Dec 19, 2008 10:56 am
Location: SE Central IL

Issue with registry settings on installation

Postby AdamW » Sat Dec 20, 2008 11:38 am

Cepstral engineering has identified an issue with installation on both XP-64 and Vista-64. It has to do with the 32-bit "magic" occurring in the registry at installation time, given that our libraries are 64-bit libraries. We are working on identifying the failure scenarios and suitable workarounds until we fix all of them.
AdamW
 

Postby lap0918 » Sat Jan 03, 2009 11:48 pm

I am running Windows Home Premium-64 and when looking in the control panel under "Text to Speech", it does not list my purchased voice. There is, however, and icon to view a 32-bit control panel and it is listed there. I was able to install a 32-bit version of the application I was using and it finally started to work in the application.
lap0918
 
Posts: 1
Joined: Sat Jan 03, 2009 11:28 pm

Update?

Postby acarbon » Sun Feb 08, 2009 4:47 pm

Are there any updates to this i am leary about purchasing more licenses until this problem is addressed.
acarbon
 
Posts: 1
Joined: Sun Feb 08, 2009 4:45 pm

One solution...

Postby tgrand » Sun Feb 08, 2009 7:46 pm

Thanks to lap0918 for the hint! I just ran into this issue on Windows 7 x64. I couldn't find any UI to bring up a 32-bit TTS control panel, so I created a shortcut to the normal TTS control panel and looked at its contents with a hex editor. It was running sapi.cpl. I searched my system for sapi.cpl and found a separate 32-bit version at C:\Windows\SysWOW64\Speech\SpeechUX\sapi.cpl. When I ran that, I was able to select my Cepstral voice as the default voice and my 32-bit apps picked up on it successfully. I don't do TTS in any 64-bit apps (yet).
tgrand
 
Posts: 1
Joined: Sun Feb 08, 2009 7:39 pm

Postby Paul » Tue Apr 14, 2009 3:11 pm

The Cepstral voices as of right now are released as 32-bit packages.

All Windows 64-bit systems include a utility called Windows On Windows 64, or WoW64 for short.

The WoW64 Utility allows a 64-bit Windows system to run 32-bit applications however this utility isolates all 32-bit applications from 64-bit applications... meaning that our voices will only work with other SAPI5 compliant 32-bit applications that are installed on the 64-bit Windows system.

For Instance: A user has a 64-bit Windows Machine, the user installs a Cepstral voice and opens Speech settings within the 64-bit control-panel, the Cepstral voice cannot be selected as the default voice inside this control-panel... Now the user opens the 32-bit control-panel, opens the speech settings, the Cepstral voice is selectable because this control-panel is 32-bit.

A lot of SAPI5 compliant application distributors still offer the 32-bit version of there software, so try downloading and installing the the 32-bit version of there software, our voices should work with the 32-bit version.
Live, Laugh, Love..
Paul
 
Posts: 19
Joined: Fri May 16, 2008 5:15 pm

Postby Soltanis » Sat Sep 12, 2009 3:41 am

Is there any more information available about 64bit support?

Can we expect a 64bit 5.x's to be released or are we going to have to wait for 6.x's?
Soltanis
 
Posts: 1
Joined: Sat Sep 12, 2009 3:33 am

Postby AdamW » Sat Sep 12, 2009 10:07 am

Indeed we are working on 64-bit support for both Windows and Mac. It will be a 5.x release. It is coming very soon.
AdamW
 

Postby robbiex » Thu Nov 26, 2009 10:57 am

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).
A third possibility is Cepstral's Callie. I believe that this is still
available only as a 32 bit Voice. The demo version has some glitches.
Testing with Microsoft's sample program, TTSApp, revealed two
problems that we haven't encountered with any other Voice. Text
highlighting doesn't track properly even when the TTS has not been
interrupted with a "nag" statement and the program hangs when a
stop is requested before the end of the text that is being spoken.


As others have already mentioned in this forum, there is a well known
fix that permits the display of all the 32 and 64 bit 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.

This fix works properly except for one unfortunate problem
that occurs with use of a Visual Basic program to interface with the
SAPI 5+ library.

The Visual C/C++ statement

hr = m_cpVoice.CoCreateInstance( CLSID_SpVoice );

correctly sets up a Voice object regardless if the default
system Voice is 32 or 64 bit.

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 current 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.

We have had considerable discussions with Microsoft about this
problem and they appear to be unwilling to correct it.
There are several possible fixes as follows.

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.

It may be possible to modify the Voice registry entries so
that 32 bit Voices work with the 64 bit 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".

Finally, the registry entries can be programmatically changed so
that the default Voice meets the requirements of
"Voice = New SpeechLib.SpVoice" only for this one statement. The
original default entries are then immediately replaced prior to further
usage of the Voice object.
It is far from perfect, but we have chosen this approach as the
best current compromise for our programming environment. One
unfortunate limitation is that Windows 7 64 bit and Windows Server
2008 R2 use different TTS registry directory paths and Values for
DefaultTokenId. Note that these operating systems are identified by
the same "6.1" major and minor version numbers and it is necessary
to check both the version numbers and the operating system names.
Incidentally, an invaluable tool for working with the registry is
Registry Workshop for X64. It can do copy/paste in addition to
multiple other helpful registry operations.

The following code snippet demonstrates the methodology.


'Created inside Form_Load and released inside Form_Unload.

Dim WithEvents Voice As SpeechLib.SpVoice
Dim modifyRegistryFlag As Boolean = False

'Code snippet from Form_Load

Dim ret As Integer
Dim keyName, userRoot, subkeys, defaultString, oldString As String
Dim OSName, OSPlatform, OSVersion, versionNumbers As String
keyName = ""
userRoot = ""
subkeys = ""
defaultString = ""
oldString = ""
VersionNumbers = ""
OSName = Trim(My.Computer.Info.OSFullName.ToString)
OSPlatform = Trim(My.Computer.Info.OSPlatform.ToString)
OSVersion = Trim(My.Computer.Info.OSVersion.ToString)
'MessageBox.Show(OSName & vbCrLf & OSPlatform & vbCrLf & OSVersion)
If Len(OSVersion) >= 3 Then
versionNumbers = Mid(OSVersion, 1, 3)
'MessageBox.Show(versionNumbers)
Select Case versionNumbers
Case versionNumbers = "6.0"
ret = InStr(1, OSName, "Microsoft" & Chr(174) & " Windows Server" & Chr(174) & " 2008")
If ret = 1 Then
modifyRegistryFlag = True
'Registry directory for Windows Server
userRoot = "HKEY_CURRENT_USER"
subkeys = "Software\Microsoft\Speech\Voices"
'Default string for Windows Server
defaultString = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MS-Anna-1033-20-DSK"
Else
MessageBox.Show("Cannot Identity Operating System Name starting at: " & ret & vbCrLf & OSVersion & vbCrLf & OSName & vbCrLf & "It should be Microsoft Windows Server 2008", "TTS Error", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Me.Close()
End If
Case versionNumbers = "6.1"
ret = InStr(1, OSName, "Microsoft Windows 7")
If ret = 1 Then
modifyRegistryFlag = True
'Registry directory for Windows 7 64 bit
userRoot = "HKEY_CURRENT_USER"
subkeys = "Software\Microsoft\Speech\Voices"
'Default string for Windows 7 64 bit
defaultString = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MS-Anna-1033-20-DSK"
ElseIf InStr(1, OSName, "Microsoft Windows Server 2008 R2") = 1 Then
modifyRegistryFlag = True
'Registry directory for Server 2008 R2
userRoot = "HKEY_USERS"
subkeys = ".DEFAULT\Software\Microsoft\Speech\Voices"
'Default string for Server 2008 R2
defaultString = "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Speech\Voices\Tokens\MS-Anna-1033-20-DSK"
Else
MessageBox.Show("Cannot Identity Operating System Name starting at: " & ret & vbCrLf & OSVersion & vbCrLf & OSName & vbCrLf & "It should be Microsoft Windows 7 or Windows Server 2008 R2", "TTS Error", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Me.Close()
End If
Case Else
End Select
End If

keyName = userRoot & "\" & subkeys

If modifyRegistryFlag = True Then
'Retrieve name of default Voice
oldString = ""
Try
oldString = Registry.GetValue(keyName, "DefaultTokenId", "-1")
Catch ex As Exception
MessageBox.Show(ex.Message.ToString, "TTS Error:Get Current Default Voice", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Exit Sub
End Try

If oldString = "-1" Then
MessageBox.Show("No DefaultTokenId", "TTS Error:Get Current Default Voice", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Exit Sub
End If

'Set default name to Anna if she is not the default
If oldString <> defaultString Then
'MessageBox.Show(oldString & vbCrLf & defaultString)
Try
Registry.SetValue(keyName, "DefaultTokenId", defaultString, RegistryValueKind.String)
Catch ex As Exception
MessageBox.Show(ex.Message, "TTS Error:Set Default Voice", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Exit Sub
End Try
End If
End If

'Create the voice object
Try
Voice = New SpeechLib.SpVoice
Catch err As Exception
MessageBox.Show("Error Creating SpeechLib Voice" & vbNewLine & err.Message, "TTS Error", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Exit Sub
End Try

'Restore the original default Voice before further use of the Voice object
If modifyRegistryFlag = True Then
If oldString <> defaultString Then
Try
Registry.SetValue(keyName, "DefaultTokenId", oldString, RegistryValueKind.String)
Catch ex As Exception
MessageBox.Show(ex.Message, "TTS Error:Restore Default Voice", MessageBoxButtons.OK, MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
Exit Sub
End Try
End If
End If

Lastly, I should mention that one important reason for wanting 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.
robbiex
 
Posts: 2
Joined: Thu Nov 26, 2009 10:54 am

Status of Fix for 64-bit OS

Postby davek » Sat Nov 28, 2009 1:39 pm

Does anyone know of the status of the 64-bit OS fix/release for any Cepstral voices? I need to have this work in a 64-bit environment to be useful. Is there a beta available that can be used interim until the final version is released?
davek
 
Posts: 1
Joined: Sat Nov 28, 2009 1:35 pm

Postby AdamW » Mon Nov 30, 2009 10:32 am

We have finished the actual engine portion of the development cycle, in that we have an engine that works under 64-bit windows of any ilk. What's left is the installation of dual engines (32-bit and 64-bit) since the absence of either will disable TTS in one class of applications, including sorting out DLL registrations, Control panel, and so forth . But we are close to a Beta with 2 weeks or so.
AdamW
 

Cepstral Voices with Windows 64 bit Operating Systems

Postby robbiex » Wed Dec 02, 2009 8:35 am

Hi Dave,

As discussed in a previous message, with some limitations, you can use Cepstral 32 bit voices with Windows 64 bit operating systems.
There could be problems if the application program is compiled as 64 bit code.
robbiex
 
Posts: 2
Joined: Thu Nov 26, 2009 10:54 am


Return to Troubleshooting

Who is online

Users browsing this forum: Google [Bot] and 0 guests

cron