moncuex Posted December 5, 2015 Share Posted December 5, 2015 I went to Windows 10 tonight and I could hear everyone in mumble but they couldn't hear me. I went through the Config - Audio Wizard, and no matter what I chose it wouldn't work. I reverted back to Windows 8 as everything was working and it's still not working. I use a Afterglow Wireless Gaming Headset - it has USB and then plugs into the front Headset slot. I can't pinpoint if it's my microphone or something else. I'm running 1.2.10 -- if I need to provide some kind of code - let me know where to get it and I'll provide. Thank you. Quote Link to comment Share on other sites More sharing options...
Administrators mkrautz Posted December 7, 2015 Administrators Share Posted December 7, 2015 Could you try to run Mumble as you normally would?Connect to a server, try speaking -- or whatever you're doing to test that it does not work, Audio Wizard should be OK to.Then close Mumble.Then, open the file %APPDATA%\Mumble\Console.txt (you can paste it into the Run prompt to open your default text editor). Then copy the output from the session you just had (you should be able to see it from the timestamps). Then paste it here.If the text you're pasting contains any personal information, please remove that before posting. Thanks. Quote Link to comment Share on other sites More sharing options...
Vorkos Posted December 16, 2015 Share Posted December 16, 2015 My problem is similar, the built in mic stops working when mumble starts up. when mumble is closed, the mic bar moves in the sound control panel, and skype works. when mumble is open, the mic errors when I try to "set up voice control" in windows, and skype also fails to work.2015-12-15 16:49:01.745 DirectSound: Disabled as WASAPI is available2015-12-15 16:49:01.745 ASIO: No valid devices found, disabling2015-12-15 16:49:03.286 G15LCDEngine_lglcd: Logitech LCD Manager not detected.2015-12-15 16:49:03.289 CELT bitstream 8000000b from C:/Program Files (x86)/Mumble/celt0.0.7.0.sse2.dll2015-12-15 16:49:03.291 CELT bitstream 80000010 from C:/Program Files (x86)/Mumble/celt0.0.11.0.sse2.dll2015-12-15 16:49:03.291 Locale is "en_US" (System: "en_US")2015-12-15 16:49:07.421 Database SQLite: "3.7.7.1" 2015-12-15 16:49:07.422 Bonjour: Failed to load dnssd.dll2015-12-15 16:49:07.443 Overlay: Listening on "\\.\pipe\MumbleOverlayPipe" 2015-12-15 16:49:07.567 GlobalShortcutWin: No LowLevelHooksTimeout registry key found.2015-12-15 16:49:07.771 Adding device {6f1d2b60-d5a0-11cf-bfc7-444553540000} Mouse Mouse:52015-12-15 16:49:07.771 Adding device {6f1d2b61-d5a0-11cf-bfc7-444553540000} Keyboard Keyboard:1272015-12-15 16:49:07.774 Adding device {6a7f3050-4ef2-11e4-8002-444553540000} UMDF HID minidriver Device UMDF HID minidriver Device:12015-12-15 16:49:08.034 AudioInput: 40000 bits/s, 48000 hz, 480 sample2015-12-15 16:49:08.044 WASAPIInput: Latencies 100000 30000 => 1000002015-12-15 16:49:08.045 WASAPIOutput: Latencies 101587 30000 => 1000002015-12-15 16:49:08.073 WASAPIOutput: Stream Latency 0 (984)2015-12-15 16:49:08.073 WASAPIOutput: Periods 10158us 3000us (latency 0us)2015-12-15 16:49:08.073 WASAPIOutput: Buffer is 22312us (1)2015-12-15 16:49:08.087 AudioOutput: Initialized 2 channel 44100 hz mixer2015-12-15 16:49:08.168 WASAPIInput: Successfully opened exclusive mode2015-12-15 16:49:08.168 WASAPIInput: Stream Latency 100000 (480)2015-12-15 16:49:08.171 AudioInput: Initialized mixer for 2 channel 48000 hz mic and 0 channel 48000 hz echo2015-12-15 16:49:15.193 Sad panda 2015-12-15 16:49:52.509 OpenSSL Support: 1 (OpenSSL 1.0.1q 3 Dec 2015)2015-12-15 16:49:52.520 SSL: CA certificate filter applied. Filtered size: 110, original size: 1102015-12-15 16:49:52.520 ServerHandler: TLS cipher preference is *censored*2015-12-15 16:49:52.523 ServerHandler: QOS2 loaded2015-12-15 16:50:08.153 AudioInput: 40000 bits/s, 48000 hz, 480 sample2015-12-15 16:50:08.154 WASAPIInput: Latencies 100000 30000 => 1000002015-12-15 16:50:08.155 WASAPIOutput: Latencies 101587 30000 => 1000002015-12-15 16:50:08.168 WASAPIInput: Successfully opened exclusive mode2015-12-15 16:50:08.168 WASAPIInput: Stream Latency 100000 (480)2015-12-15 16:50:08.182 AudioInput: Initialized mixer for 2 channel 48000 hz mic and 0 channel 48000 hz echo2015-12-15 16:50:08.188 WASAPIOutput: Stream Latency 0 (984)2015-12-15 16:50:08.188 WASAPIOutput: Periods 10158us 3000us (latency 0us)2015-12-15 16:50:08.188 WASAPIOutput: Buffer is 22312us (1)2015-12-15 16:50:08.192 AudioOutput: Initialized 2 channel 44100 hz mixer2015-12-15 16:50:21.558 AudioInput: 40000 bits/s, 48000 hz, 480 sample2015-12-15 16:50:21.559 WASAPIInput: Latencies 100000 30000 => 1000002015-12-15 16:50:21.560 WASAPIOutput: Latencies 101587 30000 => 1000002015-12-15 16:50:21.574 WASAPIInput: Successfully opened exclusive mode2015-12-15 16:50:21.574 WASAPIInput: Stream Latency 100000 (480)2015-12-15 16:50:21.588 AudioInput: Initialized mixer for 2 channel 48000 hz mic and 0 channel 48000 hz echo2015-12-15 16:50:21.594 WASAPIOutput: Stream Latency 0 (984)2015-12-15 16:50:21.594 WASAPIOutput: Periods 10158us 3000us (latency 0us)2015-12-15 16:50:21.594 WASAPIOutput: Buffer is 22312us (1)2015-12-15 16:50:21.598 AudioOutput: Initialized 2 channel 44100 hz mixer Quote Link to comment Share on other sites More sharing options...
Administrators mkrautz Posted December 20, 2015 Administrators Share Posted December 20, 2015 Vorkos -- you are using exclusive mode. That means ONLY Mumble has access to your mic.There's a checkbox in Audio Input and Audio Output that allows you to enable/disable the use of exclusive mode.Hope it helps. Quote Link to comment Share on other sites More sharing options...
Administrators mkrautz Posted December 20, 2015 Administrators Share Posted December 20, 2015 Moncuex -- please follow these instructions:You could try one of the Mumble snapshots (1.3.0). They are available on the front page of our website, http://www.mumble.info.They've fixed some bugs with the WASAPI audio system.If the problem still persists, we ask you to create log file for us. Here's how:Open Mumble, and use it like you usually would. As if your headset is working.Talk to yourself or your friends for a few seconds.Quit Mumble.Open the file %APPDATA%\Mumble\Console.txt. Find the relevant parts. That is, the session you just had open (you can use the timestamps to determine...).Once you've found the relevant parts, copy/paste them into a post here in this thread -- or a Pastebin or Gist if you like.Once we have the log, we should be able to help you further.Thanks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.