Unable to load synthesizer with invalid voice error

[NCW-Srandall]

Hi,
I'm trying to help someone get set up with a new Win11 machine and getting an error. Snip from NVDA's log below.
DEBUGWARNING - synthDriverHandler.getSynthList (17:19:42.922) - MainThread (18128):
Synthesizer 'mssp' doesn't pass the check, excluding from list
DEBUGWARNING - synthDriverHandler.getSynthList (17:19:42.927) - MainThread (18128):
Synthesizer 'sapi4' doesn't pass the check, excluding from list
WARNING - synthDriverHandler.SynthDriver.loadSettings (17:19:44.540) - MainThread (18128):
Invalid voice: 4294967295
ERROR - synthDriverHandler.setSynth (17:19:44.540) - MainThread (18128):
setSynth failed for ibmeci
Traceback (most recent call last):
File "synthDriverHandler.pyc", line 332, in loadSettings
File "synthDriverHandler.pyc", line 388, in changeVoice
File "speechDictHandler_init_.pyc", line 138, in loadVoiceDict
KeyError: '4294967295'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "synthDriverHandler.pyc", line 462, in setSynth
File "synthDriverHandler.pyc", line 432, in getSynthInstance
File "synthDriverHandler.pyc", line 323, in initSettings
File "synthDriverHandler.pyc", line 338, in loadSettings
File "synthDriverHandler.pyc", line 388, in changeVoice
File "speechDictHandler_init_.pyc", line 138, in loadVoiceDict
KeyError: '4294967295'
INFO - synthDriverHandler.setSynth (17:19:44.541) - MainThread (18128):
Falling back to previous synthDriver espeak
INFO - synthDrivers.espeak.SynthDriver.init (17:19:44.549) - MainThread (18128):
Using eSpeak NG version 1.51-dev
INFO - synthDriverHandler.setSynth (17:19:44.593) - MainThread (18128):
Loaded synthDriver espeak

[Mohamed00]

Try either deleting the [[ibmeci]] section in nvda.ini, or resetting to factory settings.

…

On 1/19/2022 1:42 PM, NCW-Srandall wrote: Hi, I'm trying to help someone get set up with a new Win11 machine and getting an error. Snip from NVDA's log below. DEBUGWARNING - synthDriverHandler.getSynthList (17:19:42.922) - MainThread (18128): Synthesizer 'mssp' doesn't pass the check, excluding from list DEBUGWARNING - synthDriverHandler.getSynthList (17:19:42.927) - MainThread (18128): Synthesizer 'sapi4' doesn't pass the check, excluding from list WARNING - synthDriverHandler.SynthDriver.loadSettings (17:19:44.540) - MainThread (18128): Invalid voice: 4294967295 ERROR - synthDriverHandler.setSynth (17:19:44.540) - MainThread (18128): setSynth failed for ibmeci Traceback (most recent call last): File "synthDriverHandler.pyc", line 332, in loadSettings File "synthDriverHandler.pyc", line 388, in changeVoice File "speechDictHandler_/init/_.pyc", line 138, in loadVoiceDict KeyError: '4294967295' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "synthDriverHandler.pyc", line 462, in setSynth File "synthDriverHandler.pyc", line 432, in getSynthInstance File "synthDriverHandler.pyc", line 323, in initSettings File "synthDriverHandler.pyc", line 338, in loadSettings File "synthDriverHandler.pyc", line 388, in changeVoice File "speechDictHandler_/init/_.pyc", line 138, in loadVoiceDict KeyError: '4294967295' INFO - synthDriverHandler.setSynth (17:19:44.541) - MainThread (18128): Falling back to previous synthDriver espeak INFO - synthDrivers.espeak.SynthDriver.*init* (17:19:44.549) - MainThread (18128): Using eSpeak NG version 1.51-dev INFO - synthDriverHandler.setSynth (17:19:44.593) - MainThread (18128): Loaded synthDriver espeak — Reply to this email directly, view it on GitHub <#61>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADY4AYDTDS5N7RUX43OXHV3UW4A2TANCNFSM5MKWRMAA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[NCW-Srandall]

I cleared the .ini section but hadn't tried a full reset yet. :) will do that next Thanks Sean On 19 Jan 2022, at 23:52, Mohamed Al-Hajamy ***@***.***> wrote:  Try either deleting the [[ibmeci]] section in nvda.ini, or resetting to factory settings.

On 1/19/2022 1:42 PM, NCW-Srandall wrote: Hi, I'm trying to help someone get set up with a new Win11 machine and getting an error. Snip from NVDA's log below. DEBUGWARNING - synthDriverHandler.getSynthList (17:19:42.922) - MainThread (18128): Synthesizer 'mssp' doesn't pass the check, excluding from list DEBUGWARNING - synthDriverHandler.getSynthList (17:19:42.927) - MainThread (18128): Synthesizer 'sapi4' doesn't pass the check, excluding from list WARNING - synthDriverHandler.SynthDriver.loadSettings (17:19:44.540) - MainThread (18128): Invalid voice: 4294967295 ERROR - synthDriverHandler.setSynth (17:19:44.540) - MainThread (18128): setSynth failed for ibmeci Traceback (most recent call last): File "synthDriverHandler.pyc", line 332, in loadSettings File "synthDriverHandler.pyc", line 388, in changeVoice File "speechDictHandler_/init/_.pyc", line 138, in loadVoiceDict KeyError: '4294967295' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "synthDriverHandler.pyc", line 462, in setSynth File "synthDriverHandler.pyc", line 432, in getSynthInstance File "synthDriverHandler.pyc", line 323, in initSettings File "synthDriverHandler.pyc", line 338, in loadSettings File "synthDriverHandler.pyc", line 388, in changeVoice File "speechDictHandler_/init/_.pyc", line 138, in loadVoiceDict KeyError: '4294967295' INFO - synthDriverHandler.setSynth (17:19:44.541) - MainThread (18128): Falling back to previous synthDriver espeak INFO - synthDrivers.espeak.SynthDriver.*init* (17:19:44.549) - MainThread (18128): Using eSpeak NG version 1.51-dev INFO - synthDriverHandler.setSynth (17:19:44.593) - MainThread (18128): Loaded synthDriver espeak — Reply to this email directly, view it on GitHub <#61>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADY4AYDTDS5N7RUX43OXHV3UW4A2TANCNFSM5MKWRMAA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

— Reply to this email directly, view it on GitHub<#61 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWYQWVWEJUA523GSHBWHIOLUW5FEVANCNFSM5MKWRMAA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***> [Recycle trees] Save a tree...please don't print this e-mail unless you really need to. Confidentiality Notice This message and any attachments are private and confidential and may be subject to legal privilege and copyright. If you are not the intended recipient please do not publish or copy it to anyone else. If you have received this message in error please notify the sender immediately by using the reply facility in your email software and then remove it from your system. Data Protection We comply with data protection legislation, including the General Data Protection Regulation (GDPR), and take the security and privacy of personal data very seriously. If you no longer wish to receive emails from us please forward this email (so we can see who it was sent to you by) to ***@***.******@***.***> with your request, and we will review our information in line with your wishes. Disclaimer Although this email and attachments have been scanned for viruses, New College Worcester accepts no liability for any loss or damage arising from the receipt or use of this communication.