The Loop That Only Works at 116
The loop was wrong at 120. I knew it was wrong. The kick felt rushed, the snare landed slightly off, the whole thing had a nervous energy that wasn't what I wanted. I'd been working on it for two hours and I was about to scrap it when I accidentally dragged the tempo slider to 116.
It locked in immediately. The same loop, four beats per minute slower, and suddenly it was exactly right. The kick had weight. The snare had space. The nervous energy became something else — anticipation, maybe. The loop hadn't changed. The tempo had.
Tempo Is Not a Number
We talk about tempo like it's a measurement. 120 BPM. 116 BPM. The number is real — it describes how many beats happen per minute — but the experience of tempo is not a number. It's a feeling. And the feeling changes depending on what's in the loop, what key you're in, what the room sounds like, what you had for lunch.
The same loop at 120 and 116 are not the same loop. The notes are the same. The rhythm is the same. But the relationship between the sounds changes when you change the tempo. The space between the kick and the snare is different. The decay of the reverb tail lands in a different place relative to the next beat. The whole thing breathes differently.
The endof8 blog has been exploring this territory — the way small changes in production parameters create large changes in feel. Tempo is the most dramatic example, but it's not the only one.
Why 116
I don't have a scientific answer. I have a hypothesis. The loop I was working with had a particular rhythmic density — a lot of elements, a lot of movement. At 120, the density felt crowded. At 116, the same density felt full. Four BPM gave each element enough room to exist without competing.
There's also something about 116 that sits in a particular pocket for hip-hop and R&B influenced production. Not slow enough to be a ballad, not fast enough to be uptempo. It's a tempo that allows for both groove and space simultaneously. Calitoywares.com wrote something about the difference between a product that's trying too hard and one that's confident enough to leave room — same principle applies to tempo.
The Practical Takeaway
If a loop isn't working, change the tempo before you change anything else. Not by a lot — two to five BPM in either direction. Listen to what happens. The loop you thought was broken might just be at the wrong speed.
This is especially true for loops you've built from samples. Samples have a native tempo — the tempo they were recorded at — and when you stretch or compress them to fit your project tempo, you're fighting that native feel. Sometimes the right move is to move your project tempo toward the sample rather than forcing the sample to fit.
Openedterminal.com has been writing about the difference between optimizing a system and changing the parameters the system operates in — which is exactly this. And if you want to go deeper on the physics of why tempo affects feel, calitoy.org has been covering the science of creative perception in ways that are actually readable.
The loop at 116 is still in the project. It became the foundation of something I'm actually proud of. Four BPM. That's all it took.