starred/mumble-mumble-voip

Fork 0

mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00

Shortcut not recognising input is coming from different peripherals #2392

New issue

Open

opened 2026-02-20 22:05:58 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 22:05:58 -05:00

Owner

Originally created by @timotheostan on GitHub (Jan 19, 2022).

Description

Using a twin Thrustmaster T16000M FCS setup, setting a shortcut for Push-to-Talk on one stick reads input from both sticks (i.e. setting the PTT shortcut to be the left stick's trigger causes the right stick's trigger to also function as a PTT shortcut).

Steps to reproduce

Open the Configure dropdown.
Open the Settings window.
Navigate to the Shortcuts menu.
Add a PTT shortcut and set it to left joystick trigger, reading '[044F:B10A]:0'.
Test shortcut by depressing the left joystick trigger (works).
Test shortcut by depressing the right joystick trigger (also works).

Mumble version

1.4.230

Mumble component

Client

OS

Windows

Reproducible?

Yes

Additional information

No response

Relevant log output

No response

Screenshots

No response

Originally created by @timotheostan on GitHub (Jan 19, 2022). ### Description Using a twin Thrustmaster T16000M FCS setup, setting a shortcut for Push-to-Talk on one stick reads input from both sticks (i.e. setting the PTT shortcut to be the left stick's trigger causes the right stick's trigger to also function as a PTT shortcut). ### Steps to reproduce 1. Open the Configure dropdown. 2. Open the Settings window. 3. Navigate to the Shortcuts menu. 4. Add a PTT shortcut and set it to left joystick trigger, reading '[044F:B10A]:0'. 5. Test shortcut by depressing the left joystick trigger (works). 6. Test shortcut by depressing the right joystick trigger (also works). ### Mumble version 1.4.230 ### Mumble component Client ### OS Windows ### Reproducible? Yes ### Additional information _No response_ ### Relevant log output _No response_ ### Screenshots _No response_

deekerman added the

client

bug

GlobalShortcuts

labels

2026-02-20 22:05:58 -05:00

deekerman commented

2026-02-20 22:06:00 -05:00

Author

Owner

@timotheostan commented on GitHub (Jan 19, 2022):

Further testing indicates that the Mumble application is assigning the same identifier number ('[044F:B10A]:0') to each individual T16000M FCS joystick. It successfully assigns a different identifier number to a completely different peripheral (e.g. XBox controller).

@timotheostan commented on GitHub (Jan 19, 2022): Further testing indicates that the Mumble application is assigning the same identifier number ('[044F:B10A]:0') to each individual T16000M FCS joystick. It successfully assigns a different identifier number to a completely different peripheral (e.g. XBox controller).

deekerman commented

2026-02-20 22:06:00 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Jan 20, 2022):

Did you verify that Windows itself is detecting these as individual devices? Do these buttons work independently in other applications?

@Krzmbrzl commented on GitHub (Jan 20, 2022): Did you verify that Windows itself is detecting these as individual devices? Do these buttons work independently in other applications?

deekerman commented

2026-02-20 22:06:00 -05:00

Author

Owner

@timotheostan commented on GitHub (Jan 20, 2022):

Yes, Windows is detecting them as separate devices, and they work independently in other applications (e.g. flight simulators).

@timotheostan commented on GitHub (Jan 20, 2022): Yes, Windows is detecting them as separate devices, and they work independently in other applications (e.g. flight simulators).

deekerman commented

2026-02-20 22:06:00 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Jan 21, 2022):

@davidebeatrici do you have an idea about this?

@Krzmbrzl commented on GitHub (Jan 21, 2022): @davidebeatrici do you have an idea about this?

deekerman commented

2026-02-20 22:06:00 -05:00

Author

Owner

@davidebeatrici commented on GitHub (Jan 21, 2022):

The relevant code:

github.com/mumble-voip/mumble@db3a280585/src/mumble/GlobalShortcut_win.cpp (L565-L622)

@PromeThaeus Do you perhaps see the full device name if you edit the shortcut?

@davidebeatrici commented on GitHub (Jan 21, 2022): The relevant code: https://github.com/mumble-voip/mumble/blob/db3a280585ae0fb7798f18ba6487644e0b97802d/src/mumble/GlobalShortcut_win.cpp#L565-L622 @PromeThaeus Do you perhaps see the full device name if you edit the shortcut?

deekerman commented

2026-02-20 22:06:00 -05:00

Author

Owner

@timotheostan commented on GitHub (Jan 21, 2022):

Edit shortcut menu reads the device as "[044F:B10A] Thrustmaster" regardless of which device is being used to set the shortcut.

@timotheostan commented on GitHub (Jan 21, 2022): Edit shortcut menu reads the device as "[044F:B10A] Thrustmaster" regardless of which device is being used to set the shortcut.