BMTP doesn’t seem to be able to tell the difference between e.g. Ctrl/Alt/L and Ctrl/L. I set up a key command in Cubase with Ctrl/Alt/L and found that my Ctrl L key command I had previously set up in BMTP kept firing off.
Is your outgoing action Cntrl-Alt-L or are you using that as an incoming trigger to fire a MIDI message or something else?
What happens if you directly sent your keystrokes to Cubase instead of using Bome MIDI Translator Pro ? Do you get the same results?
If you look at the log Window in Bome MIDI Translator Pro and check Incoming and Outgoing, what is shown?
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
I’m using Metagrid Pro to send Cubase key commands. In this case, Ctrl/Alt/L going directly to Cubase from my keyboard or Metagrid to load a track preset. I have previously set up Ctrl/L as an incoming action in BMTP coming from my mouse to switch grids in Metagrid via outgoing MIDI message and activate a Preset in BMTP. When I fire off my newly made Ctrl/Alt /L key command from my keyboard or Metagrid, BMTP is registering it as a Ctrl/L and carrying out the above functions.
Basically, if I press Ctrl/Alt/L or Ctrl/Shift/L on my keyboard, BMTP is registering it as Ctrl/L.
Ctrl/Alt/L is going directly to Cubase from Metagrid or my keyboard.
OK,
I have not been able to duplicate the behavior but I’m not using MegaGrid as input. Maybe it sends the key combinations too fast.
See the below log entries.
1: IN 1.1 Shortcut: Ctrl+L
2: 1.1:1 Ctrl-L Shortcut pressed
3: IN 1.2 Shortcut: ShiftCtrl+L
4: 1.2:1 CtrlShiftL Shortcut pressed
5: IN 1.0 Shortcut: CtrlAlt+L
6: 1.0:1 Ctrl-AltL Shortcut pressed
And the test project file.
computer-key-test.bmtp (2.3 KB)
If your MetaGrid is sending keystrokes, try the same keystrokes with your computer keyboard to see if you have the same problem. I know I have a Macro keyboard that I had to program to be a bit slower to get some of my applications to work with it.
PS. Please make sure you are running Versio 1.9.1 build 1064. Also note that the incoming keystroke is not suppressed so other application may also interpret them and mess up what Bome MIDI Translator Pro sees depending on the order that the system has defined it’s hotkeys.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hi,
If you swap the Translators to “Physical Keys”, then you should be able to reproduce the behaviour. I went ahead and did that in the project you sent me.
computer-key-test.bmtp (1.9 KB)
I’m not 100% sure but I think that why the shortcut option is now available. Longer key combinations are not always recognized with physical keys. Is there a reason that you cannot use the shortcut option?
In either case, the combinations tested seem to work fine in this case no matter which option is chosen. Maybe close other applications that might use those key combinations and try again.
1: IN 1.1 Keystrokes: Ctrl(L)
2: 1.1:1 Ctrl-L Shortcut pressed
3: IN 1.1 Keystrokes: Ctrl(L)
4: 1.1:1 Ctrl-L Shortcut pressed
5: IN 1.2 Keystrokes: Shift(Ctrl(L))
6: 1.2:1 CtrlShiftL Shortcut pressed
7: IN 1.0 Keystrokes: Ctrl(Alt(L))
8: 1.0:1 Ctrl-AltL Shortcut pressed
9: IN 1.1 Keystrokes: Ctrl(L)
10: 1.1:1 Ctrl-L Shortcut pressed
What application is focused when you are trying this?
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
On my Win 11 system with no other apps running, if I press Ctrl/Alt/L or Ctrl/Shift/L BMTP looks like this:
243347 - IN 1.1 Keystrokes: Ctrl(L)
243347 - 1.1:1 Ctrl-L Shortcut pressed
243347 - IN 1.2 Keystrokes: Shift(Ctrl(L))
243347 - 1.2:1 CtrlShiftL Shortcut pressed
248157 - IN 1.0 Keystrokes: Ctrl(Alt(L))
248157 - 1.0:1 Ctrl-AltL Shortcut pressed
248157 - IN 1.1 Keystrokes: Ctrl(L)
248157 - 1.1:1 Ctrl-L Shortcut pressed
Notice that the “Keystrokes: Ctrl(L)” and the “Keystrokes: Shift(Ctrl(L))” are both numbered: 243347
And the next entry of “Keystrokes: Ctrl(Alt(L))” and “Keystrokes: Ctrl(L)” are both numbered: 248157
This is with theTranslators set to “Physical Keys”.
Yes, in your example with physical keys Ctrl(L) will be triggered with any combination including both Ctrl and L pressed as both of those keys are pressed in the other combinations.
You should use shortcuts to exclusively use them in your case because all keys are required in combination to trigger a given event.
For typical shortcuts with the known modifiers, the Shortcut type will always behave as expected. Physical, as explained, is dumber and will more closely follow the definition.
For example, if you specify just ‘A’, then physical will trigger no matter if any other key (including modifiers) are pressed. For a shortcut ‘A’ it only triggers if no modifier is down.
I’m assumming it works as you desire when using shortcuts, so just stick with that.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
1 Like
If you re-order the translators and put stop processing on the first two as done in the below example , the third will not be triggered when using physical keys.
computer-key-test-b.bmtp (1.9 KB)
Again, for this you should probably just use shortcuts.
Physical keys would be better if you want non-standard Modifiers such as A(B) where A acts as a modifier.
In all cases, incoming keystrokes are not suppressed for downstream applications.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Are you using this with a Mac? All testing I did was on Windows and it might be possible that Mac keystrokes are handled differently as the interals of the Mac keystroke handling is quite different than Windows. If on a Mac, what version and platform are you running?
I’m on Windows 11. And thanks for the example and info. You’ve just solved multiple niggles I’ve had with BMTP inexplicably sending random commands to Cubase, mainly a “Nudge Right” command that’s been driving me crazy. I will change all my “Physical Keys” Translators over to Shortcuts and ONLY use Shortcuts in future. 