It seems that BMTP is missing the release of the command key after switching apps that are running in different desktop/spaces after using the shortcut command+tab.
after pressing the command key, it shows the log ‘CMD PRESSED’
after releasing the command key, it shows the log ‘CMD RELEASED’ and the notification ‘CMD RELEASED’
after pressing the shortcut command+F12, it shows the log ‘CMD+F12 PRESSED’ and the notification ‘CMD+F12 PRESSED’
Steps to reproduce the issue:
Open any app in desktop 1 (i.e. System Settings)
Open any other app in desktop 2 (i.e. TextEdit)
Go to desktop 2 and activate TextEdit
Use the command+tab shortcut to select the System Settings app
Release the command key
The System Settings app is activated and desktop 2 changes to desktop 1
Now press F12 key alone. Everytime you press the F12 key alone, you will see the notification ‘CMD+F12 PRESSED’. It seems that BMTP is not aware that the command key has been released, and it reacts as the command key is still pressed.
Pressing and releasing the command key stops the issue
The issue occurs with any app change. System Settings and TextEdit are just examples.
Using BMTP 1.9.1 build 1064 and macOS Sonoma 14.7.1
I would appreciate if you could fix this issue as soon as possible. Thanks a lot.
I’m able to duplicate it on my Mac MINI M4. I’m not sure if it has something to do with the fact that then CMD key is also a part of a combination key to switch applications. It appears that it is only recognized for release if you are in the same workspace.
Also, on my Keyboard for F12, I need to also include function no matter how I set Fn key behavior in Systems setting, so for CMD F12 I have to hit CMD fn and F12.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
As I said in previous posts, I confirm that this issue only happens when switching apps that are in different desktops after pressing the cmd+tab shortcut.
Regarding F12, this shortcut is working fine for me. I can set the shortcut like this and the output action is executed as expected (my system settings are configured to always use F1, F2, etc):
It appears the issue is that you need to break up your keystrokes. The following translator 0.0 presses CMD down when you send note 0 on MIDI CH1 but only if you have not sent the keystroke already. We use the global variable ga to determine if the keystroke has already been sent.
Translator 0.1 sends the tab key every subsequent note 0 message.
The key here (no pun intended) is to send the CMD up key when you are done (translator 0.2). For this I use MIDI IN note 1. I then set ga back to 0 so the next time you press note 0, the process will repeat. I add a delay to allow keyboard processing to complete on translator 0.1.
I think the issue here is that sending a partial shortcut can cause some issues, so you need to break them up.
I’m not convinced that the behavior of Bome MIDI Translator Pro is really the issue here. It is just the way we need to work around how Mac keyboard processing works.
Of course, you can change the incoming triggers but make sure translator 0.0 and 0.1 have the same incoming trigger.
Sorry for the delay in getting back to you!
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Well looking back, I can’t verify that it is a bug. I was unable to reproduce it, and actually looking back wasn’t sure how I confirmed it, so I just created something that works. Keystroke handling on the Mac seems very unusual to me as compared to Windows. I’ll continue to explore but I think the most important thing is to make something that meets your needs with our current implementation.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
