In Bome Classic, when translating a MIDI message to a computer keystroke, is it possible to block the midi message from going though? I would like midi notes not to play while that key is being used as a keyboard shortcut.
As an unrelated question, I was also wondering why chaining translators doesn’t work? I want one midi translator to take midi message Y and convert it to the ‘enter’ keystroke, while another one converts Midi message X to Midi message Y.
Make sure MIDI Thru is unchecked in options.
Use 2 translators with the same incoming triggers and different outgoing actions.
Steve Caldwell
Bome Customer Care
Thank you for the help.
I checked and midi thru is definitely unchecked, but I’m still both hearing the note and receiving the keyboard keystroke when pressing the midi key. Could it be Ableton is receiving both Bome’s midi messages as well as the midi controller?
As for chaining messages, I think having the same input for both translators is not quite what I want to do? (I’m trying to convert the messages in chain as follows)
I need midi CC2 → note C#7 → Enter key
But I don’t want the midi CC2 message to ever reach Ableton, I don’t want it to inadvertantly control parameters (which on my midi controller it does)
In effect, what I’m trying to do here is have two different midi messages both trigger ‘enter’ but the reason I tried doing it chain is because I need CC2 to get blocked from actually controlling the DAW while the Bome preset is active.
Muting / silencing midi messages as they convert to a computer keystroke would achieve the same result that I’m trying to achieve though.
So I tried 2 translators with the same incoming message like you mentioned and it doesn’t work for what I want it to do, it ends up both playing a note and sending a computer keystroke at the same time when I turn the jogwheel on my Ableton Move controller.
I wonder if the fact Ableton runs the midi controller through a remote script is somehow preventing supression of the midi messages sent from move when I try to convert them to a computer keystroke?
What are your input and output ports in Bome MIDI Translator Classic and in Ableton Live?
I anticipate Ableton Live is reading the MIDI message directly from your controller and you would need to use something like loopMIDI or loopBE for ports to be read by Ableton Live.
Steve Caldwell
Bome Customer Care
Thanks for the reply/help, I’ll check the ports when I get home but I did try making a loopmidi port, the moment I deselect move as a midi input source the pads go sark and it stops being able to control live nor does it detect Live sending it any messages. I’m sure I’m doing something wrong though as I’m not very well versed in how to work Live’s midi routing preferences
Okay, so I checked the settings and I think I know what the issue is. The Move controller does not send any MIDI messages to Live in the usual sense. Meaning when it’s connected via USB, Live is listening to it via a script customized for Move (I am unable to map any of Move’s knobs to anything in Live, they are default mapped by the script to the first 8 controls of any rack)
Yet somehow Bome unlike live is receiving regular midi note and CC messages from Move and converting them to computer keystrokes.
If I add a virtual midi port with loopmidi, now I can map the controller’s knobs to Ableton Live parameters, but the Move controller still simultaneously controls it’s automatic knob mappings (via the remote script) in addition to the parameter I mapped myself.
Here are the Ableton midi settings when there is no loopmidi port active:
And here they are when there is a loopmidi port active
Changing any of the menu items where ‘Move’ is written causes the controller to just disconnect
With all that in mind, I’m wondering if Bome Pro would even allow me to supress these control messages from Move without losing its functionality as a a well integrated control surface?
Hi, your control surface script in Live is showing Move Controller for input, If you want to read what is coming through Bome Classic, you will instead need to select the outgoing loopMIDI port you have selected as input in Live. In Bome Classic there is no way to suppress only some MIDI messages and routing is one way. You probably need to have a closer look at Bome MIDI Translator Pro.
Here is a comparison of features.
Steve Caldwell
Bome Customer Care
Thanks for the reply, I’ve tried this. The issues is the drop-down list are ‘control surfaces’ that control live through scripts, and not in the traditional midi messages sense. The moment I select only loopmidi as an input then the Ableton Move controller stops functioning as a custom control surfaces and becomes a ‘dumb’ midi controller. The drop-down menu items basically activate control scripts in live as far as I can tell, they are not quite traditional midi inputs. The controllers listed in that drop-down are presets for controllers and loopmidi is therefore not a selectable option
My question is would Bome midi translator pro do anything to circumvent that? My guess is it won’t? Because to have move as a control surfaces, live needs to see it connected as a ‘control surface’ input not as a traditional ‘midi in’, making me think no matter what I do it will send duplicate midi messages
The first column defines the control script you want to use. The second and third columns describe the MIDI input and output ports that you want to use. In order for a script to function correctly, the response from and MIDI messages to the controller need to be supported for that controller. There is no way in Bome Classic to have MIDI thru routes in both direction but you can do that with Bome MIDI Translator Pro as shown below. In this case I’m using Bome MIDI Translator Pro virtual ports (not available in classic) to talk to Ableton Live (the application).
My aliases (not available in classic) are set up as follows:
You can learn more about aliases from this tutorial.
So in this configuration and without translators as long as you select your controller definition in column 1 and BMT 1 for column 2 and 3, it should work.
Then you can add translators for custom MIDI messages to and from Ableton Live. You can use additional virtual ports if necessary and if not part of the controller definition, select them in the lower section of Ableton Live. In addition you can convert incoming MIDI from your controller to keystrokes as you initially requested. Each translator has a ‘Swallow’ option, if you don’t want the original MIDI message to go through.
In the below example, I’m using the second virtual port for custom control definitions.
Note, that Bome MIDI Translator Pro is always the middleman in communications between the controller and the application whether using MIDI thru paths or translators. Ableton Live never talks directly to the controller.
Since MT Classic has no virtual ports and no advanced MIDI routing and no swallow, it is much more limited in what you can do. You can still do simple transforms but if you still want to use your control script, it would not be sufficient for your needs.
I might add that you can download a free trial copy of Bome MIDI Translator Pro which is fully functional although times out every 20 minutes.
You can download a trial copy of Bome MIDI Translator Pro here.
I hope this helps!
Steve Caldwell
Bome Customer Care
Thanks so much for the clear explanation! 
Good to know it can function as the middleman with the midi messages, I guess it should work then. I’ll give the trial a try
So I don’t want to start a new whole new thread for this, but I was wondering if Bome Pro can send sysex messages to Ableton Move to change the LCD display’s writing?
