I downloaded all the Microsoft English voices and installed them.  They all work when I tested them in Windows but when I try to assign them in the VoxATC Voice Configuration I only have Great Briton Hazel available.

Any ideas how to fix?

Garry

garry

firstly ..... fsx & vox652 or P3DV4 with vox742

the first uses 32bit voices, the later 64bit

& are you using W7 or W10

Sorry...should have thought to include that info.  It's VoxATC 742, for P3D v4 and I'm on a 64bit W10 machine.  As I said they work when I tested them in Windows...just Vox doesn't even recognize they are there.

Thanks

Garry

Garry,

How did you install these? Did you install the WIn 10 English UK language pack? The pack only adds entries to the Windows registry that Windows 10 itself cares about. VOXATC uses different entries even though the app is 64 bit like Windows 10. For example, here are the correct entries for Microsoft Mark:

Quote

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MSTTS_V110_enUS_MarkM]
@="Microsoft Mark Mobile - English (United States)"
"409"="Microsoft Mark Mobile - English (United States)"
"CLSID"="{179F3D56-1B0B-42B2-A962-59B7EF59FE1B}"
"LangDataPath"=hex(2):25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,53,\
  00,70,00,65,00,65,00,63,00,68,00,5f,00,4f,00,6e,00,65,00,43,00,6f,00,72,00,\
  65,00,5c,00,45,00,6e,00,67,00,69,00,6e,00,65,00,73,00,5c,00,54,00,54,00,53,\
  00,5c,00,65,00,6e,00,2d,00,55,00,53,00,5c,00,4d,00,53,00,54,00,54,00,53,00,\
  4c,00,6f,00,63,00,65,00,6e,00,55,00,53,00,2e,00,64,00,61,00,74,00,00,00
"VoicePath"=hex(2):25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,53,00,\
  70,00,65,00,65,00,63,00,68,00,5f,00,4f,00,6e,00,65,00,43,00,6f,00,72,00,65,\
  00,5c,00,45,00,6e,00,67,00,69,00,6e,00,65,00,73,00,5c,00,54,00,54,00,53,00,\
  5c,00,65,00,6e,00,2d,00,55,00,53,00,5c,00,4d,00,31,00,30,00,33,00,33,00,4d,\
  00,61,00,72,00,6b,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\MSTTS_V110_enUS_MarkM\Attributes]
"Age"="Adult"
"Gender"="Male"
"Version"="11.0"
"Language"="409"
"Name"="Microsoft Mark Mobile"
"SharedPronunciation"=""
"Vendor"="Microsoft"
"DataVersion"="11.0.2013.1022"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enUS_MarkM]
@="Microsoft Mark Mobile - English (United States)"
"409"="Microsoft Mark Mobile - English (United States)"
"CLSID"="{179F3D56-1B0B-42B2-A962-59B7EF59FE1B}"
"LangDataPath"=hex(2):25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,53,\
  00,70,00,65,00,65,00,63,00,68,00,5f,00,4f,00,6e,00,65,00,43,00,6f,00,72,00,\
  65,00,5c,00,45,00,6e,00,67,00,69,00,6e,00,65,00,73,00,5c,00,54,00,54,00,53,\
  00,5c,00,65,00,6e,00,2d,00,55,00,53,00,5c,00,4d,00,53,00,54,00,54,00,53,00,\
  4c,00,6f,00,63,00,65,00,6e,00,55,00,53,00,2e,00,64,00,61,00,74,00,00,00
"VoicePath"=hex(2):25,00,77,00,69,00,6e,00,64,00,69,00,72,00,25,00,5c,00,53,00,\
  70,00,65,00,65,00,63,00,68,00,5f,00,4f,00,6e,00,65,00,43,00,6f,00,72,00,65,\
  00,5c,00,45,00,6e,00,67,00,69,00,6e,00,65,00,73,00,5c,00,54,00,54,00,53,00,\
  5c,00,65,00,6e,00,2d,00,55,00,53,00,5c,00,4d,00,31,00,30,00,33,00,33,00,4d,\
  00,61,00,72,00,6b,00,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enUS_MarkM\Attributes]
"Age"="Adult"
"DataVersion"="11.0.2013.1022"
"Gender"="Male"
"Language"="409"
"Name"="Microsoft Mark Mobile"
"SharedPronunciation"=""
"Vendor"="Microsoft"
"Version"="11.0"

 

As i recall Win10 only needs the entries at:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\

VOXATC needs the entries at;

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\

To be sure, you'd have to check with the Windows registry editor. You first export the Speech_OneCore entries, edit just the two HKEY lines and change them to Speech. Save the file as <VoiceName>.reg (or whatever). Then click the reg file and reboot. Editing the Windows registry incorrectly can make your computer inoperative, so only do this if you feel competent about such editing. 

Also, if you really adept with the Registry Editor, you can just copy the specific entries from Speech_One to Speech.

I did install the UK language pak...and Hazel works in Vox...but the others don't.  I see when I opened the Registry Editor that Hazel is in both locations.  I also see that when I use the Registry Editor I don't get all those lines of text you show above.  I get a folder titled "Attributes" and then when I open that I just get as you see on the attached screen shot.

I've never touched the Registry Editor so I probably should not be even considering this...unless:

• When you say "really adept"...I'm not
• You say just copy the "specific entries"...not sure what you mean by "specific entries".  Are you referring to all those lines of text i see above...or...are you saying just copy the folder (as example - MSTTS_V110_enAU_CatherineM folder) from the "Speedh_OneCore" to the "Speech" area?

My guess is when you read my questions your going to say don't try it.

Thanks

Garry

1 hour ago, flytriman said:

I've never touched the Registry Editor so I probably should not be even considering this...unless:

• When you say "really adept"...I'm not
• You say just copy the "specific entries"...not sure what you mean by "specific entries".  Are you referring to all those lines of text i see above...or...are you saying just copy the folder (as example - MSTTS_V110_enAU_CatherineM folder) from the "Speedh_OneCore" to the "Speech" area?

My guess is when you read my questions your going to say don't try it.

You can prevent any permanent blunders by creating a restore point in Windows settings. If you look at that list  of keys (MSTTS_V110_enGB_GeorgeM, for example) under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices], all you have to do is copy that key to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices]. The reason that I suggested the export-import approach is that with every major build update (for example 1909), Windows will delete the registry entries that it thinks are unneeded. If you export to a reg file, you can add it back to the registry with every build update. Also, this approach requires no direct editing of the registry with the Windows registry editor.

For example, select the key MSTTS_V110_enGB_GeorgeM, right click and export to a filename of your choice, like George.reg. Edit the reg file in Notepad so that it refers to Speech and not Speech_OneCore, save the file and then double click on it. The voice will magically appear in the registry and VOXATC will find it. BTW, this also works for Pilot2ATC. If one searches the AVSim forums one can find posts that describe how to do all this in greater detail. Some of the older posts also suggested adding the 32 bit registry entries, but that would only matter for P3d v1-3 or FSX. Another interesting aside is that one can use foreign language voices and have them speak English. Since the phonemes in each language (building block sounds) are different, an Italian voice will speak English with an Italian accent!

Okay...thanks...think I understand.  Will give it a try in the next couple of days (working on another project currently) and post results.

Thanks again for all you help.

Garry

That worked perfectly...thank you very much.

Garry

Save those reg files for when Microsoft issues one of those not so creative updates to Win 10. You might or might not need the files. 

Done...thanks.

 

Garry