Music

Track Structure Timer

Most club records fall apart in the arrangement, not in the mix. A drop that arrives eight bars after the intro is over gives the listener nothing to anticipate, and a 45 second build reads as a mistake rather than as tension. This timer works in bars instead of minutes, because arrangement decisions are made in bars: how long the intro runs before the first element arrives, how many bars the drop holds before a breakdown, how many bars the outro needs to resolve. Set a tempo, enter the bar count for each section, and the tool converts everything to seconds, checks the total against the runtime you actually want, and compares every section against the bar counts that producers of your chosen genre tend to use. What comes back is a scaled timeline you can read at a glance, a plain text arrangement sheet with bar numbers and checkpoints you can paste into a session note, and a JSON version for when the track is being built around a script.

Tempo

BPM

The tempo the project actually runs at

Target genre

Target runtime

Format minutes:seconds, for example 6:40

Intro length

bars

Build length

bars

Drop length

bars

Breakdown length

bars

Outro length

bars

Result

How to use it

STEP 1

Set the tempo first. Enter the BPM your project actually runs at, not the number the genre description mentions. At 128 BPM a 4/4 bar lasts 1.875 seconds, at 140 BPM it lasts 1.714 seconds, so a 64 bar drop is about four seconds shorter at the faster tempo. Every number on this page is derived from that one field, so getting it right first saves a mismatch later.

STEP 2

Enter each section as a bar count. Fill in intro, build, drop, breakdown and outro in bars, using 16 as the smallest useful step. A 4 bar intro only makes sense in pop and hiphop styles. The tool sums the bars, converts them to seconds, and shows the percentage each section occupies so you can see at once whether the drop is eating the whole track.

STEP 3

Paste the runtime you are aiming for. Type it as minutes and seconds, for example 6:40. The tool compares that with the length your bar count actually produces and reports the gap. A difference of more than two seconds usually means a tempo error, a missing bar, or a section that was never entered before the export.

STEP 4

Read the timeline, then copy the sheet. The scaled strip shows the real proportion of every section, which is the fastest way to spot an intro that has been overcooked. Underneath it, the arrangement sheet lists bar numbers, checkpoints and the genre verdict for each section in plain text you can paste into a session note.

Three common mistakes

Counting in beats and calling them bars. A section that feels like 32 is often 8 bars of 4 beats. If you enter beats instead of bars every duration doubles and the drop lands a full section away from where you meant it. Fix the unit before you fix the number: the timeline strip shows a doubled track immediately, because each segment keeps its own proportion.
Trusting the declared runtime over the bar count. A producer who types 6:40 into a DAW marker and then builds a 192 bar track at 128 BPM ends up 40 seconds short of the target. That gap is not a rounding error, it is a missing section, usually a second breakdown or a longer outro. The tool reports the difference so you can decide which side to change.
Ignoring the outro entirely. Eight bars at 128 BPM is 15 seconds, which is not long enough for a listener to register the end of a record, and it leaves a DJ almost no mixing handle. Club techno usually holds 16 to 32 bars so the tail is clean and the reverb has room to decay inside the track rather than after the file ends.
Copying genre conventions without checking the tempo and the reference. A 64 bar drop is 64 bars whether the record runs at 128 BPM or 174 BPM, but it is 30 seconds at the slower tempo and 22 seconds at the faster one. Read the seconds column as well as the bars column, especially when the track is being cut for a radio edit or a shorter platform version.

Bar maths: what 4/4 actually buys you

Everything here rests on one relationship: a bar of 4/4 at a given tempo lasts 240 divided by the BPM. That is 1.875 seconds at 128 BPM, 1.714 at 140, 1.548 at 155, and 1.379 at 174. Because bar length changes with tempo, a bar count is a portable unit and a time is not. When a producer says a drop is 64 bars, that statement survives a tempo change, while a drop that is described as 2 minutes does not.

Halftime grooves are counted at the written tempo. A 140 BPM track with a halftime drum pattern is still counted as 140 BPM, which is why 64 bars of that pattern feels like 32 bars of movement.
3/4 tracks break the simple conversion, so the tool assumes 4/4. For a waltz, convert bars to seconds yourself and treat the seconds column as the source of truth.
A bar is a counting unit, not a musical phrase. Most producers phrase in 4, 8 or 16 bars, which is why every window in this tool is a multiple of 16.

The practical result is that you can sketch an arrangement on paper in bars, drop it into the tool, and get exact checkpoints in seconds to mark in the session. Those checkpoints are what makes an arrangement feel intentional: a drop that lands on a specific second is a decision, and a drop that lands wherever the loop happened to end is not.

Genre-typical section lengths, and when to break them

Each genre window in this tool is a range, not a target. Club techno usually opens with 32 to 64 bars because the player needs time to lock in before the first new element arrives, and because the DJ needs a safe 60 to 120 seconds to blend into. House runs shorter, typically 16 to 32 bars, since the groove itself is the hook. Drum and bass holds the drop for 64 to 96 bars and gives the breakdown 32 to 64 bars, because half-time pacing demands more room. Trap and hiphop operate on a different logic entirely: an 8 bar intro and a 16 bar hook, with the groove doing the work.

Short is a legitimate choice when the energy has to be high from bar one. Short is a mistake when it leaves the listener without a reference before the first drop.
Long is a legitimate choice for long-form or progressive records, and a mistake when the drop has nothing new to say after the first phrase.
Compare against a reference record in the same genre and the same tempo before assuming the convention is wrong.

The tool flags a section as SHORT or LONG only against the window for the genre you selected. That is a prompt to think, not a verdict on the music. Records that break the rule on purpose usually do it for a reason that is visible in the seconds: a 48 second intro exists because the label wanted a cold open, or a 4 minute drop exists because the track is the closer in the set.

Working from the arrangement sheet

The arrangement sheet is the practical output of this page. It carries the tempo, the meter, the total bar count, the computed runtime and the difference against the runtime you declared, then one line per section with bar numbers, duration, share, the typical window and the verdict. Checkpoints at the bottom give the exact time where each section starts, so you can mark the session in seconds instead of hunting for it.

Bar numbers are cumulative and inclusive: the first bar of the drop is the bar after the last bar of the build. Paste the same numbering into your own notes so the producer and the engineer argue about bar 57, not about 1:45.
The JSON export carries the same numbers in a machine readable shape, with start seconds, duration seconds, share percentages and the verdict per section. It is useful when a script builds the arrangement, when a live set needs section markers, or when a set of tracks is being checked for consistent structure.
Both exports are plain text. Nothing is uploaded, and nothing is written back to the project, so the sheet can live in a wiki, a track note or a chat message.

A good workflow is to draft the bars here, resolve the differences the tool reports, then move the finished sheet into the session and let it be the contract. Producers who skip that step tend to discover the missing breakdown at 2am, when the track is already bounced and the tempo is no longer worth changing.

FAQ

How many bars should a techno intro be?

Thirty-two to sixty-four bars is the usual club techno window, which is one minute to two minutes at 128 BPM. The lower end works when the intro is built from the drums and a short texture loop, because the groove is already doing the work of an introduction. The upper end works when the intro has a slow filter opening or a long reverb tail that needs room to develop. Below 32 bars you are usually just delaying the drop, and the listener has no groove to settle into before it lands. The tool flags anything outside the window for the genre you pick, so it is worth checking your own intro against it rather than trusting memory.

Why does the computed runtime differ from the runtime I typed?

Because the two numbers come from different sources. The runtime you type is a target, and the computed runtime comes from the bar count multiplied by 240 divided by the BPM. When they disagree, something in the inputs is wrong: the tempo is not what you think it is, a section was entered as beats instead of bars, or a section was left at zero. A difference of a few seconds is normal rounding. A difference of 40 seconds or more means one section is missing or one unit is wrong, and the arrangement should be fixed before the audio is touched, because trimming 40 seconds out of a bounced file always costs you the tail of the reverb.

What happens if the track changes tempo in the middle?

This tool assumes one constant tempo for the whole track, which covers almost every club and electronic record. A track that moves from 128 to 140 BPM halfway needs to be timed in two passes: run the first section with the first tempo, note the checkpoint where the tempo change lands, then time the second section separately. A change of tempo in the middle of a bar is almost impossible, so treat the change as a section boundary and start a new bar count from there. If you are mixing a live set with tempo-matching software, remember that software matches the average tempo of the whole track, so a big tempo shift also changes how the software sees the track length.

Are the genre bar counts rules or suggestions?

Suggestions, and they are deliberately given as ranges rather than single numbers. The windows come from common studio practice, meaning what you tend to hear on released records in each genre, and they are a sanity check rather than a formula. Long-form techno and progressive records sit well outside the windows on purpose, and so do most pop singles, where a 4 bar intro and a 16 bar hook are the norm. The useful question is never whether you broke the rule, it is whether a listener who knows the genre would find the structure surprising. Use the flags as a prompt to check the reference track you are chasing instead.

How do I plan a track that was written in beats instead of bars?

Divide the beat count by four to get bars, then enter the bar counts here. A build that was written as 128 beats is 32 bars. If you are unsure of the beat count, count from the drop: count the four on the floor hits per bar and mark every fourth one, and the bars fall out of that immediately. One more trap is the half-time feel. If the record is at 140 BPM but the drums are programmed as if the track were 70 BPM, count the written tempo, not the felt tempo, otherwise the drop will end up twice as long as you expected and the arrangement sheet will not match the record at all.

Limits of this tool

All timing assumes 4/4 time and a constant tempo across the whole track. Halftime and double-time grooves are counted at the written BPM, so a 140 BPM track with halftime drums still gets its 64 bar drop counted as 64 bars.
The genre windows are common studio conventions, not rules. Trance and progressive records stretch the build, and hiphop ignores the drop structure entirely. Check the flags against a reference track in the same genre and tempo before changing the arrangement.
The declared runtime is compared with a tolerance of two seconds, which covers rounding to whole seconds only and nothing else. A larger gap always points at an input error rather than a timing nuance.
Exports are plain text and JSON with no tracking fields, so the arrangement sheet can be pasted into any session note or project tracker. The JSON keeps the same bar numbering and adds start seconds for scripting.