Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sapi4/5 synth drivers fail on voices which don't specify a language #1264

Closed
nvaccessAuto opened this issue Dec 6, 2010 · 4 comments
Closed

Comments

@nvaccessAuto
Copy link

Reported by briang1 on 2010-12-06 21:18
On one machine out of three all running the same version of XP etc, the snaps 970 will not allow sapi 4 to work, giving an error. If one reinstalls snap 946 the problem goes away, so it seems not to be corruption in the machine or anything like that.
I present the log fragmement below for a recent snap.

INFO - nvda (12:13:11):

Starting NVDA

INFO - core.main (12:13:11):

Config dir: C:\DOCUME1\brian\APPLIC1\nvda

DEBUG - core.main (12:13:11):

setting language to Windows

INFO - core.main (12:13:11):

NVDA version main-3971

INFO - core.main (12:13:11):

Using Windows version sys.getwindowsversion(major=5, minor=1, build=2600,
platform=2, service_pack='Service Pack 3')

INFO - core.main (12:13:11):

Using Python version 2.7 (r27:82525, Jul 4 2010, 09:01:59) v.1500 32
bit (Intel)

INFO - core.main (12:13:11):

Using comtypes version 0.6.2

DEBUG - core.main (12:13:11):

Creating wx application instance

DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (12:13:14):

No locale gesture map for language en

DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (12:13:14):

No user gesture map

.... So what is this all about by the way?...

DEBUG - core.main (12:13:14):

Speech Dictionary processing

DEBUG - speechDictHandler.SpeechDict.load (12:13:14):

Loading speech dictionary
'C:\DOCUME1\brian\APPLIC1\nvda\speechDicts\default.dic'...

DEBUG - speechDictHandler.SpeechDict.load (12:13:14):

file 'C:\DOCUME1\brian\APPLIC1\nvda\speechDicts\default.dic' not found.

DEBUG - speechDictHandler.SpeechDict.load (12:13:14):

Loading speech dictionary 'builtin.dic'...

DEBUG - speechDictHandler.SpeechDict.load (12:13:14):

4 loaded records.

DEBUG - core.main (12:13:14):

Initializing speech

WARNING - synthDriverHandler.SynthDriver.loadSettings (12:13:16):

No such voice: {8454410E-002C-0200-BC4F-5B1800D50059}

ERROR - synthDriverHandler.setSynth (12:13:16):

setSynth

Traceback (most recent call last):

File "synthDriverHandler.pyc", line 78, in setSynth

File "synthDriverHandler.pyc", line 416, in loadSettings

File "synthDriverHandler.pyc", line 31, in changeVoice

File "synthSettingsRing.pyc", line 73, in init

File "synthSettingsRing.pyc", line 124, in updateSupportedSettings

File "synthSettingsRing.pyc", line 40, in init

File "baseObject.pyc", line 21, in get

File "synthDriverHandler.pyc", line 295, in _get_availableVoices

File "synthDrivers\sapi4.pyc", line 213, in _getAvailableVoices

KeyError: 0

INFO - synthDrivers.espeak.SynthDriver.init (12:13:17):
This occured on running the installer which is why it was already set to sapi 4 on the machine. tthe voice was in fact an Orpheus one called Dave.

There was an associated error generated in Windows, though I'm not sure if this was a confused installer or the error, but here it is anyway.

Speaking u'nvda.exe - Application Error icon 1 of 5'

IO - speech.speakText (12:19:18):

Speaking u'nvda.exe - Application Error dialog The instruction at
"0x09577c42" referenced memory at "0x00000004". The memory could not be
"read".\r\n\nClick on OK to terminate the program'

IO - speech.speakText (12:19:18):

Speaking u'OK button'

All other machines have no problems, so I'm at a loss, but something has changed in the snapshots.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2010-12-08 06:11
This apparently happens for sapi5 as well. It seems that some voices don't specify the language. We should just set the language to None in these cases.
Changes:
Changed title from "Sapi 4 synth no longer working on some machines" to "sapi4/5 synth drivers fail on voices which don't specify a language"
Milestone changed from None to 2011.1

@nvaccessAuto
Copy link
Author

Comment 2 by briang1 on 2010-12-08 08:15
Not sure this is the whole story in this case as I have now installed the same Orpheus on three machines and two are fine and one is not, although using earlier snaps all do work correctly.

The Orpheus is quite old it has to be said, and it has a huge list of languages and voices, and I'd have thought it would change its language indication accordingly.

I need to do more tests, but have no time today.

@nvaccessAuto
Copy link
Author

Comment 3 by mdcurran on 2010-12-09 01:23
Hopefully fixed in 614763c.
Please report if the sapi4 issue goes away now. I'm not sure about the sapi5 one exactly as I never saw an example log message.

@nvaccessAuto
Copy link
Author

Comment 4 by mdcurran on 2010-12-14 04:55
Pople reporting sapi4 is definitely fixed. Still have not heard about sapi5. Am closing for now. If sapi5 is still broken, please reopen and provide further info.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant