How long a song actually takes to make, measured on a Mac

24 September 2026 · 6 min read

Ask a producer how long a track takes and you usually get the length of the best session: the night the loop worked and the chorus landed. The real figure also includes the evenings of arrangement, the listening passes, the hour spent finding the right kick, the bounce that clipped and had to be redone, and getting the file to someone else. A week or two of per-app records, plus one line a day in a notebook saying which track you worked on, turns that guess into hours.

Why the estimate comes out short

The session you remember is the one where the track came alive. It feels like the song. Around it sit sessions that feel like housekeeping: editing a vocal take syllable by syllable, fixing a click at an edit point, naming and coloring forty tracks, re-bouncing because the first version went to a collaborator with the limiter still bypassed.

None of those produce the moment you remember, so memory drops them. There is a quick way to see the gap on a song you already finished. Select the project file in Finder and press Command-I. The Created and Modified dates show the calendar span the song really took. They say nothing about hours, but a song that “took a weekend” and was created five weeks before it was last modified is a hint that the weekend was not the whole story.

What a music day actually contains

Split the work into what happens inside your digital audio workstation and what happens around it.

Inside the workstation: writing, arranging, recording, editing, mixing and, for many people, mastering. On a record of the frontmost app this is one line, whether you use GarageBand, Logic Pro or any other workstation. Plugin windows usually open inside the host app, so an hour spent tweaking a synth patch counts as the workstation too. A standalone instrument or sample manager that runs as its own app gets its own line.

Around it:

• Listening. Reference tracks in the Music app, your own bounce on repeat, a playlist of the genre you are aiming at.
• Research. Sample sites, tutorials, a plugin manual, a forum thread about sidechain settings. Nearly all of this happens in the browser.
• File work. Finder, sorting sample folders, renaming stems, clearing disk space for a new library.
• Export and sending. The bounce itself (in GarageBand it lives under the Share menu; in Logic Pro it is called a bounce, under the File menu), then Mail, a chat app or a file-transfer site in the browser to get it to a collaborator, a client or a label.

The around-it work is where missing hours tend to hide, because it never feels like making music.

Listening is where the record gets strange

A frontmost-app record counts which app is in front, not which app is making sound. That matters more in music than in almost any other kind of work.

Play a reference track in the Music app, click back into the workstation to compare, and the time counts as the workstation, because that is the app in front. Play your own bounce in the Music app while you type notes about it, and it counts as Music. Sit back for a long, hands-off listen and the record is on shakier ground: automatic trackers generally treat a stretch with no keyboard or mouse input as time away from the Mac. Listen on headphones on a walk, in the car or on your phone, and it counts as nothing.

So the Music line on a day’s record is a partial count of listening at best. Critical listening in the sense producers mean it, the same mix on three pairs of speakers, mostly happens away from the Mac. Treat whatever listening you can see as a floor.

Measuring one track from blank project to sent

1. Pick the next track you start from scratch. Not the one that has been ninety percent done since spring; it will mislead you in both directions.
2. Let the Mac record each day without a timer. Punchcard notices which app is in front and, at the closing time you set, prints a receipt: one line per app with its time, and a total for the day. It records app names only, never project names, file names or window titles, so it does not know which song you were working on.
3. Keep a one-line log per day. Date, track, phase, and anything the Mac could not see. “Thu, track 3, comping vocals. Also forty minutes working out the bass part on the instrument.”
4. Mark the phase boundaries. Sketch done, arrangement done, mix sent for notes, final version delivered.
5. Add it up when the track is sent. The workstation line for each day you logged against the track, the browser and Music time you judge belonged to it, and the off-Mac time from your notes.

Step five is manual, and that is the honest limit. The receipt shows the day; your log says which song the day belonged to. If you work on three tracks in one evening, “track 2 for the first hour, then track 5” is enough. There are no projects or tags in Punchcard. It exports its record as CSV, so the adding up can happen in Numbers instead of on the back of an envelope.

If you also cut video, how long a video edit actually takes uses the same method for a project with a different shape.

What a finished tally tells you

One measured track is better than none, and three of a similar kind start to form a pattern. Three things are worth looking for.

The share that is not the workstation. If the workstation line is a smaller part of the total than you assumed, the rest is research, file work and sending. Much of that can be batched: one sample-hunting session a week instead of breaking off mid-mix to search.

The tail. The stretch from “nearly done” to “sent” (mix notes, small fixes, re-bounces, exporting stems) tends to take more days than it feels like it should. Knowing how long your tail is makes release dates honest.

Hours against calendar. A track that took twenty hours over one week and one that took twenty hours over six weeks are different planning problems. Hours tell you what to charge for production or mixing work; the calendar tells you how many releases a season can hold. How to estimate hours for a quote when you never tracked the last job covers turning a first measurement into a price.

What the record misses

Some of the most important work in music never touches the Mac, and no record of the Mac can see it.

• Time at the instrument. Working out a part on guitar or piano in another room, or practicing a take before recording it. If the Mac is asleep or out of reach, there is nothing to record.
• Ideas captured on the phone. A melody hummed into Voice Memos on an iPhone at the bus stop. Punchcard runs on the Mac and has no iPhone app.
• Rehearsals, sessions in someone else’s studio, gigs. All real work on the song, all invisible to your Mac.
• Thinking. The walk where you realized the second verse should be half as long.

Write these in the daily log as rough minutes. They do not need to be precise, only present, so the final number does not quietly assume the Mac saw everything. Work that happens away from the Mac goes into how to patch that gap without turning the log into a chore.

Questions

Does Punchcard know which project I had open? No. It records the name of the app in front and nothing inside it, so a day in Logic Pro is one line whether you touched one song or four. Your daily log does the assigning.

Should time in the Music app count as work? When it is reference listening or checking your own mix, yes. When it is an album on while you answer email, the email app is in front anyway, so it will not count as Music. Anything genuinely ambiguous, decide once and note the rule in your log so every track is counted the same way.

How many tracks before the number means anything? Three of a similar kind: three beats, three mixes for hire, three full songs with vocals. Keep them separate, because a beat and a finished vocal song are not the same job.

Does it matter that my workstation sits in front while I play an instrument into it? That is recording, and it belongs in the total. Short takes between clicks show up as workstation time. A long take where you never touch the keyboard or mouse may be read as time away, for the same reason as a hands-off listen, so if you track long live takes, add them to your daily log.