VoiceGuide IVR Software Main Page
Jump to content

No proper VoiceGuide Key to switch to the new Arabic ‘text to speach’ engine downloaded from Windows system setting

Recommended Posts

After downloading a new Arabic ‘text to speach’ engine using  the download procedure mentioned by Micorsoft :

Settings > Time & Language > Region & Language > Language options > Speech, select Download

We tried to toggle between the existing text to speech engine and the new downloaded one by changing the value pointed by the ‘TTS_SAPI_Engine’ as shown in the  VB code below :

vg.RvSet $RV_LINEID, "TTS_SAPI_Engine", "Microsoft David Desktop - English (United States)"


From the ‘VoiceGuide’ logs ‘0527_ktTts.txt’  it seems that ‘TTS_SAPI_Engine’ is addressing the Windows Registry Key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\’ giving access to only the following TTS values:




However, looking further in the Windows register database (via regedit) the new installed TTS engine there seems to be another Windows Registry key ‘Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices’  addressing the actual TTS packages including the new ‘Arabic’ that we are targeting (and not considered by VoicGuide TTS APis’






Is there a way or another TTS API (expect TTS_SAPI_engine ) that would allow us to point to ‘Speech_OneCore’ registery’ values instead of ‘Speech’ ones.



Best Regards,

Share this post

Link to post

Can you please post the VoiceGuide trace logs which contain the system startup and the "TTS_SAPI_Engine" Result Variable set.

The log files which need to be posted are the matching vgEngine, ktTel and ktTts traces.

We can then confirm the TTS engines' operation on your system.

Please .ZIP up the traces before posting them.


Share this post

Link to post

vgEngine trace was not included in the uploaded Logs.7z

Please upload the matching vgEngine trace as well.

Share this post

Link to post

I just attached the a new zip file file including the missing 'vgEngine' trace you mentioned along with the previous files.

Please let me know if your require other elements.

Thanks for your support


Share this post

Link to post

Looks like you are trying to use TTS voices that were not installed into the Window's  SAPI system.

In this case however, there is apparently a way to make these particular Windows 10 TTS engines accessible through SAPI. Please see:





Share this post

Link to post

We apply the procedure of the link and it is working.


Thank you very much for your support.

Share this post

Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now