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

Warn user when access to the microphone is blocked in the privacy settings (Windows 10) #3347

Closed
ghost opened this issue Feb 24, 2018 · 14 comments
Labels
audio client feature-request This issue or PR deals with a new feature windows

Comments

@ghost
Copy link

ghost commented Feb 24, 2018

With Mumble (1.2.19) I have problems with the input.
It recognises my microphone until I am in the Audio Settings at the point where you can decide between the different voice recognition methods (Push-To-Talk and Voice recognition etc.)

I never had this problem until I installed my sound card. No other application (Discord, TS3..) has problems with multiple sound cards / chips -> On board and external..

@ghost ghost changed the title [Windows] Input problem with multiple sound cards [Win 10] Input problem with multiple sound cards Feb 24, 2018
@davidebeatrici
Copy link
Member

Could you install the latest snapshot and see if the issue persists, please?

@ghost
Copy link
Author

ghost commented Feb 25, 2018

I could solve the problem by running the program as an administrator.
That's an interesting behaviour of the program..

@mkrautz
Copy link
Contributor

mkrautz commented Feb 25, 2018

That would indeed be surprising and unexpected. Mumble is not intended to be run as admin.

Could you elaborate a bit on how to you reproduce this problem? You're saying that your microphone works perfectly until you click Configure -> Settings, and visit Audio Input -- without doing anything in the settings dialog?

@ghost
Copy link
Author

ghost commented Feb 25, 2018

That's indeed surprising. Even more surprising is, that I can't reproduce this..

@ghost
Copy link
Author

ghost commented Feb 25, 2018

Oh I could reproduce this. It's indeed a bug. At the first time it did not happen.. but now

@ghost
Copy link
Author

ghost commented Feb 25, 2018

I made a video corresponding to this: https://www.youtube.com/watch?v=1L_uPTfqQLw
That's weird.. I can't revert it this time even when I execute Mumble as an administrator..
I even tried the newest snapshot. Same problem. Maybe it is a bug which appears sometimes?
I should also say that I use the standard Windows drivers for my internal sound chip.
For my sound card I naturally use the drivers from the manufacturer: http://www.delock.de/produkte/G_89249/dokumente.html?setLanguage=en

@ghost
Copy link
Author

ghost commented Feb 25, 2018

Oh no.. That's so embarrassing.
The slider, as you can see in the Video, was all the way to the left..
The problem sits right in front of the display like most of the times.

@mkrautz
Copy link
Contributor

mkrautz commented Feb 25, 2018

As far as I can see, no slider being all the way to the left in your video should cause the mic problems you're seeing.

@ghost ghost changed the title [Win 10] Input problem with multiple sound cards [Win 10] Input problem Feb 25, 2018
@davidebeatrici
Copy link
Member

@Singustromo Does it happen with the latest snapshot?

@frenchiveruti
Copy link

Hello, I've downloaded both snapshot and stable 1,2.19, both of them give me issues with my microphone on windows 10. I've win 10 Pro Version 1803 on 17134.191 compilation.
I can hear myself on windows 10 configuration for the mic, and discord web through firefox detects my voice and I can hear myself too, but when I go to mumble config, nothing, totally dead as if I didn't have a mic, and I have tried every single option of "input" although I only have one device which is the microphone. On a side note, the "WASAPI" on the config looks greyed out, I don't know if it has something to do with it.
I'm actually using the integrated chipset for this motherboard: https://www.asrock.com/mb/Intel/H81M-VG4/
Using the FRONT panel plugs, I didn't try the rear ones because they're too far.
Any idea on what could be the issue here?
I'm really curious to know why, and also I want to use the microphone.

@frenchiveruti
Copy link

Both times I used the program in admin mode, and normal user mode.

@frenchiveruti
Copy link

OK FIXED IT, Windows 10 privacy settings was not allowing apps to access the microphone, and mumble was a victim of that.

@tumik
Copy link

tumik commented Jan 6, 2019

Thanks @frenchiveruti - I've had the same issue for a while, even starting Mumble as Administrator didn't work, but it was fixed by allowing apps to use a microphone from the Win 10 privacy settings.

Is there a way Mumble could detect if it doesn't have the permission to use a microphone and give an informative error message about it? Currently it allows you to select the microphone device without errors but there's just no audio input at all, just silence.

@davidebeatrici davidebeatrici added the feature-request This issue or PR deals with a new feature label Jan 6, 2019
@davidebeatrici davidebeatrici changed the title [Win 10] Input problem Warn user when access to the microphone is blocked in the privacy settings (Windows 10) Jan 6, 2019
@davidebeatrici
Copy link
Member

Is there a way Mumble could detect if it doesn't have the permission to use a microphone and give an informative error message about it?

Message added in #3572.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
audio client feature-request This issue or PR deals with a new feature windows
Projects
None yet
Development

No branches or pull requests

4 participants