alpha-35509: When using SAPI4 and rapidly adjusting the speech rate with NVDA + up/down arrow keys, NVDA emits an error tone.

[dpy013]

Steps to reproduce:

First download from here
Then create a portable version
and switch the speech synthesizer to sapi4
Finally, use ctrl+NVDA+left and right arrows to switch to the speed of speech, the
and hold down the up and down arrows.
to reproduce the error

Actual behavior:

Using ctrl+NVDA+up and down arrows to adjust the speed of speech under sapi4 gives an error.

Expected behavior:

Hold ctrl+NVDA+arrow to adjust the speed of speech without the beeping sound

NVDA logs, crash dumps and other attachments:

nvda.log

System configuration

NVDA installed/portable/running from source:

portable version

NVDA version:

alpha-35509,90a3c8d6

Windows version:

Microsoft Windows 24H2 (OS 26100.3194)

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.

Not yet.

If NVDA 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?

Haven't run the tool yet

[SaschaCowley]

@gexgd0419 this may be to do with your recent SAPI4 work

[gexgd0419]

Before my SAPI4 work, this error could also happen. But it happens more frequently after my change.

[gexgd0419]

Please try this snapshot build of pull request #17817 to check if this fixes the issue.

[dpy013]

Please try this snapshot build of pull request #17817 to check if this fixes the issue.
hi
Thank you for all your hard work.
Just now have done the test using nvda_snapshot_pr17817-35722.
The current issue has been fixed and the logs are provided below.

nvda.log

[valiant8086]

Awesome! so we can close this then, right?

[gexgd0419]

@valiant8086 The issue is linked to the pull request, so it will be automatically closed after #17817 is successfully merged. No need to close it prematurely.