Hello, I found the solution to my problem here: Dealing with accidental double/duplicate midi messages but I can’t get this solution to work with my translator. The translator is simple, consisting of 10 program changes and 10 keystroke outputs, and my only goal is to limit keystroke outputs to one every 500ms. I can’t figure out why my configuration isn’t working and I’ve spent hours on this. Please help, thanks!
Behringer FCB1010 keystrokes.bmtp (4.2 KB)
Hi and welcome to the Bome community!
Well it looks like the only improvement I might make to it is to call Perform 'Focus’in the rules of translator 1.0. This trigggers translator 1.3 will output it to provide focus to the desired application. Maybe your application was not in focus prior to sending keystrokes as keystrokes are send to the currently focused application. In my case I used my standard editor “editplus.exe” but you probably want to set it to your computer application.
The perform outgoing action was introduced in version 1.9.0, I believe. Later versions should work as well. We are currently at 1.9.2.
Behringer FCB1010 keystrokes-sjc.bmtp (4.3 KB)
If this doesnt’t fixe it. Please capture and share your log window with MIDI IN, Incoming, MIDI OUT,and Outgoing checked.
Steve Caldwell
Bome Customer Care
Hi Steve,
I think you may be misunderstanding my issue. My translator is working. Dealing with accidental double/duplicate midi messages The solution you created in this link, “Dealing with accidental double/duplicate midi messages”, which I attempted to add to my translator, is not working.
Ableton is reading the keystrokes without issue. However, even after adding your modification from the thread linked above, it’s allowing the same keystroke to be triggered an unlimited number of times, when it should only be allowing one keystroke per 500ms.
I can’t try out the file you sent me because, for some reason, Ableton Live 12 isn’t on the list of applications I can Focus to, but I’m not totally sure if this suggestion is relevant anyways.
Thanks for trying, let me know if you have any other ideas.
Yes, sorry, I totally messed up on the reported problem. You can try the below project I put the choke preset in preset 0.0 and used it’s input value (PC #) to call the other keystroke translators in preset 1. Depending on the PC number only of the key translators will fire an outgoing keystroke. Translator 0.0 will only fire an outgoing action if the 500ms watchdog timer is not running. Then it sends a focus message to translator 0.2 and a keystroke message to the translators in preset 1,
Translator 1 will only trigger keystrokes if the timer is not running (ga=0)
In order to focus on Ableton, it must be running. It might be called ‘Live’ or something else. If focus is not your issue, you can just disable the focus translators (0.2) and make sure Ableton Live is in focus when you are running the application.
To be honest, I would probably use MIDI learn and send MIDI messages instead of keystrokes, anyway because Ableton Live can recieve MIDI messages, but I guess that is up to you.
Behringer FCB1010 keystrokes-sjc-a.bmtp (3.7 KB)
Steve Caldwell
Bome Customer Care