Amir has movedJan 25, 2025
So, after JAWS, NVDA is also kissing goodbye to SAPI 4 TTS engines, in 2026.
The support for Microsoft Speech API version 4 synthesizers is planned for removal in NVDA 2026.1. Any remaining users of SAPI4 speech synthesizers are encouraged to choose a more modern speech synthesizer.
https://github.com/nvaccess/nvda/pull/17599
@NVAccess
Fix SAPI 4 driver by SaschaCowley · Pull Request #17599 · nvaccess/nvda

Link to issue number: Fixes #17516 Summary of the issue: After the move to exclusively Windows core audio APIs, the SAPI4 driver stopped working. Description of user facing changes The SAPI4 driver...

GitHub
Show threadgexgd0419Feb 25, 2025
@amir Good news for SAPI 4 users! Now SAPI 4 support is no longer planned for removal in NVDA 2026.1, and all warning messages has been removed. Also, now SAPI 4 voices use WASAPI as well, meaning that features such as audio ducking and leading silence trimming can now work with SAPI 4 voices. Check the newest alpha version alpha-35416, and please report issues you find on GitHub!
Show threadaryan
@gexgd0419 @amir thanks for your awesome work with the TTS stuff in Nvda 2025.1
Feb 25, 2025 at 2:39pmWeb
Show threadx0Feb 25, 2025
@Aryan @gexgd0419 @amir How does it work with WASAPI? What PR was this done in?
Show threadaryanFeb 25, 2025
@x0 @gexgd0419 @amir https://github.com/nvaccess/nvda/pull/17718
Make SAPI4 voices use WASAPI by gexgd0419 · Pull Request #17718 · nvaccess/nvda

Link to issue number: None Summary of the issue: This PR makes the built-in SAPI4 synthesizer use WASAPI to output audio, so that old code related to WinMM can be removed entirely. Description of u...

GitHub