Simplify or consolidate many translators into fewer

[SteveC (Steve)]

@Mathias.Wulff

in the rules section, the prefix “0x” simply tells BMT to treat as hex instead of decimal? While raw midi used in the incoming/outgoing sections are always hex?

Correct. Also if you enter 0x40 in the rules, if you come back to after saving it will show in decimal (64).

@Mathias.Wulff

how can rr be oo AND 0x0f? Or what does that assignment do?

oo and rr are both local variables, you are setting the value of rr to the value of oo AND 0x0f. This is a bitwise operation. So if oo is 0x95 after the operation rr will be 5.

@Mathias.Wulff

I assume you’re refering to setting oo pp qq as the incoming raw midi message to all 3 byte midi messages? And similarly, oo pp would catch ass 2 byte messages, but not any part of 3 byte messages?

Correct. Bome MIDI Translator is smart enough to know when the MIDI message ends.

@Mathias.Wulff

can you do an example of bitwise manipulation that allows more values to be stored in a single variable? Ie., how to “put them into” the variable and “pull them out again”…

See this post.

@Mathias.Wulff

sometimes I will need to 8x the midi message (send the same incoming midi out to 8 channels). Is there a good way to handle that inside one translator? (Maybe if there’s a way to “empty” variables, so that, say, “oo pp qq rr ss tt” would output nothing if all the variables are empty, or one 3 byte midi message if “rr ss tt” are empty, and finally two 3 byte midi messages if all 6 variables are defined.)

Use a repeating timer and global variables. In the timer, iterate through the number of times you want to output your message changing the values on each iteration. I think there is a good example somewhere in this forum when I do this to control the APC-MINI’s 64 LEDs. Search on ‘APC-MINI’

@Mathias.Wulff

Thanks, I’m learning a lot here!

BMT and the BomeBox are just great inventions

Steve Caldwell
Bome Customer Care

---

Also available for paid consulting services: bome@sniz.biz