jph2658 Report post Posted 02/23/2012 07:25 PM After the upgrade, TTS is now using Microsoft Sam. It used to use ATT DTNV 1.4 Crystal 16. No changes were made to the installed voices. We only updated the Dialog drivers and VoiceGuide software. Do you know why this occurred? Do you know can be done to get ATT DTNV 1.4 Crystal 16 back? I'd be happy to provide additional information if needed. Share this post Link to post
SupportTeam Report post Posted 02/23/2012 09:30 PM Please post vgEngine and ktTel and ktTts traces which capture VoiceGuide startup and the first call during which TTS is used. Share this post Link to post
jph2658 Report post Posted 03/09/2012 01:51 PM For anyone experiencing a similar issue, this was a missing registry setting under HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Speech/Voices Adding both DefaultTokenId (REG_SZ) and DefaultTTSRate (REG_DWORD) seemed to resolve the issue. No idea why... Share this post Link to post
SupportTeam Report post Posted 03/20/2012 06:27 AM In VoiceGuide v7 the SAPI TTS engine to use is specified in VoiceGuide's VG.INI file, in the [sAPI] section. Please see: http://www.voiceguide.com/vghelp/source/html/config_tts.htm Share this post Link to post