Krzmbrzl
commented
1 year ago Do you have positional audio enabled in Mumble? If so, could you try turning off Link to Game in the settings and see if the issue persists (after a restart of Mumble)?
Closed Bradley-Schneider closed 1 year ago
Krzmbrzl
commented
1 year ago Do you have positional audio enabled in Mumble? If so, could you try turning off Link to Game in the settings and see if the issue persists (after a restart of Mumble)?
Bradley-Schneider
commented
1 year ago Do you have positional audio enabled in Mumble? If so, could you try turning off
Link to Gamein the settings and see if the issue persists (after a restart of Mumble)?
Ah yes, I completely neglected to mention what I tried already.
"Link to Game and Transmit Position" is disabled. "Enable Shortcuts in privileged applications" is disabled (Saw another issue that was vaguely related, regarding global hotkeys) "Enable XInput" is disabled (Disabled in case polling my controller was causing slowdowns or something) Overlay is also disabled.
Outside of these I can't think of anything else that is relevant.
EDIT: Please ignore me misclicking and closing this issue lol.
Krzmbrzl
commented
1 year ago "Enable XInput" is disabled (Disabled in case polling my controller was causing slowdowns or something)
So I take it you are on Linux, not Windows, correct? (Your initial comment states Windows)
Are you using Wayland or X11?
Hartmnt
commented
1 year ago So I take it you are on Linux, not Windows, correct? (Your initial comment states Windows)
No, there is also a XInput for Windows which succeeded DirectInput (?) Something like that. The logs and system information OP posted also say Windows 10
Hartmnt
commented
1 year ago "Enable Shortcuts in privileged applications" is disabled (Saw another issue that was vaguely related, regarding global hotkeys)
@Bradley-Schneider Have you tried disabling "Global Shortcuts" in the Mumble shortcut settings tab? That should probably tell us, if any of your peripheral devices is causing the issue.
davidebeatrici
commented
1 year ago No, there is also a XInput for Windows which succeeded DirectInput (?) Something like that.
XInput is actually poorly designed, which led to DirectInput being used for many years despite Microsoft declaring it legacy. From the Wikipedia page you linked:
Raw input is the proper replacement for both.
We kept support for XInput just because we currently only support analog input through it.
Bradley-Schneider
commented
1 year ago "Enable Shortcuts in privileged applications" is disabled (Saw another issue that was vaguely related, regarding global hotkeys)
@Bradley-Schneider Have you tried disabling "Global Shortcuts" in the Mumble shortcut settings tab? That should probably tell us, if any of your peripheral devices is causing the issue.
Yeah so while troubleshooting on my own I wasn't sure which option was the one for Global Shortcuts. So I just disabled them all to be safe, Best guess is "Enable GKey" is the one, but the others seemed relevant too.
So I've had all of the above disabled, further there are no shortcuts setup in the shortcuts table, that's empty. Those settings don't seem to impact the issue I'm having either enabled or disabled.
Krzmbrzl
commented
1 year ago No, there is also a XInput for Windows which succeeded DirectInput (?) Something like that
Ah okay. Didn't know that.
Best guess is "Enable GKey" is the one
Nah - GKeys are keys on Logitech devices, which are usually called G1, G2, etc.
I'm not even sure if we have an option to disable shortcuts on Windows (in 1.4) :thinking:
Bradley-Schneider
commented
1 year ago Nah - GKeys are keys on Logitech devices, which are usually called G1, G2, etc.
Ah Logitech GKeys that makes sense now.
I'm not even sure if we have an option to disable shortcuts on Windows (in 1.4) 🤔
Yeah, looking through the other tabs I can't locate any toggles related to disabling shortcuts; seems it isn't implemented. Is there a way to do that via registry perhaps?
Hartmnt
commented
1 year ago I'm not even sure if we have an option to disable shortcuts on Windows (in 1.4)
I see.
@Bradley-Schneider In that case could you please try to unplug your peripheral devices and test again? I think we are pretty stumped here as there is nothing special in the logs and we will have a hard time reproducing the issue (due to a lack of hardware and operating systems).
If you could somehow narrow down what exactly causes the problem, hardware or software, that would be of great help.
Bradley-Schneider
commented
1 year ago If you could somehow narrow down what exactly causes the problem, hardware or software, that would be of great help.
Appreciate the help so far! I'll attempt to isolate what the heck it could be and update you guys, really is an odd issue.
Krzmbrzl
commented
1 year ago In that case could you please try to unplug your peripheral devices and test again?
Ah. Now that you mention it: there have been reports where analog input devices (e.g. a Joystick) can drive up the CPU usage through the shortcut system. -> #6054
Bradley-Schneider
commented
1 year ago Well I figured out the fix, but no concrete reason for why the issue occurs. I'd reckon it is highly unlikely to be a Mumble related issue which is good. It's probably an ASUS BIOS or driver issue, or a TOPPING driver issue which will certainly never be addressed LOL.
Typically I have my DAC plugged into the USB 2.0 header on my motherboard which doubles as the one used for BIOS Flashback. I disconnected that, because my intuition was pointing me that direction. I let Windows default to whatever other sound device and performed the same reproduction steps.
Issue is gone! Programs opened correctly.
So I plugged my DAC into one of the generic 3.0 headers and set it up in Windows with my typical settings. Tried it again... and issue is still gone!
I've never had problems in the past using those dedicated BIOS ports for lower-bandwidth devices but I suppose on this particular board it isn't as stable. It does stand out as strange to me that Mumble was the only program to trigger the issue, but I don't think it's at fault here.
In hindsight I should have looked into that first, so I apologize for taking up your time. At least this thread will benefit others who may encounter a similar issue. I did appreciate the help though!
davidebeatrici
commented
1 year ago No worries and thank you very much for the extensive testing!
How's the Mumble log now?
Bradley-Schneider
commented
1 year ago Log doesn't seem great, gonna try a restart and grab another one in case. If you think a verbose log would be useful I could try that too.
[30772] Args: /detect
[30772] Detect mode!
[30772] Unable to initialize Logitech LCD library. (Error: 1722)
[27476]
Hartmnt
commented
1 year ago @Bradley-Schneider Wait, but the issue (be it a BIOS issue or not) did originally only occur when Mumble was running, right?
So both the USB 2.0 connection AND Mumble had to be active to trigger this?
That would suggest something fishy is still going on, no?
Bradley-Schneider
commented
1 year ago Yeah, it is certainly strange behaviour... It did indeed only occur when Mumble was running and while on that USB 2.0 port.
To add yet another thing to the pot; I totally forgot that I'm always running Peace / APO EQ in the background and that configuration was disabled by switching ports and I forgot to reconfigure it. I thought for certain enabling that would bring the issue back, but nope it's configured again and no issues yet...
Though it does seems I'm getting some errors after swapping ports that weren't in my original log.
[22316] Args: /detect
[22316] Detect mode!
[22316] Unable to initialize Logitech LCD library. (Error: 1722)
[14592]
Bradley-Schneider
commented
1 year ago Ah... issue is back now AND I fixed the errors in my previous log.
The difference was I changed the default output device in Mumble from "Default" to specifically my DAC. I require using it in this mode because it's used in tandem with VB-Cable to separate audio channels.
[23428] Args: /detect
[23428] Detect mode!
[23428] Unable to initialize Logitech LCD library. (Error: 1722)
[23184]
Hartmnt
commented
1 year ago So using your DAC as AudioOutput device is causing the issue, correct?
Bradley-Schneider
commented
1 year ago So using your DAC as AudioOutput device is causing the issue, correct?
Sorry, should have clarified. My default device in Windows was always my DAC in testing unless specified otherwise.
First to note is the issue was not occurring while I had those 2 errors occurring in the Mumble log.
Manually specifying that Mumble specifically use my DAC vs just "Default Device" (which was STILL my DAC in Windows) both solved those 2 errors, and caused the issue to return.
Further changing back to "Default Device" after this still causes the issue to occur, and most notably it still occurs even on entirely different output devices for instance HDMI-Audio and virtual devices.
Next, I figured I'd just mess with my INPUT settings. I changed the "Default Device" in Mumble (My ModMic Wireless) to a virtual device (VB-Cable) and now the issue is gone. Switching it back to "Default Device" or directly to my ModMic Wireless and the issue returns.
So I think it is actually my ModMic Wireless. I think earlier my DAC didn't handshake properly with Mumble after swapping USB ports causing those Client errors, and as soon as I manually changed the audio device that was resolved. Thus mumble was able to function and so the issue returned.
I've tried the following to address the microphone.
None of those helped unfortunately, and I'm out of ideas and time at the moment; will follow up again later!
davidebeatrici
commented
1 year ago I actually spotted something weird in your log, that's why I asked for an up-to-date one (confirming my suspicion):
[23184] 2023-07-13 06:11:18.305 WASAPIInput: Mic Stream format 1
[23184] 2023-07-13 06:11:18.305 WASAPIInput: Stream Latency 0 (1056)
[23184] 2023-07-13 06:11:18.308 WASAPIOutput: Output stream format 1
[23184] 2023-07-13 06:11:18.308 WASAPIOutput: Stream Latency 0 (1056)
[23184] 2023-07-13 06:11:18.308 WASAPIOutput: Periods 10000us 3000us (latency 0us)
[23184] 2023-07-13 06:11:18.308 WASAPIOutput: Buffer is 22000us (1)The latency cannot be 0...
Bradley-Schneider
commented
1 year ago Damn, nice catch.
I had a bit of time just now to test with another microphone, and it has the exact same issue of showing 0 latency and the unresponsive applications issue. This is also a ModMic but the 3.5mm wired version plugged directly into the Mic Line In on my mobo, weird that it's happening on this as well since it's a very generic device in terms of compatibility.
[23008] Args: /detect
[23008] Detect mode!
[23008] Unable to initialize Logitech LCD library. (Error: 1722)
[17084]
Is this a configuration issue on my end you think? Also, I can test with a USB microphone later if necessary.
Bradley-Schneider
commented
1 year ago Not sure if this is super helpful but there are 3 other open issues on Mumble that contain that same 0 latency log.
Specifically: "WASAPIInput: Stream Latency 0 (1056)"
As for "WASAPIOutput: Stream Latency 0 (1056)" there are no open issues but there are these closed ones.
Hartmnt
commented
1 year ago Not sure if this is super helpful but there are 3 other open issues on Mumble that contain that same 0 latency log.
I think this search query will work just fine: https://github.com/mumble-voip/mumble/issues?q=is%3Aissue+%22latency+0us%22
Bradley-Schneider
commented
1 year ago Well, it's probably safe to close this issue; I'll leave it to your discretion though.
The ONLY software I use that interfaces with the microphone is Mumble, so I didn't have any use case to really test outside of that.
However, in an attempt to bypass the issue I used Discord's voice feature in it's place and discovered that it's not Mumble specific. It's ANY application that accesses the microphone. I should have caught that much earlier.
Further, I unfortunately did not grab the logs for this but I can add them later; on my older system I recently replaced running the same windows environment with the same devices the issue does not occur BUT the "Stream Latency 0" log does still appear there for me.
Krzmbrzl
commented
1 year ago Thanks for sharing your insights :+1: Under these circumstances, I will indeed close the issue.
Description
I run Mumble Server and Client on the same Windows 10 machine and don't have any issues with Mumbles functionality itself outside of my own configuration troubles unrelated to this issue.
However, the Mumble Client causes strange slowdowns in other applications simply by being open. It does not seem to matter if I am connected to a server, disconnected or trying to connect. The affected programs I noted are:
This likely also affects other software outside of this but these are the programs I most commonly use at the same time as Mumble. The most obvious and annoying problem is while the Mumble client is open, launching any of the programs I listed will take 10-12 seconds as opposed to it being instantaneous when it is not running. In addition these programs will be much less responsive in general when running as opposed to normal.
The issues are always fully resolved by simply closing the Mumble Client (and restarting the other application to be safe) Note, Mumble Server has no effect on this only the Mumble Client.
I am wondering if it could also be one of my connected devices as well. DAC, Wireless Microphone, Gamepads as I see there are some open issues related to some of these but they don't describe the issues I am encountering.
I will provide any requested logs or other information, and am willing to attempt troubleshooting if anybody has suggestions. Love Mumble otherwise!
Steps to reproduce
Mumble version
1.4.287 and 1.5.517
Mumble component
Client
OS
Windows
Reproducible?
Yes
Additional information
Relevant System Information Windows 10 22H2 19045.3155 Ryzen 7950X3D Asus X670 ProArt (Not using any of the onboard audio though)
Relevant Connected Devices Topping D30 Pro (External DAC, could be a source of problems? #3224 ) AntLion ModMic Wireless Adapter XBOX 2.4Ghz Adapter (Issue #6054 ?) Switch Pro Controller (Issue #6054 ?)
Relevant Software VB-Cable (Never had issues with this and Mumble, but not impossible that there is a weird interaction) Peace + APO EQ
Relevant log output
Log upon launching Mumble, launching other programs afterwards didn't provide anything useful from what I gathered.
[19844] Args: /detect [19844] Detect mode! [19844] Unable to initialize Logitech LCD library. (Error: 1722) [2096]2023-07-10 04:27:39.294 G15LCDEngine_lglcd: Logitech LCD Manager not detected.
[2096] 2023-07-10 04:27:39.296 libopus 1.3.1-97-g6b6035ae from C:/Program Files/Mumble/client/opus.dll
[2096] 2023-07-10 04:27:39.300 CELT bitstream 8000000b from C:/Program Files/Mumble/client/celt0.0.7.0.dll
[2096] 2023-07-10 04:27:39.303 Theme: "Mumble"
[2096] 2023-07-10 04:27:39.303 Style: "Dark"
[2096] 2023-07-10 04:27:39.303 --> qss: ":themes/Mumble/Dark.qss"
[2096] 2023-07-10 04:27:39.303 Locale is "en_US" (System: "en_US")
[2096] 2023-07-10 04:27:39.476 Database SQLite: "3.35.5"
[2096] 2023-07-10 04:27:39.497 Updating application palette
[2096] 2023-07-10 04:27:39.585 QMetaObject::connectSlotsByName: No matching signal for on_qtvUsers_customContextMenuRequested(QPoint,bool)
[2096] 2023-07-10 04:27:39.766 AudioInput: Opus encoder set for low delay
[2096] 2023-07-10 04:27:39.766 AudioInput: 64022 bits/s, 48000 hz, 480 sample
[2096] 2023-07-10 04:27:39.767 Public list disabled
[2096] 2023-07-10 04:27:39.770 WASAPIInput: Latencies 100000 30000 => 100000
[20432] 04:27:39.770 21 AudioDeviceSessionCollection OnSessionCreated
[20432] 04:27:39.771 21 DesktopAppInfo DisplayName read failed mumble 0x80070490
[2096] 2023-07-10 04:27:39.777 WASAPIOutput: Latencies 100000 30000 => 100000
[20432] 04:27:39.781 21 AudioDeviceSession Create mumble {0.0.0.00000000}.{b58dd1e6-0a1f-4443-bc93-b36713b148ab}|\Device\HarddiskVolume3\Program Files\Mumble\client\mumble.exe%b{00000000-0000-0000-0000-000000000000}|1%b2096
[20432] 04:27:39.782 UI AudioDeviceSessionCollection AddSession mumble {0.0.0.00000000}.{b58dd1e6-0a1f-4443-bc93-b36713b148ab}|\Device\HarddiskVolume3\Program Files\Mumble\client\mumble.exe%b{00000000-0000-0000-0000-000000000000}|1%b2096
[2096] 2023-07-10 04:27:39.782 WASAPIInput: Mic Stream format 1
[2096] 2023-07-10 04:27:39.782 WASAPIInput: Stream Latency 0 (1056)
[2096] 2023-07-10 04:27:39.792 WASAPIOutput: Output stream format 1
[2096] 2023-07-10 04:27:39.792 WASAPIOutput: Stream Latency 0 (1056)
[2096] 2023-07-10 04:27:39.793 WASAPIInput: Echo Stream format 1
[20432] 04:27:39.793 21 AudioDeviceSession OnStateChanged Active mumble {0.0.0.00000000}.{b58dd1e6-0a1f-4443-bc93-b36713b148ab}|\Device\HarddiskVolume3\Program Files\Mumble\client\mumble.exe%b{00000000-0000-0000-0000-000000000000}|1%b2096
[2096] 2023-07-10 04:27:39.795 WASAPIOutput: Periods 10000us 3000us (latency 0us)
[2096] 2023-07-10 04:27:39.795 AudioInput: Initialized mixer for 1 channel 48000 hz mic and 2 channel 48000 hz echo
[2096] 2023-07-10 04:27:39.795 WASAPIOutput: Buffer is 22000us (1)
[2096] 2023-07-10 04:27:39.796 AudioOutput: Initialized 2 channel 48000 hz mixer
[2096] 2023-07-10 04:27:39.832 AudioInput: Noise canceller disabled
[2096] 2023-07-10 04:27:39.832 AudioInput: ECHO CANCELLER ACTIVE
[2096] 2023-07-10 04:27:39.847 Database SQLite: "3.35.5"
[2096] 2023-07-10 04:27:39.847 OpenSSL Support: 1 (OpenSSL 1.1.1k 25 Mar 2021)
[2096] 2023-07-10 04:27:39.851 SSL: CA certificate filter applied. Filtered size: 104, original size: 104
[2096] 2023-07-10 04:27:39.851 ServerHandler: TLS cipher preference is "TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:AES256-SHA:AES128-SHA"
[2096] 2023-07-10 04:27:39.853 ServerHandler: QOS2 loaded
[2700] Suspending
Screenshots
No response