Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
midi_routing_for_multi_input_processing [2019/07/11 02:56] – _ki | midi_routing_for_multi_input_processing [2020/03/05 07:27] – Minor update _ki | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Midi routing for multi midi input processing plugins ====== | + | ====== Midi routing for multi-channel-midi processing plugins ====== |
+ | ~~NOTOC~~ {{tag> | ||
+ | |||
+ | **Table of Contents: | ||
+ | * [[#Standard routing]] | ||
+ | * [[#Naive approach]] | ||
+ | * [[#Working solution]] | ||
+ | * [[# | ||
===== Standard routing ===== | ===== Standard routing ===== | ||
Line 9: | Line 16: | ||
. | . | ||
- | ===== Naive approach | + | ==== Naive approach ==== |
If midi processing plugins are involved that take multiple instruments as input, one might think that one could simply route all generators to the plugin and let all instruments read from the plugin. But then all instruments would play the notes of all generators as that is the output of the processing plugin. | If midi processing plugins are involved that take multiple instruments as input, one might think that one could simply route all generators to the plugin and let all instruments read from the plugin. But then all instruments would play the notes of all generators as that is the output of the processing plugin. | ||
Line 26: | Line 33: | ||
. | . | ||
- | ====== | + | ===== Work-arounds for problem cases ===== |
- | Everything working now ? Mostly - there are some tiny problems with the above solutions: | + | |
- | * There are midi generators that don' | + | === Set 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 | + | If a generator plugin by itself wont' |
+ | |||
+ | * **Midi Tools:** Use the included ‚Midi Clone and Filter‘ plugin | ||
+ | * **[[StreamByter]]** script: [[streambyter_force_channel|Force Channel with GUI]] | ||
+ | * **[[mozaic_plugin_engine|Mozaic]]: | ||
- | 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 | + | \\ |
+ | === Host without midi matrix | ||
+ | If a hosts lack complex midi routing and only support midi plugins for a single track/slot, there is a pair of Mozaic scripts for host-wide midi transmission. | ||
+ | * **[[mozaic_plugin_engine|Mozaic]]** script: RadioMidi Transmitter | ||
- | ===== and work-arounds ===== | + | \\ |
- | If a generator plugin by itself wont' | + | === Apply Input Channel Filter |
+ | If a host doesn' | ||
+ | * **[[StreamByter]]** script: [[streambyter_channel_filter|Channel Filter with GUI]] | ||
+ | * **[[mozaic_plugin_engine|Mozaic]]** script: [[https:// | ||
- | Here are two sample script to force incomming events onto a specific output channel | ||
- | ** 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> |