8. Form

I. Making music

Form

A loop of four bars is an idea; a song is what happens to it over three minutes. Form is that: the song's sections, how long each runs, and what changes from one to the next. This chapter lays out sections, counts the changes between them as the studio's coach does, reads the song's energy from section to section, and joins sections with transitions.

zig build run-studio -- manual/08-form/two-loop

Sections

The band under the ruler holds the song's sections, each from its bar to the next one's. A double-click on the band adds a section on the nearest bar, or names the one starting there anew; a click selects a section and sets the locators across it, so cycle loops it and range edits act on it; a drag on its start moves it; and remove section, in the menu a right-click on it opens, takes its name away. Sections hold nothing: they say what the bars are.

Most songs are built from a handful of section kinds. A verse tells the story and changes its words each time; a chorus repeats, and is the part people remember; a bridge comes once, late, and goes somewhere new; an intro and an outro open and close. Club music thinks in builds, breakdowns, and drops, and a hip-hop song in verses and hooks.

A right-click on the band where it holds no section, before the first or past the song's end, opens the band's menu, and its lay out a form drops a list of forms; sections ▾ over the track list holds it too. Each form lays sections over the bars from there, names and lengths:

Form Sections, in bars
two-loop A 8, B 8, C 8, D 8
pop intro 4, verse 8, chorus 8, verse 8, chorus 8, bridge 8, chorus 8, chorus 8, outro 4
AABA A 8, A 8, B 8, A 8
club intro 16, build 16, breakdown 16, drop 32, break 16, drop 32, outro 16
hip-hop intro 4, verse 16, hook 8, verse 16, hook 8, verse 16, hook 8, outro 4

Shift+Enter on a form, or Shift and a click, also copies the first section's bars into every new one, so the whole song is full from the start, and arranging it is taking things away. Dennis DeSantis's Making Music calls this arranging as a subtractive process: start with everything, and take away what each section doesn't need.

The two-loop rule

How much should change from one section to the next? Alex Rome's video An Insanely Simple Arrangement System, which builds a deep house track from one loop, gives a rule of thumb: two changes a section. Add an instrument, take one away, or add or take away expression, such as a filter opening, twice at each boundary. One change is too little to hear as a new section; four or more starts to sound like another song. The studio's example studio/examples/two-loop/build.txt builds his song in the window.

The studio's coach counts. After each section's name on the band it writes its verdict, a check ✓ for enough change, a ring ○ same for none, and ! for a lot, then what starts, +bass, what stops, −kick, and what changes on a track that plays on both sides, drums~. A track counts once, however much changes on it.

Twenty bars in five sections over one loop of chords. The coach checks two changes at each of the first three boundaries, `+hats +stabs`, `−kick +pad`, and `+kick +lead`, and draws a ring at the last, where nothing changes.: the arrange

0.0 / 39.3 s

peak -8.7 dBFS

Fig. 8.1 Twenty bars in five sections over one loop of chords. The coach checks two changes at each of the first three boundaries, +hats +stabs, −kick +pad, and +kick +lead, and draws a ring at the last, where nothing changes.

openzig build run-studio -- manual/08-form/two-loop

renderzig build run-studio -- render manual/08-form/two-loop two-loop.wav

two-loop/song.json
{
  "tempo": 122,
  "end": "21",
  "sections": ["1 A", "5 B", "9 C", "13 D", "17 E"],
  "key": ["1 A minor"],
  "chords": ["1 Am7", "2 Dm7", "3 Fmaj7", "4 Em7", "5 Am7", "6 Dm7", "7 Fmaj7", "8 Em7", "9 Am7", "10 Dm7", "11 Fmaj7", "12 Em7", "13 Am7", "14 Dm7", "15 Fmaj7", "16 Em7", "17 Am7", "18 Dm7", "19 Fmaj7", "20 Em7"],
  "devices": [
    { "name": "synth", "type": "synth", "state": { "parts": [
      { "patch": "A72", "level": -6, "reverb_send": 20 },
      { "patch": "A51", "level": -4 },
      { "patch": "A61", "level": -8, "delay_send": 20 },
      { "patch": "A31", "level": -12, "reverb_send": 30 }
    ] } },
    { "name": "808", "type": "drums" }
  ],
  "tracks": [
    { "name": "kick", "device": "808", "channel": 1, "role": "drums", "clips": [{ "at": "1", "length": "8.0.0", "notes": "kick" }, { "at": "13", "length": "8.0.0", "notes": "kick" }] },
    { "name": "hats", "device": "808", "channel": 1, "role": "drums", "clips": [{ "at": "5", "length": "16.0.0", "notes": "hats" }] },
    { "name": "bass", "device": "synth", "channel": 2, "keys": "pent", "role": "bass", "clips": [{ "at": "1", "length": "20.0.0", "notes": "bass" }] },
    { "name": "stabs", "device": "synth", "channel": 1, "keys": "chord 7", "role": "chords", "clips": [{ "at": "5", "length": "16.0.0", "notes": "stabs" }] },
    { "name": "pad", "device": "synth", "channel": 4, "keys": "chord 7", "role": "pad", "clips": [{ "at": "9", "length": "12.0.0", "notes": "pad" }] },
    { "name": "lead", "device": "synth", "channel": 3, "keys": "pent", "role": "lead", "clips": [{ "at": "13", "length": "8.0.0", "notes": "lead" }] }
  ],
  "notes": {
    "kick": {
      "length": "1.0.0",
      "notes": [
        "1.1.0 C2 0.0.240 120", "1.2.0 C2 0.0.240 112", "1.2.0 D#2 0.0.240 96",
        "1.3.0 C2 0.0.240 116", "1.4.0 C2 0.0.240 112", "1.4.0 D#2 0.0.240 96"
      ]
    },
    "hats": {
      "length": "1.0.0",
      "notes": [
        "1.1.240 F#2 0.0.120 52", "1.1.480 A#2 0.0.240 80", "1.2.240 F#2 0.0.120 52", "1.2.480 A#2 0.0.240 76",
        "1.3.240 F#2 0.0.120 52", "1.3.480 A#2 0.0.240 80", "1.4.240 F#2 0.0.120 52", "1.4.480 A#2 0.0.240 76"
      ]
    },
    "bass": { "length": "20.0.0", "follow": { "pattern": "offbeat", "low": "E1" } },
    "stabs": { "length": "16.0.0", "follow": { "pattern": "stabs", "low": "F3" } },
    "pad": { "length": "12.0.0", "follow": { "pattern": "whole", "low": "F3" } },
    "lead": {
      "length": "4.0.0",
      "notes": [
        "1.1.0 E5 0.0.900 100", "1.2.0 D5 0.0.420 90", "1.2.480 C5 0.0.420 90", "1.3.0 A4 0.1.900 96",
        "2.1.0 C5 0.0.900 96", "2.2.0 D5 0.0.420 90", "2.2.480 C5 0.0.420 88", "2.3.0 A4 0.1.900 94",
        "3.1.0 C5 0.0.900 96", "3.2.0 E5 0.0.900 92", "3.3.0 G5 0.1.900 98", "4.1.0 E5 0.0.900 96",
        "4.2.0 D5 0.0.420 90", "4.2.480 E5 0.0.420 90", "4.3.0 G4 0.1.900 94"
      ]
    }
  }
}

Read the band left to right and the song's story is there: the kick and the bass alone, then the hats and the stabs come in; the kick drops out and a pad swells for a breakdown; the kick comes back with the lead for the peak. Section E plays the same as D, and the coach draws a ring, ○ same: the hint over it says Nothing changes here: the two-loop rule asks for two changes a section. Four or more changes draw a !, and the hint says A lot changes at once; the rule is the walkthrough's, not a law. It isn't one: a verse going into a chorus may want more, and a long club track changes less.

Energy

Along each section's foot runs a thin bar, as long as the section has energy: how many tracks play there, and how busy their notes are. Down the song, the bars rise and fall, and the shape of the whole song reads at a glance, its build, its breakdown, and its peak. In the figure, A is the shortest, B and C about equal, and D and E the longest.

The coach warns about two ways parts get in each other's way, at the right end of a section:

  • low end crowded: two tracks both hold notes under E2 for a quarter of the section. The hint names them, as bass and pad both play below E2: move one up, or raise its hpf. Two low parts at once turn to mud.
  • lead inside the chords: the lead's notes all sit within the chords' range, so it's buried among them. The hint suggests moving it up to stand out.

Transitions

The moment between sections is where a song is most likely to sound pasted together, and a transition smooths it. A boundary has a small mark at the band's foot. A click on it sets the locators two bars either side of the boundary, turns cycle on, and drops a list of transitions; Up and Down try each one across the boundary as the song loops there, and Enter writes it as one edit:

Transition Writes
fill The drum machine's fill in the bar before, as a pattern clip, or a snare fill as notes
build A cutoff rising over the two bars before on the chords, and a snare roll into the boundary
drop out The kick's and the bass's clips cut a bar before, so the boundary lands harder
crash A cymbal on the boundary's first beat
stop Everything but the drums silent for the last beat

Alt and a click on the mark, or check the transition in the section's menu, checks a boundary without changing it: the locators go two bars either side, cycle turns on, and the song plays across it.

What `fill` and `crash` write at a verse going into a chorus: the drum machine's fill, `2-F1A`, in the bar before, and a cymbal clip on the chorus's first beat, over its beat. The coach counts `drums~ bass~ +stabs` at the boundary.: the arrange

0.0 / 7.9 s

peak -12.4 dBFS

Fig. 8.2 What fill and crash write at a verse going into a chorus: the drum machine's fill, 2-F1A, in the bar before, and a cymbal clip on the chorus's first beat, over its beat. The coach counts drums~ bass~ +stabs at the boundary.

openzig build run-studio -- manual/08-form/fill

renderzig build run-studio -- render manual/08-form/fill fill.wav

fill/song.json
{
  "tempo": 122,
  "end": "5",
  "sections": ["1 verse", "3 chorus"],
  "key": ["1 A minor"],
  "chords": ["1 Am7", "2 Dm7", "3 Fmaj7", "4 Em7"],
  "devices": [
    { "name": "synth", "type": "synth", "state": { "parts": [
      { "patch": "A72", "level": -6, "reverb_send": 20 },
      { "patch": "A51", "level": -4 }
    ] } },
    { "name": "808", "type": "drums", "state": { "program": "2-1A" } }
  ],
  "tracks": [
    { "name": "drums", "device": "808", "channel": 1, "role": "drums", "clips": [
      { "at": "1", "length": "1.0.0", "pattern": "2-1A" },
      { "at": "2", "length": "1.0.0", "pattern": "2-F1A" },
      { "at": "3", "length": "2.0.0", "pattern": "2-1A" },
      { "at": "3", "length": "0.1.0", "notes": "crash" }
    ] },
    { "name": "bass", "device": "synth", "channel": 2, "keys": "pent", "role": "bass", "clips": [{ "at": "1", "length": "4.0.0", "notes": "bass" }] },
    { "name": "stabs", "device": "synth", "channel": 1, "keys": "chord 7", "role": "chords", "clips": [{ "at": "3", "length": "2.0.0", "notes": "stabs" }] }
  ],
  "notes": {
    "crash": { "length": "0.1.0", "notes": ["1.1.0 C#3 0.1.0 112"] },
    "bass": { "length": "4.0.0", "follow": { "pattern": "offbeat", "low": "E1" } },
    "stabs": { "length": "2.0.0", "follow": { "pattern": "stabs", "low": "F3" } }
  }
}

A transition writes ordinary clips, which you can move, change, or delete: here the fill is a pattern clip of the rhythm's group, and the crash a notes clip a beat long. The bass counts as a change too: it follows the chords, and the chorus starts on other chords than the verse.

Try it in the window

  • In the two-loop song, mute the stabs and watch the coach's count at B drop to one. Unmute them.
  • Click the mark at the foot of the boundary into D, play, and step through the transitions with Up and Down, listening to each.
  • Start a new song from the pop template, Ctrl+N and pop, and read the coach's counts along its sections: what would you add or take away?
  • Make an eight-bar loop without sections, right-click the band at bar 1, choose lay out a form, and Shift-click the two-loop form: four sections of the same eight bars. Then arrange it by muting and deleting, two changes a section.
  • Rest the pointer on a boundary's changes, and read the details.

Next: chapter 9, recreating, learning from songs you like.