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
change default NVDA voice and variant #5272
Comments
Comment 1 by briang1 on 2015-08-07 06:30 I do not think this is a good idea. I think, although many may find the current choice not ideal, it can be understood in many languages and dialects. If I were to change anything I'd suggest making the fact that other choices exist is put forward to new users as part of the first run system. |
@jcsteh @michaelDCurran Could you please briefly address this request and subsequently close this ticket? |
@michaelDCurran, do you think making Edward the default for Espeak instead of Max is a good idea? |
Many english speaking users would be very happy with this change if it
did happen. However, I fear for non-english speakers, Edward may not be
as good as Max as there may still be some issues with the way eSpeak
maps particular phonemes to Klatt.
|
This affects only Windows 8.1 users, since in Windows 10 and higher the default voice is one core. |
If this only affects windows 8.1 users, then I think given that (A) Windows 8.1 reached end of life in Jan 2023, (B) less than 2% of our users are running windows 8.1, and (C) there's been very little activity on this issue in the 9 years since it was raised, we can close this issue as stale. |
Reported by joshknnd1982 on 2015-08-06 17:34
Due to the fact that so many people like eloquence, and also the fact that they cannot use sapi5 eloquence right away when NVDA is first started... or some people cannot afford eloquence... Therefore I would like to request the default voice in NVDA please change it to the latest speechPlayer in ESpeak with Edward as the default variant set to US english. I would also ask that the volume of Edward be slightly increased.
The text was updated successfully, but these errors were encountered: