Seconds to Minutes

A Session Timed in Seconds, a Release Listed in Minutes

Inside a project everything is seconds. A region is 32 seconds long, the intro sits at 0:00 to 0:15, the reverb tail runs 4.2 seconds past the last hit, and the transport counter ticks up in seconds and fractions of one. Outside the project nothing is. A distributor's metadata form wants a duration, a sync brief asks for a 30-second cut and a 60-second cut, a playlist editor talks about tracks in minutes, and the release itself is listed as 3:24. Every arrangement decision made in seconds eventually has to be reported as a length in minutes.

Conversion factor: 1 s = 1/60 min, so divide seconds by 60. A track that ends at 205 seconds is 205 ÷ 60 = 3.41666667 min, which on a release sheet is written 3:25 — the decimal is 0.41666667 of a minute, and 0.41666667 × 60 gives the 25 seconds back.

The Three Clocks Running in a Session

Musical time: bars and beats

The grid the arrangement is actually written on. A section is 16 bars whatever the tempo, and its length in seconds only exists once a tempo is chosen.

Absolute time: seconds on the transport

What the timeline ruler shows when you switch it off bars. Fades, delay times and the point a supervisor asks you to move are all placed here.

Catalogue time: the listed duration

Minutes and seconds on the release, rounded to a whole second and fixed forever once the master is delivered. Trailing silence counts towards it.

Platform time: the counted window

The first 30 seconds, which streaming services use as the threshold for whether a play is counted at all. Half a minute, decided before the first chorus.

Reading a Region Length as Track Time

The workflow below is what happens between bouncing a rough arrangement and filling in a delivery form, when a pile of second counts has to become one duration.

Enter the seconds the transport reports

Type the raw figure, decimals included — 205, 187.5, 32.4. A comma is accepted in place of the dot, so a length shown as 187,5 by a European-configured host needs no editing first.

Add the tail before you convert

Master length is measured to the last sample, not the last note. A reverb or delay tail that rings 4 seconds past the final hit is part of the duration, and so is any silence you left at the top.

Turn the decimal back into a colon

A metadata field wants 3:25, not 3.41666667. Take the fractional part of the minutes and multiply by 60: 0.41666667 gives 25, which is the seconds after the colon.

Reverse it to place a brief on the grid

The swap button (↔) gives min → s, which is the direction a sync brief arrives in: a 1.5-minute edit is 90 seconds, and at 120 BPM that is exactly 45 bars of 4/4 to work with.

The decimal is not the seconds. 3.5 min is 3:30, not 3:05, and 3.25 min is 3:15. Filing a decimal minute into a field that expects mm:ss is how a 3:30 track ends up in a catalogue as three minutes and five seconds, which nobody notices until a sync report does not match.

Bar Lengths and Track Times at Working Tempos

Tempo is what connects the two clocks. One beat lasts 60 ÷ BPM seconds, so a 4/4 bar lasts 240 ÷ BPM, and from there any section length in bars has a length in seconds. The last column is the useful one when an arrangement is being sketched: how many bars fit inside a three-minute track, which is 180 seconds. Values that do not divide evenly are shown to four decimals.

Tempo	Seconds per 4/4 bar	Bars per minute	Bars in a 3-minute track
70 BPM — slow ballad	3.4286 s	17.5	52.5
80 BPM — downtempo	3 s	20	60
90 BPM — hip-hop	2.6667 s	22.5	67.5
100 BPM — mid-tempo pop	2.4 s	25	75
110 BPM — indie rock	2.1818 s	27.5	82.5
120 BPM — the round one	2 s	30	90
128 BPM — club	1.875 s	32	96
140 BPM — trap, dubstep half-time	1.7143 s	35	105
174 BPM — drum and bass	1.3793 s	43.5	130.5

The 120 BPM row is why so many demos land there. A bar is two seconds flat, a four-bar phrase is eight, an eight-bar section is sixteen, and a 90-bar arrangement is a three-minute track with no arithmetic at all. Everything either side of it is messier, and the fractional bar counts in the last column explain a familiar problem: at 70 or 174 BPM a three-minute target lands mid-bar, so either the arrangement or the target has to move.

What This Pair Does While an Arrangement Is Being Cut

Check a length without leaving the arrangement

Type the seconds a region reports and the minutes appear as you go, so the question of whether the edit is under three minutes is answered before the fader moves again.

Place a brief written in minutes

Swapping the pair turns a request for a 1.5-minute or 2.5-minute cut into the second count you can measure on the timeline ruler before deciding where the edit falls.

Milliseconds for the delay and fade fields

Both dropdowns are searchable across every unit the app defines, so the same page reads a 0.375-second dotted-eighth delay as 375 ms without opening anything else.

Fractions of a second survive the trip

Results keep up to eight decimals, so a 3.4286-second bar at 70 BPM does not collapse to three and a half, and a 16-bar section built from it still totals correctly.

Questions From the Mix Session

How long is one beat at 128 BPM?

0.46875 seconds, because 60 divided by 128 is exactly that. The number matters well beyond the metronome: a quarter-note delay is 468.75 ms, an eighth is 234.375 ms and a dotted eighth — the setting behind a great many guitar and synth parts — is 351.5625 ms. A 4/4 bar is four beats, so 1.875 seconds, and an eight-bar section is 15 seconds on the nose. Once you know the beat length in seconds, every time-based effect in the session can be set by arithmetic rather than by ear.

How many bars fit inside a three-minute track?

Multiply the tempo by 0.75, because 180 seconds at BPM beats a minute is 3 × BPM beats, and 4/4 puts four in a bar. At 120 BPM that is 90 bars, at 128 it is 96, at 140 it is 105. Structures built from 8- and 16-bar blocks fall out immediately: 96 bars at club tempo is six 16-bar sections, which is close to a standard intro, verse, build, drop, breakdown and outro with nothing left over. At 174 BPM the same target gives 130.5 bars, so a drum and bass arrangement either runs a little over three minutes or accepts a half-bar it has to hide somewhere.

Why does the first 30 seconds of a track matter so much?

Because streaming services only count a play once the listener has passed roughly the half-minute mark; anything shorter registers as a skip and earns nothing. Half a minute is 30 seconds, which at 120 BPM is 15 bars and at 90 BPM barely 11 — often not even a full verse. That single threshold has quietly reshaped arrangement practice: intros have shortened, the first vocal tends to land inside the first 10 seconds, and a long atmospheric opening is now a commercial decision as much as a musical one. It is also why a 32-bar ambient intro sounds fine on an album and is a liability as a single.

My arrangement changes tempo halfway — how do I total the time?

Convert each tempo block separately and add the seconds, then divide once at the end. Forty bars at 90 BPM is 40 × 2.6667 = 106.67 seconds, and 48 bars at 120 is 48 × 2 = 96 seconds; together that is 202.67 seconds, or 3.37777778 minutes, which is 3:23 on a release sheet. Gradual tempo ramps cannot be done this way at all — for those the only reliable length is what the host reports after a bounce. Bar counts stay meaningful across tempo changes; second counts never do.

How long should a fade-out be in seconds?

Think in bars first and convert afterwards, so the fade lines up with the music rather than fighting it. A four-bar fade is 8 seconds at 120 BPM, 9.6 at 100 and about 13.7 at 70 — the same musical gesture, three very different durations. Anything under two seconds reads as an edit rather than a fade, and anything past about 20 seconds tends to be cut by a platform's own trailing-silence handling anyway. Whatever you choose, the fade is part of the listed duration, so add it before filling in the delivery form rather than after.