-
-
Notifications
You must be signed in to change notification settings - Fork 651
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
NVDA fails to announce capital letters when pitch is set to 0 #10940
Comments
Did this work on Python 2 versions of NVDA? I guess this applies to almost every synthesizer. |
Marking this p3, as it is unlikely that one would feel very comfortable with having synthesizer pitch at 0. Having said that, it should be pretty easy to fix. |
Maybe limit all to 1 grin.
Brian
|
I think this is related to #10896 and indeed might hav been appeared after migrating to Python 3. |
I can replicate this with Windows OneCore as well as eSpeak-NG, so I don't think it is an eSpeak-NG issue. I just tried in NVDA 2019.2.1 (pre Python 3) and cannot replicate this issue then, so it may be something which came in with Python 3. Investigated as someone reported via Twitter, however I agree this is not likely to be a commonly encountered situation. Twitter thread: https://twitter.com/mhussaincov/status/1539558402434777088 |
A different but similar issue: |
Steps to reproduce:
Actual behavior:
When encountering capital letter the error sound is played and the following is in the log:
Expected behavior:
The capital letter should be read.
System configuration
NVDA installed/portable/running from source:
Portable
NVDA version:
Latest Alpha
Windows version:
Windows 7 x64
Name and version of other software in use when reproducing the issue:
Notepad
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
It works as expected in 2019.2.1 and fails in 2019.3
If addons are disabled, is your problem still occuring?
Yes
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Not relevant
cc @feerrenrut @michaelDCurran
The text was updated successfully, but these errors were encountered: