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 stops responding when a bluetooth audio device is connected to the computer #4178
Comments
Attachment NVDA_Log_2014-06-08.log added by k_kolev1985 on 2014-06-08 11:07 |
Comment 1 by jteh on 2014-06-09 04:46
I assume you mean the Bluetooth headset, not your system sound card? I assume this issue does not occur if you set NVDA to use your system sound card? Can you set NVDA to use the HFP output instead of the A2DP output? If so, what happens if you do this? My suspicion is that when the headset/driver switches to HFP, the A2DP output freezes, even though it still remains active according to the system. Windows probably doesn't report that the default playback device has changed, so NVDA continues to try to use the A2DP output. If you're, say, playing music when you switch to the Recording tab, does it too stop playing until you switch back to the Playback tab? What happens to system sounds once you switch to the Recording tab? I'm not sure there's anything we can do about this. An audio output shouldn't ever freeze like that. That seems like a pretty serious bug in the driver. |
Comment 2 by k_kolev1985 (in reply to comment 1) on 2014-06-09 08:17
Actually, when I wrote about setting the output device and when testing, I meant doing it before I connect the bluetooth headset to the computer and not after that. If I switch NVDA to use the sound card after connecting the headset, the freeze doesn't occur, because NVDA uses the sound card output (my analog speakers) and not the headset.
Yes, after connecting the bluetooth headset to the computer, I can set NVDA to use the HFP output instead of the A2DP one. In this case, every time NVDA speaks, the driver switches the audio output to the HFP one, interrupting (pausing) so the sounds (incl. music playback) played via the A2DP output. As soon as NVDA stops speaking, the driver reverts the audio output to the A2DP one.
If I switch to the recording tab (switch the output to the HFP one) while playing music, the music playback gets paused until switch to the A2DP output again. I think the same happens to the system sounds as well (at least as far as I could test). |
Comment 3 by jteh on 2014-06-09 08:33 Leaving open because I don't have such a device and can't test this. Hopefully, someone who has one can come up with a work around, but unfortunately, I very much doubt it. |
@jcsteh's #4178 (comment) implies that someone with such a device would be in a position to investigate this bug further. Clearly, no one has stepped up with necessary prerequisites in the past three years. Additionally, Jamie very much doubts that a work-around for an issue of this kind even exists. If @k_kolev1985 does not disagree, I suggest closing as cantfix. @ehollig |
Since this is not a bug in NVDA itself and a workaround from NVDA is probably not possible, I agree that the issue should be closed. I've sent a feedback to Microsoft about this via the Feedback Hub, which can be found here: https://aka.ms/bknmwh. I don't know if that way the issue will get to the right people at Microsoft and if they will do something about the issue, but that is the only way that I know of to report bugs to Microsoft. Well, actually, there is another way via some sort of forums for reporting bugs and sending ideas and I might use that channel as well. 😀 |
As this is not an issue with NVDA and an appropriate bug has been filed with Microsoft, closing as requested in #4178 (comment) |
Reported by k_kolev1985 on 2014-06-08 11:06
'''Description:'''
Until recently, I was using the TOSHIBA Bluetooth Stack for my bluetooth needs (mainly for connecting my bluetooth headset and sending files to my tablet and my phone). When connecting my bluetooth headset to my computer, it was a little tricky, but not impossible, to make NVDA send its audio output to the bluetooth headset (no matter if via the A2DP or the HFP (hands-free) protocols). That - using the TOSHIBA Bluetooth Stack software.
Yesterday I've decided that the TOSHIBA Bluetooth Stack software was too heavy and too bloated for my needs and taste. So, I've uninstalled it and started using the built-in Bluetooth functionality of Windows itself. It's not bad, except for the too long automatically generated PIN codes for pairing, but I can live with that.
I've noticed however, that if the bluetooth headset is connected to the computer via both the A2DP and HFP protocols and the HFP protocol kicks in (it does specially when on a Skype call via the Skype app for Windows 8 and when in the "recording" tab of the "Sound" in the Control Panel), NVDA will stop responding: no sound comes from it and the NVDA commands stop working. As soon as the headset switches back to the A2DP protocol, NVDA starts working normally again.
I've set NVDA's logging level to "Input/Output", reproduced the issue and I'm attaching here the log file witch should hopefully contain some useful information about what's going on.
'''NOTES:'''
'''Steps to reproduce it:'''
'''Actual results:''' When the HFP protocol is the active one, NVDA stops talking and will not respond to commands.
'''Expected results:''' NVDA should be able to work even if the HFP protocol is active and use that audio for speech output. I think NVDA would work normally if it "knows" to automatically switch its speech output to the "Headset" audio device, but it doesn't. And since it doesn't respond to commands, we can't switch the speech output device manually either. Actually, it seams that screen readers like NVDA and Narrator don't know how to output their speech to the default communication device and that is why they react like that in a situation like that. Though I might be wrong.
'''Test environment:'''
The text was updated successfully, but these errors were encountered: