-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
SAPI-4 synthesizers/voices pitch no longer increase during letter navigation #10896
Comments
Hi daniel,
For now, a workaround is to turn of the option
# use spelling functionaliti when supported checkbox #
|
There are no differences if "Trust voice's language when processing characters and symbols" and "Use spelling functionality if supported" are disabled or enabled in NVDA 2019.3.1 and 2020.1 Beta 1. I've tested all four possible variants right now. Just let me know, if you need a debug logfile. |
Yes this affects that LH sappi 4 as well. I don't think any of the sappi 4
systems is as stable now. Its is an old system, i'm surprised Microsoft
still support it.
|
This was referenced Aug 2, 2020
#12354 It seems to solve this issue. Can you test it with the latest alpha version? |
Closing as fixed by #12354 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce:
Actual behavior:
The voice pitch does no longer increase during letter navigation.
Expected behavior:
The voice pitch should increase during letter navigation.
Notes:
System configuration
NVDA installed/portable/running from source:
Portable
NVDA version:
2020.1 Beta 1
Windows version:
Win7x64
Name and version of other software in use when reproducing the issue:
Other questions
Does the issue still occur after restarting your computer?
Not tested.
Have you tried any other versions of NVDA? If so, please report their behaviors.
2019.2.1 (installed) and 2019.3.1 (portable); See notes above.
If addons are disabled, is your problem still occuring?
No add-ons are installed/used in NVDA 2019.3.1 and 2020.1 Beta 1 and I don't think that the installed/used add-ons in NVDA 2019.2.1 have any affects here.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No.
The text was updated successfully, but these errors were encountered: