Number of bars in a song calculator

Non-positive duration or tempo, and meters outside the published set, fail with invalid_input so a session template never stores a negative or infinite bar count.

How to call the API and what the response contains

Combined duration must stay strictly greater than zero and at most thirty-six thousand seconds; tempo must stay strictly greater than zero and at most four hundred BPM. The steps array walks from raw minutes and seconds through total beats to the floored count so tests can assert intermediates. Send a JSON body with four required fields: minutes and seconds for the printed track length, bpm for tempo, and time_signature from the closed list 4/4, 3/4, 2/4, 5/4, 6/4, 7/4, 2/2, 3/2, 6/8, 9/8, 12/8, 3/8, 5/8, and 7/8. Minutes also accepts duration_minutes, min, and mins. Seconds also accepts duration_seconds, sec, and secs, and values above fifty-nine are allowed so a three-minute forty-five-second file can arrive as zero minutes and two hundred twenty-five seconds. Tempo also accepts tempo, beats_per_minute, and tempo_bpm. Time signature also accepts time_sig, meter, metre, and signature. Missing fields, non-numeric strings, non-finite values, unknown meters, and out-of-range numbers return invalid_input and are never charged. On success the body echoes the rounded inputs, sets duration_seconds, beat_unit, beats_per_bar, beat_seconds, beat_ms, bar_seconds, bar_ms, total_beats, exact_bars, complete_bars and the synonym complete_measures, remainder_beats, remainder_seconds, and the boolean incomplete_bar. Formula restates the closed relation complete_bars equals floor of duration seconds times bpm over sixty, divided by beats per bar. Pricing is a flat $0.002 per successful request with unit item.

Practical tips, limits, and what this tool is not

Read minutes and seconds from the player or file metadata rather than guessing; a three-second fade that you ignore will shift the remainder even when the complete bar count stays the same. Prefer sending numbers rather than pre-formatted clock strings when you control the client; string numbers are accepted only when they match a strict finite numeric pattern. Common studio checkpoints are easy to memorize: three minutes at one hundred twenty BPM in 4/4 is ninety bars; four minutes at one hundred BPM in 3/4 is one hundred thirty-three complete bars plus one leftover beat; two minutes at ninety-six BPM in 6/8 is one hundred ninety-two complete bars. If you tap 6/8 as a dotted-quarter pulse, convert first: two dotted-quarter beats per bar at that felt tempo equal six eighth-note beats at three times the number, which is the convention this endpoint uses. Keep BPM inside the published range so the reciprocal beat duration stays finite in IEEE double precision on the Worker and in the browser. When teaching, pair a positive happy path with a deliberate zero tempo or zero duration to demonstrate the hard invalid_input path. This landing targets people searching for a number of bars in a song calculator, how many measures a track has, or a tempo and time-signature bar counter; it is not a BPM detector, not a key finder, not a phrase-structure analyzer, and not a real-time audio processor. Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately probe edge cases. Round-trip checks are straightforward: recompute duration seconds times bpm over sixty, divide by the numerator, floor the result, and confirm it equals complete_bars.