Nobody's first beat is good, and that is not the point. The point is to finish one — a short loop, exported, sitting on your hard drive with a name. Finishing teaches you more in an afternoon than a fortnight of watching tutorials, because you run straight into the real problems: the drums sound thin, the bass is muddy, nothing quite fits. Those problems have answers.
Here is the whole process, from empty project to finished loop.
Set Up the Project Before You Write a Note
Ten minutes of housekeeping now saves an hour of misery later. Open your DAW, start a blank project, and deal with these in order.
- Tempo. Around 120 BPM if you are unsure. Hip-hop and lo-fi sit closer to 85–95 BPM; house and techno usually live between 124 and 130. You can change it later, but drums written at the wrong tempo rarely survive the move.
- Sample rate. 44.1 kHz is the safe default. Choose 48 kHz if the music might end up in a video.
- Buffer size. 128 or 256 samples while playing in parts; push it to 512 or 1024 if you hear crackles or dropouts.
- Save immediately. Give the project a name and a date before you add anything. "Idea 3" is a project you will never open again.
- Clear the master. No limiter, no demo plugin, no channel strip you did not choose. Start clean and the mix will behave predictably.
Work in Eight Bars, Not Eighty
A loop is the smallest complete musical idea: eight bars of drums, bass and melody that repeat without embarrassing themselves. That is today's target. Ignore intros, breakdowns and the arrangement already playing in your head — an eight-bar loop takes thirty seconds to copy and paste into a full track later.
Set your loop region to two bars at first, then extend to eight once the pattern works. Everything you write should survive being heard four times in a row.
Program the Drums First
Drums are the easiest part to get right and the easiest to overthink. Load a drum machine or sampler, pick samples from a single pack so everything belongs to the same family, and set the grid to sixteenth notes.
Kick and snare
Put the kick on beats one and three, and the snare or clap on beats two and four. That is a skeleton, not a beat, but it is the correct skeleton. Play it back. Now move one kick — an eighth note before the third beat, or a double at the end of the bar. Small moves, big difference.
Hats, velocity and swing
Add closed hats on every eighth note, then pull the velocity of every second hat down by about a third. That unevenness is what makes a grid sound human; identical velocities are the biggest giveaway of a beginner's drum track. For a lazier feel, apply 55–60% swing to the hats and leave the kick straight.
Resist the urge to layer
One kick, one snare, one hat. Stacking three kicks that fight each other in the low end is a problem you will spend an hour solving later without realising you caused it. Choose the best single sample and move on.
Add a Bass Line That Follows the Kick
If your drums sit in, say, F minor, your bass should start on F. Two notes are plenty for a first loop — the root, plus one other note that gives the line some movement. Write it in the piano roll rather than playing it, so you can see whether the notes line up with the kick.
Keep it simple and keep it low. Use a mono synth patch and low-pass around 200–300 Hz if the sound feels woolly. Make sure at least one note lasts long enough to be felt; a bass line that stutters on every sixteenth usually just sounds busy. To stop kick and bass competing, duck the bass with a sidechain compressor keyed to the kick, aiming for three or four decibels of gain reduction. If sidechaining feels like too much for today, simply shorten the bass notes so they sit between the kicks.
Layer in Chords and Melody
Pick one scale and stay inside it. Minor sounds darker, major sounds brighter, and either is fine for a first beat. Build a chord from three notes — root, third and fifth — and repeat it every bar. Three notes held for two beats each already sounds like music.
Then add a melody of four or five notes. Rules that work: start and end on a note from the chord underneath, use longer notes than you think you should, and leave gaps. A melody that plays continuously for eight bars is a scale exercise; one with space in it sounds intentional.
Two or three sounds in total is the right number — one for chords, one for melody. If you are loading a fourth synth, you are probably avoiding the harder job of writing a better part.
Make It Sound Like a Record, Not a Demo
Before exporting, spend fifteen minutes balancing. Pull everything down until the master meter peaks around −6 dBFS, with kick and bass loudest. Keep kick, snare, bass and anything in the vocal range in the centre; pan percussion, plucks or a shaker slightly left or right.
- Cut rather than boost. If the mix sounds muddy, high-pass everything that is not kick or bass.
- Send instruments to one reverb on a return track instead of loading a separate reverb on each. A shared reverb glues a loop together.
- Check the loop on phone speakers and headphones. The bass should thin out on the phone; if the melody disappears too, it needs more weight.
Export the Loop Properly
Exporting is where beginners lose work they have already done. Follow this once and the habit will stick.
- Name your tracks — Kick, Bass, Chords — so the session still makes sense in a month.
- Stop playback and let any reverb or delay tail finish before setting the loop markers.
- Export as WAV, 24-bit, at the same sample rate as the project. MP3 is for sending to people, not for keeping.
- Leave the master peaking around −6 dBFS. You can make it louder later; you cannot undo clipping.
- Name the file with tempo and key: untitled_128bpm_Fmin_v2.wav.
- Open the exported file in a fresh project and listen right through. If it holds up away from the session it was written in, it is finished.
What to Do Next
Save the project as a template — same tempo, same drum kit, same reverb return — so your next beat starts where this one ended. Then make another tomorrow, and another the day after. The gap between your first loop and your tenth is where the learning happens, and it closes faster than you would expect. When a loop feels stuck, the fix is usually simpler than you think: fewer sounds, fewer notes, more space. And when something does sound good, write down what you did. Your future self will forget.
Photo: Polina Tankilevitch / Pexels
