| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018770 | MMW 5 | Hotkeys | public | 2022-01-22 22:16 | 2022-01-24 22:05 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | unable to reproduce | ||
| Target Version | 5.0.3 | ||||
| Summary | 0018770: Hotkeys: Media Keys stopped working | ||||
| Description | Play/Pause and Stop Key stopped working. Investigation found that unlike Prev/Next Play/Pause did not parsed APPCOMMAND on keypress. And MM Detect it as HID device, but as Key UP (HID 325) is same code for both keys it can't be assigned even that Play/Pause Have different key on Key Down (HID 333) and Stop key down is not even detected. Supplied Video of assigning key, LOG from my Key logger application that clearly shows Key send correct VKeys and Debug Log file. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I briefly tested and cannot replicate, in my case the Media play/pause is recognized both as HID and as AppCommand, additionally also by MediaTransferControl on Win10, so by three different methods: image.png (13,424 bytes) |
|
|
Checking your debug log and for some reason in your environment the HSHELL_APPCOMMAND from MMHelper.dll isn't coming at all, can you check whether MMHelper.dll is presented in your MM install folder and whether any previous verison of MM4/MM5 can detect your media keys correctly? I am unable to replicate with any of my keyboards. EDIT: In the log I further see that "RIDEV_EXINPUTSINK was registered successfuly" in your case so it should work. Also try whether MM4 catches it correctly and whether PreferLLKeysHook param in MediaMonkey.ini of MM4 has any impact on this. The param ins't read by MM5 though. |
|
|
Adding PreferLLKeysHook in MM4 makes Play/Pause be detected every time as event vKey: 00B3/Media Play Pause key pressed. THX for pointing in LOG as on lines: 00018139 489.95846558 [10064] MM5 [13488](R) Handling HID: 131141/264 00018141 490.10293579 [10064] MM5 [13488](R) Handling HID: 131141/256 00018142 490.10351563 [10064] MM5 [13488](R) Going to execute hotkey action: playPause, ShortCut: HID Key (ID: 325) It is clear that MM reacts to HID 13141/256 which is in my key logger Key up state where 131141/264 is actual key code and as 131141/260 is code for STOP while it is detected as 131141/256, so MM is actually execute Play and then immediately Stop within few milliseconds later that resulted in nothing happen. You can also see that my key logger (bug18770.jpg) Only HID even is detected and vKey (key pressed) without app command for Play/Pause liek it is detected for PLAY NEXT. As you pointed that you can't replicate with any of your keyboards I went and Completely uninstalled Logitech G19s Keyboard software -> Restarted windows -> Changed USB post for Keyboard -> tested if it works and then reinstalled Logitech G19s Keyboard software. After that both play/pause and stop were detected by all three types ( HID, AppCommand and MediaTransferControl). Resolving as Unable to reproduce. |
