@Jmd2000 Sapi5 technically has existed, although more underground and not connected to the main repo, so it can now move to be an official one, whilst iOS and Android would need building but could link against Espeak a lot more easily with this change so it becomes possible.

@Sevapopov if you can link to the add-on itself though I can take a look and see what can be done.

@Sevapopov ah yeah, just have zero idea what that means or requires. I don't know much about that add-on, have never used it.

@Sevapopov oh, the rename of the NVSpeechPlayer work.

Wow. This afternoon I got NVAccess' blessing to relicense TGSpeechBox. That means the SAPI5 project is moving into the repo tonight, as well as the future iOS and Android integration may be on the roadmap.
"Mick and the team here at NV Access have reviewed your request, and agree to the re-licensing.

NV Access retains the copyright to the original portions of the code, however we grant you permission to release those portions under your chosen permissive license (either MIT or Apache 2.0). Please simply ensure that the original NV Access copyright notices and attribution remain intact within the source files, as is standard practice with those licenses.

We also agree that renaming the project to "TGSpeechBox" is a sensible move. It effectively distinguishes your modern fork from the original legacy project and will help avoid confusion for users regarding support and features."

NVSpeech Player with phoneme editor and NVDA Addon version 1.8.5 Update from this link, or the updater in the add-on. I must run to work stuff. No more speechplayer until the evening.
This release adds proper tilt control to the NVDA driver.
No changes to phoneme editor, no time before work. Only changes to the speech player exports, and the driver, and packs to improve the R sound.
https://github.com/tgeczy/NVSpeechPlayer/releases/download/v-185/nvSpeechPlayer-2026-v185.nvda-addon

Well, I built a version of the NVSpeechPlayer NVDA driver for both 32-bit and 64-bit so it will indeed become compatible with 2026.1. I tried the alpha build here with it. It works. Not a lot of add-on level changes but we definitely have to make sure we load 64-bit DLLs and 32-bit ones from the right paths.

People asked for it, and I do think it's a great idea! All of my Speech synthesizers live at https://eurpod.com/synths - easy to remember URL, and if you want to check it for updates, easy to look at for a version difference. At most, we are only keeping the last 2 versions of a synthesizer, so they will not pile up here. Still uploading some of the larger files, but in the next hour this will all be updated.
The old URLs will work for now, a little bit. As time goes on I will remove them from their old locations and update the blog page to point to this folder too.

I'm sorry y'all. Our TTS engine will be frozen at 2007 pronounciation of Espeak. If we want true, true decoupled multilingual support. I wonder if it's worth maintaining two "flavors" of the driver, one which just uses existing Espeak phoneme data as built into NVDA's Espeak, and another that lets it live standalone to be useed for compiling and other projects. The fact is, this engine cannot become "free" until the phoneme data can live independently within it.

@tardis nah, I think it'll give a better chance for that unique talent to shine more. It's just going to change it where if you want to hear music that's less generic, perhaps lyrics that's more of a story and the song becomes an experience, it'll be worth it. I also think it'll really amplify live shows, and people actually watching an artist live, because that'll have more value in the age of AI music too. So it's just a reframing of what music is, how we listen to it and what we expect from artist talent.

@tardis well, the podcast points out that it's very possible for AI music to already be a regular pop song but none of us know it's actually either fully or in large-part AI made. That's fairly wild. Now the quality is so good that as long as you don't label it AI you can get away with it, so slowly people will be introduced to AI-made music personas alongside real artists, but the thing is, nobody will quite know if it's truly an AI persona because they'll put enough realism and image behind it that to the world it'll look just like a regular artist I think that time is soon here, the episode really convinced me we're closer than a few years ago to it.

I'm actually wanting to do an experiment where all music I listen to is Suno generated. Call me crazy. But I do think we're getting to the point where AI music is "good enough" to sound like real music. I know, I know. But the thing is, AI music also sounds incredibly generic when made without an artist voice. So. I don't think this means Artists are trash, far from it. If you can show that your voice and talent sounds more unique than the generic pop-laidened AI voices do, you're golden. Lyrics will still matter, but AI music gives you the freedom to make lyrics for any situation or mood you want with the motifs you want in it. That's huge. Human music then will need to shine more for its storytelling, for being authentic lyrics that make you think.
All of this stems for me from listening to Vox's Today, Explained about AI music. I recommend everyone give it a listen.
https://www.iheart.com/podcast/1319-today-explained-87205166/episode/ai-music-is-here-316616130/

@jstark Sometimes though change happens because people did work on the inside. When Microsoft decided to add MSAA (Microsoft Active accessibility) to Windows, it wasn't because there was a lawsuit, but we had people like Kelly Ford and others working inside to make change happen. Wouldn't call that one fear-based, although perhaps pressures by orgs did help that come along, since people were so concerned about transitioning from DOS to Windows. But I definitely know that that one wasn't lawsuit, but in 1997, primarily due to pressure from disability advocates and government agencies. @yatil