#7 in a series of posts about the tracks on my latest album, Small Things.
Heck yeah. I really love this track, false modesty be damned. It’s one that I had finished before Also came out, but I didn’t find a home for it there.
The big chords
This is where the track began. My memory is it followed on from being really happy with a track of mine, ‘Not On The Cards Anymore‘, where there was a lot of space between events, and quiet chords slowly creeping up on you as the track progresses. I knew early on when I was working with these very ON/OFF slabs of sound that I wanted the track to start straight in like that, no other intro.
There’s three layers here, really.
The shorter stabs:
The very quiet pads:
The big, echo-y bass note:
The harmony
We’re in C# Phrygian mode, that mode I used in ‘Trellis‘ that’s like a typical minor scale but with a flattened second. We’re almost entirely sitting on a C#m7 chord, just once every 2 bars. But at the end of the 8-bar loop, those stabs do a quick descending run that says loud and clear we’re not in C# minor. We start on that flattened second, with a Dmaj7 in its normal voicing, then Dmaj7 but in its 3rd inversion (the C# that was the highest note is now the lowest note), and then Bm7. I like using inversions like this as a sort of stepping stone that indicates the direction we’re heading in.
The bass just hammers out C#, reminding us where home is right through the whole track. It lands every four bars, so is completely absent when the chords go else in the last bars of an 8-bar pattern. I remember experimenting with having a bass note when we arrive at Bm7. But, nah. It felt like too much.
The pads are playing a thinned out combo of what the shorter stabs are playing, and with some descending inversions going on. So we have some combo of E, G#, B for most of the time and heading into bar 7 we get a combo of D, F#, A.
There’s a couple of ways to talk about these chords, which comes down to that fun fact that any seventh chord is made up of a minor and a major chord at the same damn time.
Like, on their own it would be most obvious to say we’re just moving between E major and D major triads.
But given what the stabs and the bass are doing, I’d prefer to say that we start with C#m7 missing its root note, then the second chord arguably first operates as D major while those Dmaj7 stabs are travelling by, and then for the last two bars of the progression we’ve got the same kind of thing as the first, Bm7 missing its root note.
I dunno, it’s the same combinations of notes, but that’s what makes sense to me.
The sound design
All three original sounds are just out of the box Bitwig synths. From memory they’re presets I then tweaked a little.
If the split out audio above sounds clean and tidy compared to the final track, it’s because in the final track both the stabs and the pads are glued together and made grungy by an effect called, aptly, LO-FI-AF. Listen how much more noise is there in the stabs, plus how the pads sound less stable.
Meanwhile, the bass note has some heavy modulation of its parameters, so the timbre shifts a fair amount each time it plays. Those tweaks to the synth sound create the swooping, phasing kind of effect that is a big part of the final result.
The bass then goes through a chain of effects:
- Bit crushing gives a digital grain like a Speak & Spell.
- This then runs into a kind of smeary reverb created through spectral processing, the kind of tech in play in that sample-modelling drum machine I used in ‘Ashcan Edition‘. (This time Unfiltered Audio’s SpecOps.)
- Finally, there’s long, slow echoes. (Bitwig’s most basic Delay-1.)
✨ Sparkles ✨
These shimmering sounds later in the track are a whole different set of chords, landing largely in between what I’ve called the big chords.
Messing with a piano roll “live” to create harmony
I went down quite a different route to come up with these chords, compared to what I’d usually do.
For the big chords, I went the normal route. I sequenced a series of notes, basically writing out instructions that then get sent to an instrument: play this note, at this time, with this loudness, and maybe with this much of a fully sick pitch bend to make it like an 80s keytar solo.
It’s like the successor to feeding instructions into a player piano, maybe: we make marks on a piano roll, feed that into the piano, and, when we hit go, the piano plays back exactly the notes on that piano roll.

Music software nowadays has actually standardised on using an interface called the piano roll, after exactly this.
But with these sparkly chords, while I used Bitwig’s piano roll, I’m then doing the digital equivalent of messing with the instructions between when they leave the piano roll and reach the piano. What you see on the piano roll is most definitely not what you hear.
Here’s what the un-messed-with piano roll for the sparkly chords sounds like. Be warned, it’s ugly!
The software I use gives you a whole set of what they call “note fx”, to do this manipulation of note data. Here’s the stack of these note-wrangling devices I set up for these chords.

I won’t go into the full explanation (although hit me up if you want it!), but if I wrote this like instructions, it might be something like this:
- Tidy up any notes that aren’t in C# Phrygian, by moving them up or down.
- Wildly rearrange the timing of the notes each time they play, but err towards keeping them pretty close to in time / on the grid.
- Add some randomness to how loudly each note plays.
- Finally, at the start of the track, only play the very lowest notes. Over time let through higher and higher notes until every note from the piano roll gets through.
What’s on the piano roll?
I deliberately made a progression on the piano roll that is hardly in C# Phrygian at all, knowing one of the note fx in the chain above was going to push everything back into that scale.
Some online chord finder reckons the first chord, the one I started with, should be described as an inversion of an E dominant 13th chord, inverted around C#.

While that chord does fit in the scale, I then just copy and paste it either up or down a semitone, repeatedly. The first, higher set of chords walks up from C# to E, while the lower one that comes in second is doing the opposite, the chords walk down from E to C#. So, it’s pretty spectacularly messed up.
When writing this post I toyed with actually doing the equivalent of printing the results of the note fx on to a fresh piano roll, to figure out what the resulting notes even are. But this post is huge enough and I may as well leave some mystery.
Why, Michael, why?
The fun for me in this kind of thing is to get out of habits and surprise myself. I reckon music is a lot about intuition, what feels right, and the process of making changes that intuition, so over the years your sense of what should happen next gets a bit narrower. Doing something arbitrary like I’ve done here usually throws up an unintuitive result, and it’s often fun to respond to that. I still feel really engaged in the writing process, especially when I’m combining these kinds of antics with the other more traditional, fully-in-control approach to other parts.
Not sure if it’s interesting, but I have tried to do even more generative stuff, which is where you’re almost (or actually) programming and telling your software to basically make a piano roll for you from the rules you gave it. I don’t find much joy in it and I usually feel distant from the results.
It’s probably clear I’m interested in harmony and in rhythm, and if you’re basically just telling a computer to spit out some set of notes that fit a scale and in a rhythm that fits say 16th beats… it’s just a bit “so what?” for me.
But some amount of coaxing the machines to intervene on what I had planned can be really exciting and, yeah, fun.
Unethical guitar harmonics
The last thing I’ll comment on for this giant post is that the guitar harmonics in this track are a free virtual instrument from a company called Spitfire Audio. This company has since been boycotted by lots of people I associate with online because of shit things one of its now former owners said.
I guess all I want to comment on here is that the fraught business of trying to navigate consumer choices perhaps unsurprisingly extends to making music, the tools you’re going to use at least. One minute you’re having a good time with some quality product and the next cognitive dissonance sweeps in, colouring your memories of making the music as well as, of course, affecting what you say and do next.
Or, as Blur put it…
