Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revisionBoth sides next revision | ||
midi_routing_for_multi_input_processing [2020/02/14 03:04] – Added midi and midi_router tags _ki | midi_routing_for_multi_input_processing [2020/03/05 06:24] – Updated title and added more text to solutions _ki | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Midi routing for multi midi input processing plugins ====== | + | ====== Midi routing for Multi-Channel-Midi |
===== Standard routing ===== | ===== Standard routing ===== | ||
Line 26: | Line 26: | ||
. | . | ||
- | ====== Some problems | + | ===== Some problems ===== |
- | Everything working now ? Mostly - there are some tiny problems with the above solutions: | + | Everything working now ? Mostly - there are some tiny problems with the above solution: |
- | * There are midi generators that don't allow to specify the output channel | + | |
- | * There are midi generators that have a setting for the output channel, but don't statesave it - so every time when reloading the sesssion one has to setup the output channel again | + | |
+ | * There are midi generators that have a setting for the output channel, but don't statesave it - so every time when reloading the sesssion one has to setup the output channel again | ||
+ | * The [[midi_au_output_channel|midi au output channel wiki page]] summarizes all midi generating plugins regarding their ability to specify the midi output channel and state save this value. | ||
- | The [[midi_au_output_channel|midi au output channel wiki page]] summarizes all midi generating | + | * Routing the midi |
+ | * Some hosts lack complex midi routing and only support | ||
+ | |||
+ | * Input channel filter on the instrument side | ||
+ | * There are host that don't offer a midi input filter for their instrument slots | ||
===== and work-arounds ===== | ===== and work-arounds ===== | ||
+ | There are solutions for all of the above problems | ||
+ | |||
+ | \\ | ||
+ | === Set Output Channel === | ||
If a generator plugin by itself wont't change channel, or forgets its channel settings one can allways insert a midi channel modifying plugin into the connection between the problematic generator and the multi midi input processing plugins forcing everything onto a specifiy channel. | If a generator plugin by itself wont't change channel, or forgets its channel settings one can allways insert a midi channel modifying plugin into the connection between the problematic generator and the multi midi input processing plugins forcing everything onto a specifiy channel. | ||
+ | * **Midi Tools:** Use the included ‚Midi Clone and Filter‘ plugin | ||
+ | * **StreamByter: | ||
+ | * **Mozaic:** [[https:// | ||
+ | |||
+ | \\ | ||
+ | === Host without midi matrix | ||
+ | |||
+ | * **Mozaic:** RadioMidi Transmitter and RadioMidi Receiver scripts | ||
+ | |||
+ | \\ | ||
+ | === Apply Input Channel Filter | ||
- | Here are three solutions to force incomming events onto a specific output channel | + | * **StreamByter: |
+ | * **Mozaic:** [[https:// | ||
- | ** Midi Tools:** | ||
- | Use the included ‚Midi Clone and Filter‘ plugin | ||
- | | ||
- | ** StreamByter scripting: | ||
- | XX = X4 # Use (output channel -1) and for XA <> 11, XB <> 12, XC <> 13 .. XF <> 16 | ||
- | **Mozaic scripting engine:** | ||
- | @OnMidiInput | ||
- | outputTo = 5 | ||
- | SendMIDIOut MIDICommand+(outputTo-1), | ||
- | @End | ||
- | {{tag> | + | {{tag> |