Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Don't allow Silent synth to be saved between restarts if auto selected due to failure #2589

Closed
nvaccessAuto opened this Issue Aug 8, 2012 · 5 comments

Comments

Projects
None yet
1 participant

Reported by elliott94 on 2012-08-08 18:14
It may be a good idea to change the Silent synth driver to ensure that it can't be used as NVDA's default synthesizer. This can automatically be activated if the default audio output device that NVDA uses has failed. With the current behaviour, a user may find themselves in a situation where by this particular synth gets activated, and they either don't know how to change to their chosen speech engine, or are unable to figure out why speech has stopped.

Comment 1 by jteh on 2012-08-08 21:47
Some people may actually want the silence synth as their default; e.g. deaf users or sighted users using the Speech Viewer. Adjusting the summary to just cover the fallback case.
Changes:
Changed title from "Don't allow Silent synth to be saved between restarts" to "Don't allow Silent synth to be saved between restarts if auto selected due to failure"

Comment 2 by elliott94 (in reply to comment 1) on 2012-08-09 09:22
Replying to jteh:

Some people may actually want the silence synth as their default; e.g. deaf users or sighted users using the Speech Viewer. Adjusting the summary to just cover the fallback case.

Sorry; I originally considered adding this into the description, but wasn't sure if it'd be possible to detect if the synth had been activated due to an audio device failure. If this can be done though, this would of course be the best solution.

Comment 3 by nikosdemetriou on 2012-11-06 21:51
Hi.
Perhaps we could have a checkbox under synth settings to prevent nvda from saving the silent synth as the default if we don't need this feature.

Comment 4 by elliott94 on 2012-11-11 20:13
Was this fixed in d0e9429?

Comment 5 by jteh (in reply to comment 4) on 2012-11-21 02:08
Replying to elliott94:

Was this fixed in d0e9429?

Yes.
Changes:
Milestone changed from None to 2013.1
State: closed

@nvaccessAuto nvaccessAuto added this to the 2013.1 milestone Nov 10, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment