Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Not necessarily. Particularly with the missiles radar, the direction you are in relation to a fighter/aircraft carrier or the like, and all that important stuff. There's too much noise going on for the screen reader to be legible under

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay I wonder though, do you really need to pause the game to provide a status update? Haven't played TDV in a long time so sorry if this is obvious, but can't you just announce it and let the game go on? It's only a few seconds of

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Ok. That definitely won't work for something like TDV. The user experience will be greatly disrupted if the player was asked to press ENTER after every status message. URL: https://forum.audiogames.net/post/460733/#p460733 -- Audio

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay The Manamon solution is one of the things I mentioned above, press enter once your screen reader is done speaking to continue. URL: https://forum.audiogames.net/post/460701/#p460701 -- Audiogames-reflector mailing list Audiogames

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay I think that, instead of using some dirty tricks to see whether the screen reader finished speaking, better use some more reliable way to output speech, such as sapi(windows) or speech dispatcher(linux), which can determine quite easily if the

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @Rastislav Kiss: Thanks for this information; it's very helpful! You're correct that we'd have to run some reliable tests to really see how fool-proof this method is.bgt lover wrote:However, if you feel like you need screen reade

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay bgt lover wrote:However, if you feel like you need screen readers in your game, the manamon solution is the best there is.What exactly is the Manamon solution? Some elaboration would be helpful here.As for confining the player to SAPI, I prefer

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay I think that, instead of using some dirty tricks to see whether the screen reader finished speaking, better use some more reliable way to output speech, such as sapi(windows) or speech dispatcher(linux), which can determine quite easily if the

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Hi,Munawar is right. The algorithm is expected to run in its own method, as I have stated above it, I haven't wrote it explicitly as I didn't consider it important.It is thus synchronous and thread safe.Regarding 10 ms check, I h

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Hi,Munawar is right. The algorithm is expected to run in its own method, as I have stated above it, I haven't wrote it explicitly as I didn't consider it important.It is thus synchronous and thread safe.Regarding 10 ms check, I h

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @Ethin: he doesn't need a mutex on counter. I'm assuming that code is its own function in which case there is no sharing of state there. You don't need to make counter reside in global scope for this. So the code is thread-safe.A

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay There's still a race condition in there. Since you can't synchronize that looping thread and the screen reader reliably, this situation is very possible:1. Thread runs: screen reader is not speaking. Waits 10 MS.2. Thread runs 10 MS l

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @20: regarding the peak tracking algorithm, I would myself take different approach. Not because of half second long words, I don't think something like that could happen, although it is possible in theory.But rather because 500 ms is very

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @20: regarding the peak tracking algorithm, I would myself take different approach. Not because of half second long words, I don't think something like that could happen, although it is possible in theory.But rather because 500 ms is very

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @20: regarding the peak tracking algorithm, I would myself take different approach. Not because of half second long words, I don't think something like that could happen, although it is possible in theory.But rather because 500 ms is very

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Thanks everyone for your suggestions. It seems like some of you have gotten it to work reliably for determining if a screen reader is speaking, though I'm getting pretty accurate timings with the solution I've currently got, especia

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @18: I have adressed that problem in the pause between sentences section, it should work quite reliably.It's not very surprising as recognizing by the audio's peak is the same what we humans do to determine if screenreader has fi

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @18: I have adressed that problem in the pause between sentences section, it should work quite reliably.It's not surprising as recognizing by the audio's peak is the same what we humans do to determine if screenreader has finished i

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay No, 10, fir my first question I meant that if the peek volume is zero, you cannot reliably determine whether audio is done streaming. Just because a peek may be at zero at one time does not mean that audio isn't still being streamed. Silen

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Although done speaking doesn't inform you when the synth started speaking again. But i'm pretty sure that those events can be handled and requested from within NVDA and thus be added to its api as well.Best Regards.Hijacker

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay from the NVDA 2019.3 alpha changelog... SynthDriver classes must now notify the synthDriverHandler.synthDoneSpeaking action, once all audio from a SynthDriver.speak call has completed playing.so its in the works. URL: https

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Hi,@11 & 12: yup, however those are not actual volume sliders but expected volume sliders. You can use them to set how loud should each program be, but they don't show current volume.For showing current volume, there are green bars i

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Hi,@11 & 12: yup, however those are not actual volume sliders but expected volume sliders. You can use them to set how loud should each program be, but they don't show current volume.For showing current volume, there are green bars i

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay It just shows the volume output, no matter if its actually outputting something or not.Regarding Windows XP and stuff, you shouldn't bother caring about that too much. XP is long gone now and we as developers shouldn't hang around wit

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Ok. I see now what this program does. How would you go from here (just getting volume) to determining if the screen reader is speaking? Do the volume levels change when something is streaming? After a quick glance it seems like it's o

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Same here, using sndvol for years now and it works perfectly fine.Best Regards.Hijacker URL: https://forum.audiogames.net/post/460431/#p460431 -- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @10I just opened Sndvol and can see each program I have open as well as the associated volume level by just tabbing through the window. NVDA says "dialog" before the program name, but that's it. Perfectly accessib

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @10I just opened Sndvol and can see each program I have open as well as the associated volume letter by just tabbing through the window. NVDA says "dialog" before the program name, but that's it. Perfectly accessib

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @8:1. Do you mean when for example user lowered volume of the system to zero, so this would be as well while screenreader could be potentially speaking?Well, what would be then the point to wait for screenreader to end its speech, when user

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @8:1. Do you mean when for example user lowered volume of the system to zero, so this would be as well while screenreader could be potentially speaking?Well, what would be then the point to wait for screenreader to end its speech, when user

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @8:1. Do you mean when for example user lowered volume of the system to zero, so this would be as well while screenreader could be potentially speaking?Well, what would be then the point to wait for screenreader to end its speech, when user

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @7: Thanks for this code, though as @8 mentioned, this would only work if no other sounds were playing.To achieve the words-per-minute count, I do exactly what Lone Wolf did:1. Have the screen reader speak something.2. The user presses ENTER

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay @7: Thanks for this code, though as @8 mentioned, this would only work if no other sounds were playing.To achieve the words-per-minute count, I do exactly what Lone Wolf did:1. Have the screen reader speak something.2. The user presses ENTER

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Two issues I see with this approach:1) It appears like that only gets volume output for each application and does not indicate whether audio is being streamed or not. Even if the peek is zero, audio can still be being streamed.2) How would you

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Hi there,I haven't tried it directly as I didn't really need this functionality yet, but wouldn't it be possible to just hook into screenreader's audio output and track if something is going on or not?Or more technica

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Hi there,I haven't tried it directly as I didn't really need this functionality yet, but wouldn't it be possible to just hook into screenreader's audio output and track if something is going on or not?Or more technica

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay If you mean addons, then they wont load since they will be Python 3 incompatible anyways. If you mean something like Sapi synths, then that will be handled by NVDA's sapi driver. URL: https://forum.audiogames.net/post/460254/#p4

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay It'll be interesting to see how synthesizers not sanctioned through official channels support this since we can't guarantee any kind of regular updates from this type of software. URL: https://forum.audiogames.net/post/46025

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay As soon as the support in the NVDA codebase is there, adding the corresponding function to the NVDA dlls should be a matter of 10 minutes and submitting a pull request, which will be very likely to be accepted.Best Regards.Hijacker URL: https

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Awesome, thanks for the input. No, the NVDA dlls don't provide this functionality (it doesn't look like they've been updated for about ten years.) So hopefully this functionality will be merged into the dlls so

Re: Empirically setting a screen reader delay

Re: Empirically setting a screen reader delay Actually, in alpha, NVDA already requires speech synthesizers to notify when they are done speaking. I don't know if the code is in the API as well, but if not, I'd guess it is definitely a planned feature together with the speech ref

Empirically setting a screen reader delay

Empirically setting a screen reader delay Some screen-reader APIs, like NVDA, provide no way to tell when the screen-reader has finished speaking. I finally sat down and thought about this with regards to TDV and screen-reader support: how can we provide a halt mechanism for these screen