Comment 1 by jteh on 2012-06-18 22:27
It's worth noting that NVDA can only use 32 bit SAPI engines, so this might explain the difference between NVDA and other applications. Why the 32 bit engines are slower for you is still an open question. :)

If you haven't already, would you mind testing with the SAPI 5 version of eSpeak (which is 32 bit)?

Comment 2 by erion (in reply to comment 1) on 2012-06-19 06:59
Replying to jteh:

If you haven't already, would you mind testing with the SAPI 5 version of eSpeak (which is 32 bit)?

It is just as slow as the other 32 bit voices, e.g. the 32 bit version of MS David.
However this is not voice specific, since native 32 bit programs have no such issue (maybe the wave buffer is too large?).

CC @jcsteh

@erion can you still reproduce this?
@jcsteh, @michaelDCurran I guess there is low priority for this issue at NV Access. Right? Actually there was also some problems regarding this issue which have been reported in the german community as well. Especially with 24 khz voices. But I think those voices can be replaced by better and more responsive ones. Your thoughts are very appreciated.

We do not have any user reports on this one for a very long while. I am closing this. if you still have this problem, please comment on it and we can reopen the discussion. For me it works just fine with NVDA 2019.1.1 on Windows 8.1 and Sapi5 voices.