Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
multi_channel_midi_processing_setup_in_audiobus [2020/03/05 20:05] – WIP update, upload of images _ki | multi_channel_midi_processing_setup_in_audiobus [2020/03/06 19:10] (current) – Updating the text- stlll WIP _ki | ||
---|---|---|---|
Line 11: | Line 11: | ||
This is a short tutorial on how to setup multi-channel-midi processing in AudioBus | This is a short tutorial on how to setup multi-channel-midi processing in AudioBus | ||
- | ===== Initial | + | ===== The Goal: Multi-Channel-Midi Processing |
- | 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. | + | |
- | {{ab_mcm_02b_audio_.jpg? | + | 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. |
- | ===== Multi-Channel-Midi processingSetup ==== | + | 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, | ||
+ | * permutation of assigned instruments (bass or melody played by other sounds) | ||
+ | from a single plugin (or even chains of multi-channel-midi processing plugins). | ||
- | In a multi-channel-midi processing setup, you want to route all generted midi through | + | The resulting, modified midi stream leaving the multi-channel-midi processing plugin |
- | a single | + | |
- | route the resulting, modified midi streams to the receivers in such a way, that each | + | |
- | receiver only listens | + | |
This is realized by means of the 16 Midi channels. | This is realized by means of the 16 Midi channels. | ||
- | * Each Midi generator transmits on a different | + | * Each Midi generator transmits on a different |
* Each synth/drum receives only the Midi data of the channels it is intended for | * 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? | ||
+ | |||
+ | \\ | ||
=== Step-by-Step using Streambyter === | === Step-by-Step using Streambyter === |