Repository navigation
Expand file tree
/
Copy pathChapter-005-Process-Routing.qmd
More file actions
124 lines (108 loc) · 6.64 KB
/
Copy pathChapter-005-Process-Routing.qmd
File metadata and controls
124 lines (108 loc) · 6.64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
---
editor:
markdown:
wrap: 72
---
# Process - Routing MIDI and Audio {#Chapter-005-Process-Routing}
In the spirit of the “Lazy Producer,” I like to reuse a single MIDI or
audio input across multiple tracks, each with its own chain of effects.
The benefit of this is that the tracks which reuse the same input are
related to the original in pitch but with different timbre if they use
different synth sounds, or have different audio effects applied. In
Ableton Live, it’s easy to route one track into another. You can either
“push” the output of a source track to a destination or have the
destination track “pull” the input from the source.
::: callout-tip
## Key idea
Reusing MIDI or audio tracks across many channels ensures that the
different tracks are related in their input source, even if additional
MIDI or audio effects are applied. This provides coherence between the
different sounds and tracks—the "predictable" part of our "predictable
vs. unexpected" balancing act. This helps the listener hear the sounds
as coming from the same "family" even if the actual sounds in each track
are different. Exploiting this it’s possible to layer tracks that are
almost guaranteed to work well together using different sound sources,
timbres, even pitches (if using MIDI input) or resonances (if using
Audio input).
:::
In Ableton Live [we have a couple of ways to either "push" or "pull"
MIDI or audio from one track into
another](https://www.ableton.com/en/live-manual/11/routing-and-i-o/#routing-and-io).
In the image below, MIDI received by Track 1 is "pushed" (via MIDI To
choices) to Track 2 which contains an instance of Operator. The second
box below the MIDI Track specifies that the MIDI is to be sent to the
input of the first MIDI device in this track - the Operator instrument
in this case. You don't ***have*** to have this specified, but in this
case it means that the Monitor setting in Track 2 can be left on "Auto".
You can also route the input to a specific device in an instrument rack.
You can use this approach to send MIDI from multiple MIDI tracks to
***the same device***. For example if you have separate MIDI patterns
for Kick, Snare and High-hat these can be sent to the same instrument
track containing a Drum Rack. This can be useful if you want to apply
MIDI effects, randomness, Follow Actions or modulation to the high-hat
but not the kick.
The third MIDI track here is "pulling" the MIDI from Track 1. Note that
the Monitor is set to "In" so that it "listens" for the MIDI being sent.
In this case I can add a MIDI device like Note Length to "stretch" the
incoming MIDI and then apply an Arpeggiator to that to produce new
moving parts that are related to the sequence in Track 1, but different.
The fourth track (Audio) here is "pulling" the audio from Track 3
(Wavetable). Similar to Track 3, it needs the Monitor set to "In" to
"listen" for the audio output. In this track we're also showing the
various options for where to grab audio - it can be "Pre FX", "Post FX"
or "Post Mixer". "Pre FX" means that the audio is grabbed by the track
before it goes through any audio processing on the input track. This
means you can apply different effects to the same raw audio source -
some on Track 3 and some via Track 4. "Post FX" means that it grabs
audio after effects have been applied. "Post Mixer" means that track
volumes and panning are applied prior to grabbing the audio. "Post
Mixer" might be handy if you wish to control levels from only one track.
You can also route audio from tracks into other audio tracks in order to
create submix tracks. Typically I use Grouped tracks to achieve
something like this, but submix for different track types - pads, drums,
bass etc. might help in mixdown.
In MIDI tracks the "Pre FX" and "Post FX" apply to MIDI effects as well,
so you can grab MIDI inputs either before MIDI effects are applied, or
afterwards. Since Ableton's track routing works this way consistently,
it's possible to add intermediate MIDI tracks with no instruments, but
"listening" to the MIDI output at a particular state ("Pre" or "Post" FX
on the source track) and then have additional tracks that exploit the
intermediate track. This flexibility and ease of routing is a massive
bonus for The Lazy Producer. It's possible to reuse inputs across
multiple tracks in multiple ways to do a huge range with them. In
particular I use this technique to build texture, especially in "drone"
tracks where I can apply different resonators, textural effects to audio
inputs from the same source.
While you could achieve a similar result using Instrument or Effect
Racks on a single track (see
<https://www.ableton.com/en/live-manual/12/instrument-drum-and-effect-racks>),
the multi-track approach has a key benefit: each track gets its own send
controls for routing to return effects. It also makes live performance
somewhat easier since you can quickly see the levels of each track and
control these via a MIDI controller device like Ableton Push.
```{r}
#| echo: FALSE
knitr::opts_chunk$set(echo = FALSE)
```
```{r}
#| fit-alt: "Image shows the routing of MIDI notes between a generator track on the left and four other tracks. The generator track is routing MIDI to the operator instrument in track 2. Track 3 is pulling MIDI information from the generator track in position 1 so the Monitor button is switched to In. The fourth track is taking audio from the Wavetable instrument track but selecting that audio post mixer. The fifth track is recording audio from an external device, but monitor is set to off."
knitr::include_graphics(path = file.path(here::here(), "images", "Routing.png"))
```
## Splitting MIDI for a single instrument across tracks
As we discussed in [Process - Note-wise
probability](#Chapter-002-Process-Note_wise_probability) it's possible
to use multiple MIDI tracks that send MIDI to a single instrument. This
might be useful to split repeating and random parts, so that you can
apply MIDI effects to the "random" part while keeping the repeating part
static.
A similar technique might be used to have distinct MIDI parts for a Drum
Rack, so you can keep certain parts "locked in" and repeating, while
other parts have additional MIDI processing and add flavour to the part.
Even within that framework you could have a repeating kick and snare
part, but add additional snare fills, flams or lower velocity random
hits to add variation and spice to the snare part.
The flexibility and ease of routing audio and MIDI around in Live makes
it a very versatile platform for creating complex signal paths, and
apply different effects and modulation at a variety of points both
before the MIDI information is used by an instrument, and after the
audio is creating via the instrument and effects.