Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA should work without audio output #425

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 4 comments
Closed

NVDA should work without audio output #425

nvaccessAuto opened this issue Jan 1, 2010 · 4 comments
Assignees

Comments

@nvaccessAuto
Copy link

Reported by jteh on 2009-09-23 06:50
From Felix Grützmacher and Lars Bjørndal:
If NVDA finds a Braille display but no sound card, it would be great if it didn’t exit. This way, users could install their sound drivers while using NVDA with a Braille display.

At this stage, NVDA isn't going to work "out of the box" like this because it does not currently auto-detect braille displays. However, it should be possible to do this with a preconfigured NVDA; e.g. loaded on a USB stick or on flash storage in the display itself.

I suspect that tones is probably the problem here. We should already fall back to silence if eSpeak fails, so this should be fine.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2009-11-24 01:05
Bzr branch: http://bzr.nvaccess.org/nvda/noAudio/

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2009-11-24 01:07
Also useful to sighted testers who use the display synth on systems with no audio hardware.
Changes:
Changed title from "NVDA should work without audio output if a braille display is available" to "NVDA should work without audio output"

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2009-11-27 04:15
This does work on a system where audio fails. Waiting on some info as to whether this breaks the Synthesizer dialog on systems with no audio drivers at all.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2009-11-27 05:19
ON a system with no audio drivers, Microsoft Sound Mapper disappears, but NVDA handles this gracefully and simply displays nothing in the output device combo box.

Merged in r3388. Thanks to Hans Hillen for testing.
Changes:
State: closed

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

No branches or pull requests

2 participants