OK, I gave you some examples.
The strategy here is to take any 2 character or 3 character MIDI message. One character MIDI messages do not contain channel information
I have a different preset for each port routing. Port routing overrides project defaults at the preset leve. The rules in each translator look at the incoming MIDI channel and if necessary modify the outgoing MIDI channel before passing it on. Since each preset defines only specific ports, port routing is maintained per preset and channel routing is maintained via rules.
I also have 2 translators with incoming but with "None" as outgoing. These may not be necessary, however if you add any static routing (which I have not), then these will be necessary to ensure that "Swallow" works for 2 character and 3 character MIDI messages that "exit rules, skip outgoing action".
You may want to add some translators for on character timing or active sensing messages for whatever devices you want to send these to.
Since SysEx is not channel specific, you may also want to add some static routes for those to get through. If you want to modify the content of specific SysEx messages, you may want to add translators for those.
You can indeed also convert CC to NRPN and if you do that, you want to add translators to those.
The important thing is to create presets for all port routing you want and then put translators for those routings under the appropriate port routing.
I created alias names for all of the ports (but not MIDI Channels) so hopefully if you move things to different DIN ports etc, you can just re-assign the aliases.
Port names are:
Fantom8-Input Port 1
Fantom8 -Input Port 2
Fantom8 -Output Port 1
Fantom 8 - Output Port 2
Keys 1 Input
Keys 1 Output
Keys 2 Input
Keys 2 Output
Keys 3 Input
Keys 3 Output
Roland Integra-7 (which is output only)
Physis Piano (output only)
GUITAR/PRC (output only)
Roland TR-8s (output only)
Out11- Effects (output only)
SQ5-In
SQ5-Out
Of course, you can rename the aliases to anything you like as long as it makes sense to you. The aliases are primarily there for portability between PC and BomeBox.
When you first open the file in MT Pro, you will be prompted for the aliases. Once you set them up, they will be remembered.
This way you can test with aliases on your PC. Then if you move everything to BomeBox. You can re-assign aliases there as well (which will then be remembered on your BomeBox).
As mentioned earlier, it is best to get everything working on your PC first in the project file, then transfer to you BomeBox for execution.
Again, I didn't do your whole project for you. Just some examples to get you started.
I also commented the rules, so hopefully you can see what I did.
Let me know if you have any questions.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz