search

mumble-voip / mumble

Mumble is an open-source, low-latency, high quality voice chat software.
https://www.mumble.info
Other
6.43k stars 1.12k forks source link

Shortcuts in Windows do not work reliably #6168

Open Gallimathias opened 1 year ago

Gallimathias commented 1 year ago

Description

I would like to switch from Teamspeak to Mumbel.

I have registered two shortcuts "ctrl + ^" to toggle mute and "pause" to mute myself and to toggle deaf.

As soon as I leave the mumbel window and am on another window (e.g. Firefox, Steam etc..) "Pause" does not work and "ctrl + ^" sometimes (maybe 1 time out of 10 tries works).

I have already tried all additional settings (GKey, XInput etc...) and have not noticed any difference.

Steps to reproduce

  1. Define "ctrl + ^" as switch for toggle

  2. Define "pause" as switch for deaf

  3. Define "pause" as "off" for mute

  4. Go into Firefox or any other window try one of the shortcuts => nothing happens

  5. Go into Mumbel window try one of the shortcuts => it works

Mumble version

1.4.287

Mumble component

Client

OS

Windows

Reproducible?

Yes

Additional information

Windows version: Windows 10, 22H2, 19045.3086

Relevant log output

Dev console output:

<W>2023-07-09 11:46:14.192 G15LCDEngine_lglcd: Logitech LCD Manager not detected.
<D>2023-07-09 11:46:14.223 libopus 1.3.1-97-g6b6035ae from C:/Program Files/Mumble/client/opus.dll
<W>2023-07-09 11:46:14.277 CELT bitstream 8000000b from C:/Program Files/Mumble/client/celt0.0.7.0.dll
<W>2023-07-09 11:46:14.277 ASIO: No valid devices found, disabling
<W>2023-07-09 11:46:14.301 Theme: "Mumble"
<W>2023-07-09 11:46:14.302 Style: "Dark"
<W>2023-07-09 11:46:14.302 --> qss: ":themes/Mumble/Dark.qss"
<W>2023-07-09 11:46:14.302 Locale is "de_DE" (System: "de_DE")
<W>2023-07-09 11:46:15.008 Database SQLite: "3.35.5"
<W>2023-07-09 11:46:15.954 Updating application palette
<W>2023-07-09 11:46:16.223 QMetaObject::connectSlotsByName: No matching signal for on_qtvUsers_customContextMenuRequested(QPoint,bool)
<W>2023-07-09 11:46:16.674 AudioInput: Opus encoder set for high quality speech
<W>2023-07-09 11:46:16.674 AudioInput: 60155 bits/s, 48000 hz, 480 sample
<W>2023-07-09 11:46:15.968 XboxInput: using XInput DLL 'XInput1_4.dll'
<W>2023-07-09 11:46:15.968 XboxInput: using XInputGetStateEx() as querying function.
<W>2023-07-09 11:46:15.970 GlobalShortcutWin: Failed to initialize GKey!
<W>2023-07-09 11:46:16.698 WASAPIInput: Latencies 100000 30000 => 100000
<W>2023-07-09 11:46:16.704 WASAPIOutput: Latencies 100000 26667 => 100000
<W>2023-07-09 11:46:16.717 WASAPIOutput: Output stream format 1
<W>2023-07-09 11:46:16.717 WASAPIOutput: Stream Latency 0 (2880)
<W>2023-07-09 11:46:16.717 WASAPIOutput: Periods 10000us 2666us (latency 0us)
<W>2023-07-09 11:46:16.717 WASAPIOutput: Buffer is 60000us (5)
<W>2023-07-09 11:46:16.718 AudioOutput: Initialized 2 channel 48000 hz mixer
<W>2023-07-09 11:46:16.724 WASAPIInput: Mic Stream format 1
<W>2023-07-09 11:46:16.725 WASAPIInput: Stream Latency 0 (1056)
<W>2023-07-09 11:46:16.735 WASAPIInput: Echo Stream format 1
<W>2023-07-09 11:46:16.735 AudioInput: Initialized mixer for 1 channel 48000 hz mic and 2 channel 48000 hz echo
<W>2023-07-09 11:46:16.749 AudioInput: Using RNNoise as noise canceller
<W>2023-07-09 11:46:16.750 AudioInput: ECHO CANCELLER ACTIVE
<W>2023-07-09 11:46:16.878 Database SQLite: "3.35.5"
<W>2023-07-09 11:46:16.879 OpenSSL Support: 1 (OpenSSL 1.1.1k  25 Mar 2021)
<W>2023-07-09 11:46:16.895 SSL: CA certificate filter applied. Filtered size: 196, original size: 196
<W>2023-07-09 11:46:16.895 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"
<W>2023-07-09 11:46:16.992 ServerHandler: QOS2 loaded
<W>2023-07-09 11:46:17.839 ServerHandler: Failed to add UDP to QOS
<W>2023-07-09 13:50:42.725 WASAPINotificationClient: Device state changed newState= 8 device= "{0.0.0.00000000}.{7c72782e-2fa5-46f0-b1ce-203bddbc901d}"
<W>2023-07-09 13:50:42.793 WASAPINotificationClient: Device state changed newState= 8 device= "{0.0.0.00000000}.{5d6f01ff-4911-4b4e-b5e0-fd48959ade62}"
<W>2023-07-09 13:50:42.865 WASAPINotificationClient: Device state changed newState= 8 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:37.684 WASAPINotificationClient: Device state changed newState= 1 device= "{0.0.0.00000000}.{7c72782e-2fa5-46f0-b1ce-203bddbc901d}"
<W>2023-07-09 14:02:37.805 WASAPINotificationClient: Device state changed newState= 1 device= "{0.0.0.00000000}.{5d6f01ff-4911-4b4e-b5e0-fd48959ade62}"
<W>2023-07-09 14:02:37.890 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:38.055 WASAPINotificationClient: Device state changed newState= 8 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:38.101 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.1.00000000}.{a04d3407-9aa8-474e-809d-bfb969301f47}"
<W>2023-07-09 14:02:38.138 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.1.00000000}.{a04d3407-9aa8-474e-809d-bfb969301f47}"
<W>2023-07-09 14:02:38.139 WASAPINotificationClient: Device added= "{0.0.1.00000000}.{a04d3407-9aa8-474e-809d-bfb969301f47}"
<W>2023-07-09 14:02:38.184 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.1.00000000}.{a04d3407-9aa8-474e-809d-bfb969301f47}"
<W>2023-07-09 14:02:38.350 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.0.00000000}.{5d6f01ff-4911-4b4e-b5e0-fd48959ade62}"
<W>2023-07-09 14:02:38.540 WASAPINotificationClient: Device state changed newState= 1 device= "{0.0.0.00000000}.{5d6f01ff-4911-4b4e-b5e0-fd48959ade62}"
<W>2023-07-09 14:02:38.681 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.0.00000000}.{7c72782e-2fa5-46f0-b1ce-203bddbc901d}"
<W>2023-07-09 14:02:38.946 WASAPINotificationClient: Device state changed newState= 1 device= "{0.0.0.00000000}.{7c72782e-2fa5-46f0-b1ce-203bddbc901d}"
<W>2023-07-09 14:02:39.673 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:39.857 WASAPINotificationClient: Device state changed newState= 1 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:41.114 WASAPINotificationClient: Device state changed newState= 8 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:44.294 WASAPINotificationClient: Device state changed newState= 4 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:02:44.484 WASAPINotificationClient: Device state changed newState= 1 device= "{0.0.0.00000000}.{ba5c57b3-f764-4f2b-bf80-86fe0bcf0d75}"
<W>2023-07-09 14:05:09.428   OpenType support missing for "MS Shell Dlg 2", script 20
<W>2023-07-09 14:05:09.429   OpenType support missing for "Arial", script 20
<W>2023-07-09 14:05:09.430   OpenType support missing for "MS UI Gothic", script 20
<W>2023-07-09 14:05:09.430   OpenType support missing for "SimSun", script 20
<W>2023-07-09 14:05:09.431   OpenType support missing for "Arial Unicode MS", script 20
<W>2023-07-09 14:05:09.448   OpenType support missing for "MS Shell Dlg 2", script 17
<W>2023-07-09 14:05:09.449   OpenType support missing for "Arial", script 17
<W>2023-07-09 14:05:09.450   OpenType support missing for "MS UI Gothic", script 17
<W>2023-07-09 14:05:09.450   OpenType support missing for "SimSun", script 17
<W>2023-07-09 14:05:09.451   OpenType support missing for "Arial Unicode MS", script 17
<W>2023-07-09 14:05:10.058   OpenType support missing for "Segoe UI", script 20

Screenshots

No response

Krzmbrzl commented 1 year ago

Does the same issue persist when using "regular" keys for shortcuts - e.g. A or something like that?

Gallimathias commented 1 year ago

After now getting the Client again running. I tried out a as shortcut to mute. But this is even worser, because it didn't work even inside Mumble. This never works.

grafik

Krzmbrzl commented 1 year ago

@davidebeatrici any ideas?

davidebeatrici commented 1 year ago

With raw input there shouldn't be any such issues.

I wonder whether Windows is altering the behavior with that specific key combination...

Gallimathias commented 1 year ago

Maybe it's related to other applications. I tried Mumble in the Windows sandbox, there everything work like expected.

Gallimathias commented 1 year ago

Maybe also helps as suggested by a friend i tried the screen keyboard out. In Windows Sandbox, Mumble have the same issue with the Screen Keyboard like Mumble with the Real Keyboard on My Pc. On my Real Pc the Screen Keyboard didn't work at all. Or it looks more like every shortcut comes immediately twice.

Windows Sandbox - Real Keyboard => Works Windows Sandbox - Screen Keyboard => Broken Computer - Real Keyboard => Broken Computer - Screen Keyboard => Realy Realy Broken

I don't now if there is a difference by Reading KEyboard values. But in Sandbox there is nothing else inside beside Edge

Krzmbrzl commented 1 year ago

Does the application that you have in foreground when the shortcuts don't work have administrative permissions (Aka: elevated permissions)? If so, see if starting Mumble as administrator makes a difference

Gallimathias commented 1 year ago

No there is no Application with admin rights in foreground.

I test it today without starting any application and watch very detailed what happens there. For me, it looks that the Keyboard signals comes very short after each other. If you look very concentrated on the icons you see that they are very short flicker (on off). But it just a small moment.