[Nvda-dev] Problems when walking through espeak voices

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Nvda-dev] Problems when walking through espeak voices

Lubos Pintes-2
Hello,
When I choose espeak as the synthesizer, (I have SAPI4 Serotek by
default) and want to also choose the slovak voice, NVDA behaves
unpredictably. I had difficulties with understanding what espeak speaks
so I walked through voice list with arrows and with first letter,
randomly. At first nvda was silent and very big log file with something as
Warning queue full while adding function xyz (sorry the log was
rewritten I forgot to backup it).
The second time the following was generated. NVDA was silent, but I was
able to terminate it normally with NVDA+Q.

WARNING - core.main:
Slow starting core
ERROR - _espeak.BgThread.run:
bgThread.run
Traceback (most recent call last):
   File ".\synthDrivers\_espeak.py", line 149, in run
     func(*args, **kwargs)
   File ".\synthDrivers\_espeak.py", line 162, in _speakBg
     return
espeakDLL.espeak_Synth(unicode(msg),0,0,0,0,espeakCHARS_WCHAR,byref(uniqueID),index)
WindowsError: exception: access violation reading 0x00000061


Reply | Threaded
Open this post in threaded view
|

Re: [Nvda-dev] Problems when walking through espeak voices

James Teh-2
This is either a bug in eSpeak or a problem with the way we are changing
voices. I don't think we are doing anything incorrect in terms of the
API, but I could be wrong. It would be good to get a reliable test case
to reproduce this problem so we can try it outside of NVDA.

There are also certain unicode characters which currently crash eSpeak.
I need to track these down so I can report them.

Jamie

Lubos Pintes wrote:

> Hello,
> When I choose espeak as the synthesizer, (I have SAPI4 Serotek by
> default) and want to also choose the slovak voice, NVDA behaves
> unpredictably. I had difficulties with understanding what espeak speaks
> so I walked through voice list with arrows and with first letter,
> randomly. At first nvda was silent and very big log file with something as
> Warning queue full while adding function xyz (sorry the log was
> rewritten I forgot to backup it).
> The second time the following was generated. NVDA was silent, but I was
> able to terminate it normally with NVDA+Q.
>
> WARNING - core.main:
> Slow starting core
> ERROR - _espeak.BgThread.run:
> bgThread.run
> Traceback (most recent call last):
>     File ".\synthDrivers\_espeak.py", line 149, in run
>       func(*args, **kwargs)
>     File ".\synthDrivers\_espeak.py", line 162, in _speakBg
>       return
> espeakDLL.espeak_Synth(unicode(msg),0,0,0,0,espeakCHARS_WCHAR,byref(uniqueID),index)
> WindowsError: exception: access violation reading 0x00000061
>
> _______________________________________________
> Nvda-dev mailing list
> [hidden email]
> http://lists.nvaccess.org/listinfo/nvda-dev

--
James Teh
Email: [hidden email]
WWW: http://www.jantrid.net/
MSN Messenger: [hidden email]
Jabber: [hidden email]
Yahoo: jcs_teh