DAW Bar:Beat → Seconds
Convert a DAW bar.beat.sixteenth position into elapsed seconds at any BPM.
Overview
The DAW bar-beat-seconds converter translates between musical positions (like 5.2.3 — bar 5, beat 2, sixteenth 3) and elapsed seconds at a given BPM. Drop in a position and the tool returns the exact time on the project timeline, accurate to milliseconds, so you can line up markers, automation points, or video sync without trial and error.
It's a daily-use tool for sound designers scoring to picture, post-production engineers placing SFX, and producers writing automation lanes that need to hit specific instants. The math also goes the other way — give it a timestamp and it tells you which bar, beat, and sixteenth-note that lands on, which is invaluable when matching loops or aligning recorded performances.
How it works
A bar at 4/4 contains four beats; each beat at 1/4 = quarter-note resolution lasts 60/BPM seconds. A sixteenth is a quarter of that. So at 120 BPM, one quarter beat = 0.5 s, one sixteenth = 0.125 s, one bar = 2.0 s. The converter sums (bars - 1) x beats-per-bar + (beat - 1) + (sixteenth - 1) / 4, all multiplied by the seconds-per-beat, to get total elapsed seconds.
Different DAWs number bar.beat.sixteenth slightly differently. Pro Tools, Logic, Cubase, and Ableton all start counting from 1.1.1 at the project origin, so bar 1, beat 1, sixteenth 1 means time zero. The tool follows that 1-based convention. Time signatures other than 4/4 simply change the beats-per-bar count, and unusual beat units (like 6/8 with the eighth as the beat) are handled by adjusting seconds-per-beat accordingly.
Examples
120 BPM, 4/4, position 5.1.1 → 8.000 s
140 BPM, 4/4, position 1.3.1 → 0.857 s
90 BPM, 3/4, position 9.1.1 → 16.000 s
174 BPM, 4/4, time 22.345 s → bar 17, beat 1, sixteenth ~3
FAQ
Why does my DAW show a slightly different time at the same bar?
Some DAWs offset bar 1 by a count-in or pre-roll. Make sure the start of bar 1 in your project corresponds to time zero, or subtract the pre-roll length from the result.
How do tempo changes affect the math?
The simple formula assumes a constant tempo. If your project has tempo automation, you have to sum each segment separately, multiplying its duration in beats by its own seconds-per-beat.
What if my time signature changes mid-song?
Same idea: convert section by section. Add the elapsed seconds at the end of each section to the running total.
Can I use this for video frame sync at 24 / 25 / 30 fps?
Yes. Convert to seconds first, then multiply by the frame rate to get the corresponding frame number. Watch out for drop-frame timecodes at 29.97 fps.
Is the sixteenth position resolution enough?
For most music it is. For very tight sync you'll want ticks or PPQ (pulses-per-quarter), which DAWs use internally at thousands of subdivisions per beat.