-
-
Notifications
You must be signed in to change notification settings - Fork 784
Cannot load sapi 5 synthesizer #17512
Copy link
Copy link
Closed
Labels
bug/regressioncomponent/speechp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releasetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Metadata
Metadata
Assignees
Labels
bug/regressioncomponent/speechp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityrelease/blockingthis issue blocks the milestone releasethis issue blocks the milestone releasetriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce:
Update to current alpha.
Actual behavior:
sapi5 synthesizer cannot be loaded anymore.
Expected behavior:
NVDA logs, crash dumps and other attachments:
ERROR - synthDriverHandler.setSynth (09:38:56.999) - MainThread (4020):
setSynth failed for sapi5
Traceback (most recent call last):
File "synthDriverHandler.pyc", line 483, in setSynth
File "synthDriverHandler.pyc", line 446, in getSynthInstance
File "synthDrivers\sapi5.pyc", line 140, in init
File "synthDrivers\sapi5.pyc", line 209, in _initTts
TypeError: '>=' not supported between instances of 'str' and 'int'
INFO - synthDriverHandler.setSynth (09:38:57.030) - MainThread (4020):
Falling back to previous synthDriver espeak
System configuration
NVDA installed/portable/running from source:
installed
NVDA version:
alpha-34782,82fefa5a (2025.1.0.34782)
Windows version:
w11 23h2
Name and version of other software in use when reproducing the issue:
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
If NVDA add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?