Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| midi_routing_for_multi_input_processing [2019/07/11 02:56] – _ki | midi_routing_for_multi_input_processing [2019/11/24 08:03] – Unified tags _ki | ||
|---|---|---|---|
| Line 36: | Line 36: | ||
| 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. | ||
| - | Here are two sample script to force incomming events onto a specific output channel | ||
| + | Here are three solutions to force incomming events onto a specific output channel | ||
| + | |||
| + | ** Midi Tools:** | ||
| + | Use the included ‚Midi Clone and Filter‘ plugin | ||
| + | | ||
| ** 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 | ||
| Line 47: | Line 51: | ||
| @End | @End | ||
| - | {{tag>[au_midi | + | {{tag>[au_midi_fx |
_ki