Back to Blog

The Track That Never Changes

Alexzaviar••6 min read
Old upright piano in purple darkness with faint overlapping rings of light

This week I sat through an eleven-minute narrated video three times, and only on the third pass did I pay attention to the music.

It was one of those calm, faceless storytelling channels: a steady voice, slow images, a story about a life. I was studying it because I want to make a short narrated piece of my own, voice over original music. The first two times I listened for the writing and the pacing. The narrator moves at roughly 150 words a minute, unhurried, never rushed.

The third time I listened under the voice. One ambient track runs the whole length. It never builds. It never drops. It doesn't change key, doesn't add a layer at the halfway point, doesn't swell when the story turns. Eleven minutes of the same quiet thing.

My first reaction was the producer's reaction: that's lazy. My second reaction, after I muted the voice and let the track play alone, was that it's the only reason the piece works.

Every instinct I have is wrong here

Almost everything I know about arrangement is about change. A verse earns a chorus. A second verse needs something the first one didn't have. A bridge exists so the last chorus feels like arrival. I've written whole articles about how songs die when nothing changes.

Under a voice, all of that flips. The voice is the arrangement. The story has the verses and the turns and the payoff. If the music also builds and releases, there are two arrangements running at once, and they will never agree on where the big moments are.

I caught myself planning exactly that mistake. My first sketch for my own piece was arranged like a song: sparse at the start, a second part entering around the two-minute mark, a lift near the end. Then I looked at where the lift would land against the script. It fell in the middle of a sentence that wasn't the climax of anything. A listener's ear would go to the music right there and drop the next two lines of the story.

The static track in that video never makes that trade. It never asks for attention, so all of it stays with the voice.

Static is harder to write than it sounds

Here's the catch. Eleven minutes of the same thing is easy to make and hard to make well. A four-bar loop repeated a hundred and fifty times becomes a clock. By minute three I'm counting it, and once I'm counting it, it's as distracting as a drop.

So the job isn't "write something that doesn't change." It's "write something that doesn't change and never announces that it's repeating." I've been working this out at the piano, and these are the ideas holding up so far.

No home chord. Most of my progressions lean on the tonic. They go away and come back, and the coming back is the satisfaction. Under narration, that return is a tiny event every few bars, and the ear notices the cycle. What's working better is a pair of chords that sit side by side without either one being home. Two open voicings a step apart, fifths and seconds, very few thirds. Neither chord resolves the other, so there's no moment where the loop "ends."

Nothing in the voice's register. I keep the left hand low and the right hand high, and I leave the middle of the keyboard almost empty. A melody line around the pitch of a speaking voice turns into a second speaker. The bed can have movement, just not there.

Loops that don't line up. This is the oldest trick in ambient music and still the best one. Brian Eno built parts of Music for Airports from tape loops of different lengths, so the pieces kept drifting into new combinations instead of repeating as a block. I'm doing a cheap version of that. A piano phrase that's seven bars long, a soft pad that's eleven, a guitar harmonic that comes back every nineteen. None of them divide evenly into each other, so the full combination takes a very long time to come around again. Each part repeats. The whole thing doesn't.

Slow everything down. Long attacks, long releases, the sustain pedal held down further than I'd ever leave it on a song. A note that fades in over two seconds doesn't register as an event. A note with a hard attack does, every time.

Change only when the story turns

I'm not totally against movement. There's one place it belongs, and that's when the story itself changes direction. A new chapter, a jump in time, the moment the narrator stops describing and starts reflecting.

At those points a change in the bed reads as punctuation, the same way a scene cut does in a film. What doesn't work is change on a musical schedule. Sixteen bars is a musical idea. The story doesn't know what a bar is.

So the order of work is the reverse of a song. I write the story first, mark the two or three places where it actually turns, and only then decide what the music does there. Usually it's small: one layer drops out, or the pair of chords moves to a different pair. No swells. Nothing that would make a listener look up.

What I'm taking back to songs

The surprising part is how much of this applies to my regular production. The intros I struggle with are often me trying to make the music do the vocal's job. The pads that wear thin by the last chorus are usually loops that line up too neatly. And the moments I love most in other people's records are often a part that stays put while everything else moves around it.

A track that never changes is not an absence of arrangement. It's an arrangement built around getting out of the way, and getting out of the way for eleven minutes turns out to take more care than filling them.

My narrated piece is still a sketch. The plan for the bed is two chords on an old family piano, three loops of odd lengths, and a lot of pedal. The test I'm holding it to is simple: twenty minutes of playback without me counting the loop once. Nothing I've arranged like a song has passed that test yet.

Share: