Differences

This shows you the differences between two versions of the page.

--- multi_channel_midi_processing_setup_in_audiobus [2020/03/05 18:28] – Hide tag for this stub _ki
+++ multi_channel_midi_processing_setup_in_audiobus [2020/03/06 19:10] (current) – Updating the text- stlll WIP _ki
@@ Line 1: / Line 1: @@
+===== Work In Progress =====
+~~NOTOC~~ {x{tag>[audiobus au_midi_fx au_midi_routing midi midi_router tips_and_tricks}}
+\\
+The tags line is visible because i've added a syntax eror so that this page isn't yet linked to the rest of the wiki.
+.
 ======Multi-Channel-Midi Processing Setup in AudioBus ======
-~~NOTOC~~ {x{tag>[au_midi_fx au_midi_routing midi midi_router tips_and_tricks}}
+This is a short tutorial on how to setup multi-channel-midi processing in AudioBus
+===== The Goal: Multi-Channel-Midi Processing Setup ====
+In a multi-channel-midi processing setup, you want to route all generated midi through a single midi processing plugin to affect all of the midi streams at once.
+This results in full control over the running session for
+  * song staging, the constantly looping patterns of the Midi generators can be combined to song sections by muting individual patterns
+  * variations of individual tracks (note-volume, dropping of notes, transpositio, humanizing)
+  * permutation of assigned instruments (bass or melody played by other sounds)
+from a single plugin (or even chains of multi-channel-midi processing plugins).
+The resulting, modified midi stream leaving the multi-channel-midi processing plugin is picked up by all receiving instruments, therefore each of the instruments has to filter this stream for its assigned midi source.
+This is realized by means of the 16 Midi channels.
+  * Each Midi generator transmits on a different midi channel
+  * Each synth/drum receives only the Midi data of the channels it is intended for
+===== Initial Setup ====
+In this example, the initial session consists of 5 synth and a EG Pulse for drums,
+and some effects.
+On ABs Midi page it can be seen that each of them is driven by a
+midi generator. There is no special setup of midi channels needed in the generators
+or instruments as its a one-to-one connection.
+{{ab_mcm_02b_audio_.jpg?direct&450}} {{ab_mcm_01_initial.jpg?direct&450}}
+\\
+=== Step-by-Step using Streambyter ===
+{{ab_mcm_03_sb.jpg?direct&450}}
+{{ab_mcm_05_filter.jpg?direct&450}}
+{{ab_mcm_04_send.jpg?direct&450}}
+=== Solution using Mozaic ====
+{{ab_mcm_07_moz_filter.jpg?direct&450}}
+{{ab_mcm_08_moz_filter.jpg?direct&450}}
+{{ab_mcm_09_moz_filter.jpg?direct&450}}
+{{ab_mcm_10_filter.jpg?direct&450}}
+Typical processing script:
+{{ab_mcm_11_mutator.jpg?direct&450}}
+=== List of Multi-Channel-Midi Processing Scripts ===
+| Midi Matrix Switch | Permutate channel assignment to change sounds and add variations |
+| ToggleChannels On Bar Divisions | Channel mutes/unmutes in sync with the host session |
+| CopyCat | Replicate midi with applied mutations to other channels |
+| MutatoR | Channel mutes, note-drop probability, static and random transpose, static and random velocity modification in 64 user-configs |
+| Ayo DJ | Automatic channel mutes to generate procedural sessions |