Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Starting with version 2019.3, the "Capital pitch change" when using the SAPI4 synthesizer was invalid #12311

Closed
cary-rowen opened this issue Apr 20, 2021 · 10 comments
Closed

Starting with version 2019.3, the "Capital pitch change" when using the SAPI4 synthesizer was invalid #12311

cary-rowen opened this issue Apr 20, 2021 · 10 comments

Comments

@cary-rowen
Copy link
Contributor

cary-rowen commented Apr 20, 2021 •
edited
Loading

Below is the debug log I added, You may find helpful information from line 630.
nvda_log.txt

Steps to reproduce:

  1. Download and install the speech synthesizer provided in the following link, or use the SAPI4 speech synthesizer already on your computer.
    link: https://www.dropbox.com/s/3njaa8jrplutk24/IBM_ViaVoice_TTS_Runtime-V6.405.exe?dl=0
  2. Start NVDA and press NVDA + CTRL + S to select "Microsoft Speech API version 4" and confirm.
  3. At this point the NVDA should have switched to the SAPI4 synthesizer and you will need to press NVDA + CTRL + V to open the Voice Setup dialog.
  4. Use the Tab key to navigate until you hear "Capital pitch change percentageeditselected 30" You can change this value to 40 (or higher, or leave it unchanged).
  5. Then use Windows + R to open the Run dialog and type notepad and confirm, this will open notepad allowing you to type some text.
  6. Press the Caps lock key (it may be located to the left of the letter A) You may need to press it twice in a row until you hear "Caps lock on".
  7. Try to enter some letters, such as the letter "C" (or "D" or something else)
  8. Use Left Arrow or Right Arrow to move between these letters.

Actual behavior:

NVDA reports these capital letters with no change in pitch.

Expected behavior:

You will hear NVDA report these capital letters in a higher pitch

System configuration

NVDA installed/portable/running from source:

installed and portable.

NVDA version:

NVDA 2020.4

Windows version:

Windows 10 20H2 (64Bit) build 19042.928

Name and version of other software in use when reproducing the issue:

None

Other information about your system:

None

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.

I tested NVDA2020.4, NVDA2020.3, NVDA2019.3 And NVDA2019.2.1 in turn and found that this is a regression introduced by NVDA 2019.3(Of course including 2019.3.1).

If add-ons are disabled, is your problem still occurring?

Yes.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

Yes.
@vgjh2005
Copy link

Hi:
I agree with you. It is a Critical issue! SAPI version 4 is still the most important synthesizer today. Though there are more and more modern complex synthesizer switching system plugins, but using different sounds to announce different languages do to text reading is not enough of satisfied. Fortunately, IBM viavoice text to speech engine has been able to run to announce multi language at the same time by one voice. It is still my only synthesizer. So please fix it. Thanks!

@zstanecic
Copy link
Contributor

zstanecic commented Apr 21, 2021 via email

@cary-rowen
Copy link
Contributor Author

Thanks, I have tried this method and it does not work as expected, so it is invalid.
@zstanecic

@cary-rowen
Copy link
Contributor Author

Can you investigate this? Thank you.
@CyrilleB79

@zstanecic
Copy link
Contributor

zstanecic commented Apr 21, 2021 via email

@cary-rowen
Copy link
Contributor Author

Yes, so I believe this is a bug of NVDA. In the synthesizer download link I provided, this method is invalid.

@zstanecic
Copy link
Contributor

zstanecic commented Apr 21, 2021 via email

@cary-rowen
Copy link
Contributor Author

@zstanecic I have added the debug log at the very beginning of the first comment.
Thank you for your reminder and hope you can assist in the investigation.

@zstanecic
Copy link
Contributor

zstanecic commented Apr 21, 2021 via email

@dpy013
Copy link
Contributor

dpy013 commented Apr 21, 2021

cc @seanbudd

@cary-rowen cary-rowen mentioned this issue Apr 29, 2021
Merged
7 tasks
@cary-rowen cary-rowen mentioned this issue May 1, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vgjh2005 @zstanecic @cary-rowen @dpy013