Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revisionBoth sides next revision | ||
| midi_routing_for_multi_input_processing [2019/07/08 16:13] – created _ki | midi_routing_for_multi_input_processing [2019/07/08 16:38] – _ki | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Midi routing for multi input midi processing plugins ====== | + | ====== Midi routing for multi midi input processing plugins ====== |
| ===== Standard routing ===== | ===== Standard routing ===== | ||
| Line 14: | Line 14: | ||
| Furthermore since most generators default to send on midi channel one (drum type generators on channel ten) the processing plugin can't even distinguish where a note or midi event came from. | Furthermore since most generators default to send on midi channel one (drum type generators on channel ten) the processing plugin can't even distinguish where a note or midi event came from. | ||
| - | {{ : | + | {{ : |
| . | . | ||
| Line 31: | Line 31: | ||
| * 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. | ||
| ===== and work-arounds ===== | ===== and work-arounds ===== | ||
| Line 38: | Line 39: | ||
| ** StreamByter scripting: | ** StreamByter scripting: | ||
| - | XX = X4 # Use output channel -1 and for XA <> 11, XB <> 12, XC <> 13 .. XF <> 16 | + | XX = X4 # Use (output channel -1) and for XA <> 11, XB <> 12, XC <> 13 .. XF <> 16 |
| **Mozaic scripting engine:** | **Mozaic scripting engine:** | ||
_ki