Warning: loud noises. So I tried out the bestspeech addon for NVDA released by @Tamasg for fun. Unfortunately, if I arrow up and down quickly on a webpage, this is what it frequently does. Sorry for the echo and horrible clipping, I had to shout over the noises, and the setup to record this wasn't ideal. But I haven't heard a computer make these noises in ages!
@fastfinge loool that totally sounds like the pointer fried your memory horribly. And NVDA didn't reboot itself, just reset the speech synth after all that even? I've never heard eloquence samples in the corruption, wow. You can try the -older version of the add-on but since more people saw issues when we weren't using the thread executor to try and avoid race conditions I don't think you'll find it much better. We'll see how badly the 2025.1 version changes things, ironically yeah for BestSpeech the add-on changes might be more minimal, and at least the newer eloq drivers are able to play through Wasapi on Nvwave output devices, so I'm hoping they'll stay good.
@Tamasg So oddly, that only happens on my Intel Microsoft Surface laptop. It's fine on my AMD Framework Laptop. But just pressing the up and down arrows quickly on a webpage on my surface can get that to happen every time, howling squeaking random eloquence samples and all. A sighted person tells me that the "okay" button eloquence tries to read is for a dialogue that says "The instruction at {random numbers} referenced memory at {random numbers}. The memory could not be written. Click on OK to terminate the program." But if I don't press okay NVDA just fixes itself and comes back.
@fastfinge oooh that's interesting. with this newer thread executor model, I've actually gotten myself to switch back to Eloquence while the loud sounds were happening, and it would continue to play them on that other thread whilst Eloq just happily spoke along. One of the most baffling experiences in this for sure, so at least I'm thinking the newer driver does more to prevent NVDA's main thread from frying and keep it more in the DLL lock.
@Tamasg Also sounds like it's bugs in the DLL, or bugs in the way Windows 11 is running the ancient code from 1995, and not something you can fix. Maybe grab an old copy of NVDA and see what it does on Windows XP?
