I’ve got a Mackie MCU Pro Controller I’d like to use with Studio One. I would like to be able to overlay multiple functions on each button depending on what modifier buttons are depressed (eg Shift, Option, Control, Alt) when the button is pressed.
I can use a BMT translator to set a global variable g1 through g4 for each of these modifiers, and set to 1 if the button is pressed, and 0 if not.
What I would then like the ability to do is within the Rules section, check these flags when a button is pressed, and then set a local variable to the appropriate keycode I’d like to send to Studio One, and then in the Outgoing action, have this keycode sent to Studio one. For maximum flexibility, it would be nice to have these variables be able to be send as keycodes, text, or MIDI messages.
SJC> This can be easily done, if you have a specific example, I can show you how. For MIDI messages you can send raw MIDI in a single translator. For text or keycodes, each keystroke or text message will require a separate translator but you cannot use variables as MT Pro only uses integer variables and not strings or text variables. This is something that has been requested and is planned for a future release.
I think this feature would be a powerful addition to the Bome program.
SJC> I agree
An additional useful feature would be able to concatenate keystrokes or MIDI messages in string variables, and have these sent as keystrokes, text or midi message. It would also be useful to be able to do mathematical conversion from a numeric variable to an ascii character. This would make it much easier to program. I would only then need a single translator to convert a MIDI sequence to a keyboard character, without having to create a separate translator for each keystroke that you require. Given I have 48 buttons I’d like to program with up to 5 modifiers each — that would make for 240 translators which I expect would cause some performance problems.
SJC> Although as I said, conversion from numeric to ASCII character is not yet supported, there are ways we can handle some of this today. Keystrokes on PC or Mac are not ASCII, yet combinations of scan codes. However, if you application support serial data, we can send as ASCII strings with embedded variables to represent supported ASCII characters. I have written a set of translators to convert a single global variable value into a series of keystrokes to represent the variable. For instance, the value of 100 I can use rules and timers to send out "1" "0" "0" as keystrokes.
Also, we can reduce the number of variables required by "bit mapping" them. For instance a single global variable is a 32 bit signed integer so as such we can track the up/down position of up to 32 buttons with a single global variable.
If you have a specific example of what you want, I can put something together and post it here.
I've done many projects that convert Mackie MCU or Mackie HUI to generic MIDI messages and a few that have converted to keystrokes, so I'd be surprised to find many restrictions in what can be done, albeit a little more difficult not having string variables. With that said, Studio One does in general recognize generic MIDI so it is more reliable if we can translate to MIDI messages that Studio One supports rather than keystrokes, whenever possible.
Bome Customer Care
Also available for paid consulting services: email@example.com