FPS to BPM Converter for VJ Loops and Live Visuals

Locking a VJ Loop to the Tempo of a DJ Set

You have a clip on the deck and a DJ pushing a tempo at you. The clip does not care about bars — it only knows how many frames it holds and how fast it plays them. Turning that frame rate into beats per minute is what tells you whether the loop will land on the downbeat or slide off it by the third repeat.

Conversion factor: FPS × 60 = BPM. A clip running at 24 fps produces 1 440 frames every minute; at 30 fps it produces 1 800. To get the tempo a loop plays at, divide the render rate by the frames in one beat: a beat occupying 12 frames of a 24 fps clip gives 24 ÷ 12 = 2 beats per second, and 2 × 60 = 120 BPM.

What a clip length really tells you

A frame count is a fixed duration

128 frames at 30 fps occupy 4.266 667 seconds whatever the mixer does. That duration is all you have to negotiate with.

A duration is a tempo in disguise

Decide how many beats that clip should fill and the tempo falls out. Eight beats across 4.266 667 seconds is 112.5 BPM, and nothing else loops cleanly.

Bars beat seconds as a unit

A two-bar clip re-cues at every phrase boundary; a 4.3-second clip re-cues nowhere in particular, which is why libraries are best rendered to a bar count.

Working Out a Loop's Tempo Before You Load the Clip

Reduce the clip to a per-beat rate

A 128-frame clip at 30 fps meant as two bars holds eight beats, so a beat is 16 frames and the per-beat rate is 30 ÷ 16 = 1.875. Type that into the FPS field.

Read the tempo the clip already carries

The BPM side fills in while you type — 1.875 comes back as 112.5. If that disagrees with the tempo on the DJ's display, the clip needs retiming rather than re-cueing.

Size a clip you have not rendered yet

Press the swap arrows, or type into the BPM field instead. Entering the set's tempo returns the beat rate you divide your render frame rate by to get frames per beat.

Copy the bare figure into the render dialogue

The copy button beside either field gives digits with no unit attached, which is what a duration or tempo box in a compositor expects. Ctrl+C inside a field does the same.

Loop Frame Counts and the Tempo They Lock To

Each row is a real clip length assumed to fill a whole number of 4/4 bars. When a track sits at one of these tempos, that clip holds sync through the whole mix without a nudge.

Loop length	Render rate	Duration	Bars filled	Tempo it locks to
64 frames	24 fps	2.666 667 s	1 bar	90 BPM
96 frames	24 fps	4.000 s	2 bars	120 BPM
90 frames	25 fps	3.600 s	2 bars	133.333 33 BPM
150 frames	25 fps	6.000 s	4 bars	160 BPM
128 frames	30 fps	4.266 667 s	2 bars	112.5 BPM
300 frames	60 fps	5.000 s	2 bars	96 BPM

Fashionable tempos rarely give whole frames per beat. At 30 fps only tempos dividing 1 800 do — 60, 72, 75, 90, 100, 120, 150, 180 and 200. A 128 BPM house track wants 14.062 5 frames per beat, so beat markers never sit on a frame line. The bar still can: one bar at 128 BPM lasts 1.875 seconds, exactly 45 frames at 24 fps.

Fractional beat rates typed off the timeline

Awkward figures such as 1.875 or 2.343 75 go in as they are, with a comma or a dot as the decimal mark and stray spaces ignored.

Enough decimals to expose a drifting cue

Read-outs run to eight decimal places, where the gap between a 112.5 BPM clip and a 112 BPM track shows up long before your eyes catch the slip on the wall.

Both directions during a changeover

Mid-transition the question flips to what clip length suits the incoming track, and since either field can be the one you type in, nothing is entered twice.

VJ Sync Questions From the Booth

My loop is 128 frames at 30 fps — what tempo does it actually play at?

It runs for 4.266 667 seconds. Decide how many beats it covers: as two bars of 4/4 that is eight beats, giving 8 × 60 ÷ 4.266 667 = 112.5 BPM. Read as a single bar it would be 56.25 BPM instead, so the bar count has to be a deliberate decision rather than an assumption.

Why do the visuals slide off the beat halfway through a long set?

A small mismatch compounds on every repeat. A 4.266 667-second clip against a track at 112 BPM falls short by 19.05 ms per pass; over five minutes it repeats about 70 times and lands 1.34 seconds adrift, more than half a beat. The other culprit is a DJ riding the pitch fader, moving the target while your clip length stays fixed. Re-cue on a phrase boundary.

How do I retime a loop for a different tempo without visible stutter?

Work out the target frame count first. Two bars at 120 BPM is 4.000 seconds, or 120 frames at 30 fps, so a 128-frame clip must play 128 ÷ 120 = 1.066 7× faster. Speed changes under about ten per cent survive plain frame dropping; past that, blended or optical-flow retiming hides the hitch.

Should I build my clip library in bars or in seconds?

In bars. One, two, four and eight-bar clips rendered at a single reference tempo can be stretched to any set by one ratio, and each re-cues at a musically sensible point. A shelf of seven-second clips has no phrase structure, so nothing lines up once the tempo moves.

Is tapping the tempo good enough, or do I need a clock from the booth?

Tapping gets you within about a beat per minute, fine for a three-minute cue and hopeless across a headline set — the drift arithmetic above is why. A MIDI clock or an Ableton Link session re-anchors the clip every bar and follows pitch-fader moves automatically. Working the tempo out by hand beforehand still matters, because it tells you whether the clip was ever the right length.