Hi, there are two possible approaches
1) Set up a MIDI Thru Path
2) Set up translators to pass through everything
Since I remember in your email request, you didn't want System Exclusive to go through the path. I will not discuss this option here and will focus on option number 2.
The oo pp letter pairs you refer to are local variables as describe in the user manual. By local it means that they can be used in any translator and only be visible to other translators with the same incoming trigger.
There are 10 of them available all with double letters the same.
oo pp qq rr ss tt uu vv ww xx
When you capture an incoming message with the value of oo for instance, that same value will be available for the outgoing message (unless you modify them with rules).
So an incoming trigger of oo pp qq (any 3 byte MIDI message) can trigger the same outgoing MIDI by simply putting oo pp qq raw output in the same translator.
In the attached project file I do this with 1 byte messages, 2 byte messages and 3 byte messages each as separate translators with a stop action on the translator so that there is no duplicate. If translator 1 sees a one byte message it will pass it on and evaluation of incoming messages stops until the next byte. For a 1 byte message, translator 1 ignores it (since it is more than 1 byte) and the second translator takes over, and so on.
These 3 messages account of about 90% of what most instruments use but does not account for System Exclusive (which you said in email that you didn't want) or MMC (Midi Machine Control). If need be we can add translators later to conver specific cases.
I set at the preset level "Linnistrument" as the input device and "Application" as the output device. These are aliases and on first open of the project you will be asked to assign them to the real MIDI ports. After that, if you need to reassign them again, this option is available in the MIDI menu.
At this point we do not address messages coming back from the application. I forget if there is some initial handshake that needs to be set up for MPE (Multi Polyphonic Expression) with the instrument. If this is required, we may need to add another preset with some translators to set up that initial "MPE handshake". I'll research MPE further and let you know while you try the project I provided. Not many people these days use MPE yet.
Just for grins, I set up a thru path from "Application" to "Linstrument" so that any messages coming from the applicaton to your instrument should make it through. I just don't know if answers in 1, 2 or 3 byte MIDI messages will cover the appropriate responses.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz