@joshknnd1982 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 did you use 32 bit version of python?

@rommix0 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 yes python 3.7.0 ...

@joshknnd1982 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 okay. I'll look over what you got in a moment, and I'll update you on what I see.

@rommix0 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 I asked chatgpt to make controls accessible, ... tested, still no go... https://drive.google.com/file/d/1SDqEXb44df1XhSjJAmK1lcD7OZefuH_4/view?usp=sharing

@joshknnd1982 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 I tested on my rig, and it's working on mine.

@rommix0 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 Did you use the speak window with a screen reader loaded, navigating with the keyboard-only?

@joshknnd1982 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 I don't have a screen reader. I just opened the speak window alone.

@rommix0 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 I wonder if the accessibility is a limitation of the python 3.7.0 GUI? if this is the case, could you convert my speak window to c++, the language that your original speak window was written in?

@joshknnd1982 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 yeah probably

@rommix0 @MutedTrampet @TheQuinbox @BTyson @samtupy @Tamasg @AlexSpectrum93 @datajake1999 gain is volume so it seems. So I set the gain to 16 and it is much louder. gain of 20 is too high, makes voice clip and pop.

@joshknnd1982 @rommix0 @MutedTrampet @TheQuinbox @BTyson @samtupy @AlexSpectrum93 @datajake1999 sounds like good experimenting here. I wouldn't have the time to refactor the existing B32 wrapper to work with the newer DLLs, this would need to be done after you get a solid speak window. Everything is open-source, anyone's welcome to pick up Sam's work from his repo and open a pull request against it if you feel the pace isn't quick enough. These newer DLLS don't just neatly swap into the wrapper because calling conventions are probably different, so putting an AI to compare what you just built in your speak window and Sam's B32_wrapper, then modernizing on existing NVDA 2025.3 is a good start. Maybe AI can rewrite the function signatures n the wrapper for you.
But nobody should feel obligated to an open source project if they don't have time or energy to refactor it, this is where the rest of the community can come together if there's interest on improving it.

@Tamasg @joshknnd1982 @MutedTrampet @TheQuinbox @BTyson @samtupy @AlexSpectrum93 @datajake1999 I second this.