The Drop · September 8, 2026

Drill visualizer: sliding 808s and a grid that runs at double the feel

Drill is written in one tempo and heard in another. Everything that goes wrong when you point a beat reactive tool at it comes from that one gap.

Macro close view of a woven speaker cone and its centre dome, the driver that has to carry a sliding 808 sub bass

Photo via Unsplash

Two tempos, one track

Ask a producer what tempo a drill beat is and you get the written number. Soundation's own genre guide puts it plainly: the tempo typically falls between 140 and 150 BPM, but at half time. Wikipedia's UK drill entry, citing Complex and FACT, gives roughly 138 to 151 for the same reason. Ask a listener to nod along and they will nod at around 70, because the snare is landing once every two written beats rather than on two and four.

Both numbers are correct. But a visualizer has to pick one, and which one it picks decides how fast your video moves.

The app will hand you the fast number

When your file loads, the tempo is worked out offline before anything is drawn. It builds an energy envelope over the first 60 seconds, then scans every tempo from 60 to 180 BPM in half BPM steps looking for the spacing that best lines the onsets up with themselves. How beat detection works walks through that scan properly.

Here is the part that matters for drill. After the scan picks a winner, there is a correction step: if the winning tempo is under 95 and the double time reading also scores well, the app doubles it. That rule exists so a slow, sparse track does not end up with a crawling grid. On drill it means the half time reading gets promoted back up. Land on 70 and you come out with 140. So you will almost always see a number in the 140s on load, even though the track feels half that fast.

That is a fact to plan around rather than a bug to fight, and it is the opposite of what happens at the other end, where a blast beat above 180 gets reported as a division of its real tempo because the scan stops there.

Every 2 beats is what your ear calls every beat

Content changes ride the detected tempo, and the app's default is a change every quarter beat. Do the arithmetic at 140 BPM and a written beat is 0.43 seconds, so a quarter of one is about 107 milliseconds. That is more than nine changes a second on a track whose pulse people feel at roughly 0.86 seconds. Nothing on screen survives long enough to be read.

Because the grid is in the written tempo, shift every option one notch slower than instinct says:

The flashes themselves are separate from this. They fire off live energy with a hard 90 millisecond floor between them, so they keep punching on individual hits no matter how patient your content rate is. That split is the whole trick here: a slow rotation of what is on screen, fast flashes on top of it.

A sliding 808 gives the triggers nothing to see

AXL Beats, the producer behind Drake's War, described the sound to Complex as 808s, slides and fast tempo snares. The slide is the signature and it is also the problem.

Uploaded images can be assigned to a drum role, and those roles do not watch how loud a band is. They watch how much it rose since the last frame. A struck 808 produces one sharp rise and fires the trigger cleanly. A glide to a new note produces a pitch change with no new attack, so the energy in the band never jumps, so the trigger never fires. You will get a hit on the note that starts the phrase and silence through the melodic run that follows.

Expect that rather than turning the kick sensitivity up to chase it. Raising it far enough to catch a slide only makes everything else in the low end fire too.

The hats are where the syncopation is

Drill hi-hats are built on a tresillo, the 3 plus 3 plus 2 pattern, which is why the top end feels like it is pulling against the beat rather than counting it. The bands behind the image roles are fixed, and at a 44.1k sample rate they work out roughly as:

Put a secondary image on Hi-hat and you get the tresillo on screen for free. It is the same mechanism the trap post uses for hat rolls, except drill's pattern is uneven, so the result reads as a limp rather than a machine gun. Keep the main artwork on Snare, where drill's backbeat sits, and note that anything on Kick will fire on 808 attacks as well as kicks, since they share a band.

Keep the drop detector low

The bass drop detector ships at zero and drill is a good argument for leaving it there or close to it. It can engage when bass energy sits near the loudest this track has been, and a sustained 808 holding under a whole eight bars is exactly that. Push the sensitivity up and you get permanent glitch slicing and scrambled text instead of a moment that means something. A log drum in amapiano causes the same trouble for the same reason.

A starting point

  1. Content change rate: every 2 beats. Every 4 beats if the images deserve a longer look.
  2. Main image or cover art on the Snare role, texture on Hi-hat.
  3. Bass drop detector at zero, or a quarter of the slider at most.
  4. Flash duration on the longer side, to sit with the half time feel rather than against it.
  5. Check the BPM the app prints on load. A number in the 140s is the written tempo and the settings above assume it. If it prints something near 70, halve the beat counts above.

Before you post it

This is still a strobe tool. Flash rates above three per second can trigger seizures in people with photosensitive epilepsy, and drill's density makes that easy to hit even at calm content settings, so put a warning on anything you upload. The strobe guide has the thresholds and the settings for the gentler end of the range.

The short version

Try it on your own beat

Free, in the browser, no signup and no watermark. Your audio never leaves your machine, and the render comes out as a 1080p WebM you can convert to MP4 with one ffmpeg command. Start from the home page if you want the tour first.

Open the visualizer