Every song that takes more than one sitting becomes a stack of versions: the demo, the rebounce after tracking, the mix with the new bridge, the one where the vocal came up a dB. Most tools give that stack nowhere to live. Dropbox happily lets a new export overwrite last week's; email scatters bounces across threads; and the file names (you know the file names) become the only record of what happened and when.
The failure isn't storage. All of these tools store audio fine. The failure is that none of them know the files are related. To Dropbox, your demo and your final master are two unrelated blobs that happen to share a folder.
What version control means for a song
For code, version control means branching, merging, and diffing. Audio needs something simpler and slightly different:
- Every bounce kept, in order. Uploading a new version never destroys an old one, and “which one is current” is never a question.
- A note on what changed. You write “Brought vocal up 1dB, re-cut the bridge” when you upload, while you still remember.
- Conversation attached to the right version. Feedback about the old chorus stays on the version with the old chorus.
- A way to hear the difference. Not a text diff, but an actual A/B between two bounces.
How Concerto does it
Concerto organizes work the way musicians already think: projects hold songs, songs hold versions. Upload a new bounce and it lands on top of the stack; every earlier version stays playable and commentable below it. Time-synced comments attach to the version they were written on.
When you upload, Concerto asks what changed. If you've been using song todo lists, it also suggests the todos you recently resolved so you can tag the version with exactly which feedback it addresses. On Ensemble workspaces, version comparison lets you see changed sections between two versions and swap the audio back and forth to hear them.
What it deliberately isn't
This is not “git for audio.” There's no branching, no merging, no three-way conflict resolution, because in years of making records we have never once wanted to merge two mixes the way you merge code. A song's history is a line, not a tree, and pretending otherwise adds ceremony without adding clarity. Concerto keeps the line intact and legible. That's the whole job.