The Drop · September 24, 2026

Jersey club visualizer: a kick pattern against a 90 millisecond floor

Every other genre on this site gets visuals that follow the drums. Jersey club is the first one fast enough to ask whether the drums outrun the screen.

A foot in a white sneaker resting on the footboard of a kick drum pedal, the bass drum hoop visible behind it on a patterned venue carpet

Photo via Unsplash

Jersey club has one structural idea and it is in the kick: a short bunched run that tips over into the next bar and drags everything with it. Flashing on the beat is easy when the beat arrives four times a bar. This is five kicks inside a bar lasting under two seconds, and the question stops being aesthetic and becomes arithmetic.

The pattern, and the gaps inside it

The bar gets written down the same way nearly everywhere. Orphiq's jersey club reference puts it as "Five kicks per bar, spaced 4-4-3-3-2 in sixteenth notes", landing them on steps 1, 5, 9, 12 and 15 of a sixteen step bar. The front half reads like a half time pulse and the back half compresses into a three three two, the same displacement family the drill post met in the hi-hats, except carrying the kick drum.

Tempo sits high. The same reference gives the genre as 130 to 140 BPM "with a lot of tracks sitting at or near 140", and records bear out the top of that: Cookiee Kawaii's "Vibe (If I Back It Up)" measures 160 BPM on Mixgraph, Lil Uzi Vert's "Just Wanna Rock" 150 BPM on SongBPM. Call the working range 140 to 160 and divide: a sixteenth note is 107 ms at the bottom and 94 ms at the top. Those decide everything below, because the app's hard minimum gaps between visual events sit in the same neighbourhood.

Two flash paths, two different floors

There is not one flash mechanism here, there are two, with different limits. The main beat trigger reads bass energy against a rolling average of the last 0.7 seconds, and when it fires it sets a hard cooldown: beatCooldown = now + 90. Ninety milliseconds, no exceptions.

The per drum image trigger is separate. Give an uploaded image a role of Kick, Snare or Hi-hat and that path watches spectral flux in three frequency bands, never touching the 90 ms cooldown. It has its own, and they differ: kick 110 ms, snare 140 ms, hi-hat 90 ms. The kick, the one drum jersey club cares about, has the slowest of the three. So there is no single answer to whether the app keeps up. There are two, and here they disagree.

The arithmetic

TempoBar16th note16th triplet
140 BPM1714 ms107 ms71 ms
150 BPM1600 ms100 ms67 ms
160 BPM1500 ms94 ms63 ms

Read that sixteenth column against the two floors and the genre falls between them. A sixteenth is 94 to 107 ms here, above the 90 ms flash floor and below the 110 ms kick image cooldown, every time. It stops clearing the kick cooldown at 136 BPM and does not reach the flash floor until 167 BPM, so jersey club sits in the gap. Two things follow: flashes can land on consecutive sixteenths anywhere in this range, and a Kick role image cannot. Put cover art on Kick, let the pattern double up, and one of the pair is silently dropped.

The standard bar never asks, mind. Those 4-4-3-3-2 gaps at 140 BPM are 429, 429, 321, 321 and 214 ms, the tightest double the slowest cooldown in the app. It is the roll that breaks.

Where it actually breaks: the roll

The move that ends a jersey phrase is a stutter, a kick repeated in triplets or thirty second notes to throw you into the next section. A sixteenth triplet is 63 to 71 ms and a thirty second note is 47 to 54 ms, both under every floor in the app. A six hit roll gives you three or four flashes, spaced unevenly depending on where the run started.

A limit rather than a bug, and it reads better than the alternative: the floor thins the burst instead of letting the screen become a solid rectangle of light. If you need every hit at that speed you need keyframes, not a reactive tool. Different problem from the drum and bass post, which is about a fast grid rather than events colliding inside one beat.

Settings that let the pattern do the work

The instinct on a busy genre is to turn everything up. Wrong here: the kicks are already the fastest thing on screen, and content stacked on top turns the pattern into noise.

The tempo the app prints

The grid comes from an offline scan of 60 to 180 BPM, with one correction: a winning reading under 95 BPM gets doubled if double time also scores well. Jersey tempos sail past 95, so nothing fires. The case to watch is an analyser hearing the pattern in half time. SongBPM reads that same Cookiee Kawaii record at 80 BPM where Mixgraph reads 160. Eighty is under 95, so a scan landing there gets promoted back up and the grid arrives where you would count it. The beat detection post covers how. Either way, read the BPM the app reports and set the change rate against that.

The safety part, which this genre earns

A visualizer flashing on jersey club sixteenths runs at roughly nine to eleven flashes per second, well inside the range associated with photosensitive seizures. Not a reason to avoid the genre, a reason to label the upload, keep the flicker overlay low or off, and think about where the clip will autoplay. The strobe safety post has the thresholds in full, and the drum triggers carry the pattern fine with flicker opacity at zero.

The short version

Load a club edit and watch the bar

Free, in the browser, no signup and no watermark. Change rate on Every 4 beats, artwork on Snare, and see how much of the pattern reads. Renders come out as a 1080p WebM you download yourself, or take the tour from the home page first.

Open the visualizer