Conversation
|
Maybe only disable this for silence rather than only enabling for OneCore? |
It's an easy fix for silence, I am concerned about breaking existing custom synthDrivers that could be installed as addons. |
See test results for failed build of commit 4042bf9ab2 |
|
I'm applying this check to oneCore only as it broke the system test synthdriver and I imagine it will break many others. |
|
Hi @MarcoZehe, @VovaMobile and any others running a Windows copy which has no OneCore voices installed.
PS:
|
|
Hi! Windows OneCoreVoices absent for some languages, such as
Ukrainian. Your tutorial is not correct.
2021-07-15 3:33 GMT+03:00, Sean Budd ***@***.***>:
… Hi @MarcoZehe, @VovaMobile and any others running a Windows copy which has
no OneCore voices installed. You can confirm your device has no OneCore
voices by doing the following:
1. Go to Windows "Speech" settings
1. Check "Installed Voice packages"
Can you please verify that:
- the latest alpha build of NVDA still replicates this issue, such that
there is no speaking by default unless the synthesizer is changed manually
to espeak
- [this PR
build](https://ci.appveyor.com/api/buildjobs/g3v7ot4gs6s27owc/artifacts/output%2Fnvda_snapshot_pr12646-23351%2Cf7e69a1e.exe)
fixes the above issue
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#12646 (comment)
|
|
My case was a bit different I believe. I had German voices installed, but Windows hadn't included English ones. NVDA acted up when it's automatic language switching wanted to switch to English on a website. I am currently not in a position to test this PR, sorry. |
|
My mistake, in this case it would probably be better to handle this on failure or on handling LangChangeCommand Closing in favour of a more generic approach in #12647, and a targeted approach when changing languages |
Link to issue number:
Fixes #10451
Summary of the issue:
If a device has no OneCore voices installed, speech fails by default when starting a new NVDA copy.
Description of how this pull request fixes the issue:
Consider OneCore as unusable if there are no available voices
Testing strategy:
Known issues with pull request:
#11544 is still a current issue
Change log entries:
Bug fixes
Code Review Checklist: