Version Controlfor Songs, Not Just Files
A song in progress is really a stack of versions. Concerto keeps that stack in order: every bounce playable, every change noted, every comment attached to the version it belongs to.
How It Works
A History Your Whole Team Can Hear
Projects hold songs, songs hold versions. Upload a new bounce and it lands on top of the stack. The rest stays right where it was.
- Every Version, Kept
Each song holds its full upload history. Old bounces stay playable and commentable. Nothing gets overwritten.
- Change Notes
When you upload a new version, note what changed. The upload dialog even suggests recently resolved todos to reference.
- Version Comparison
On Ensemble workspaces, compare two versions visually and swap the audio back and forth to hear exactly what changed.
- Feedback Follows Versions
Comments and todos are tied to the version they're about, so a note from three bounces ago never gets confused with today's mix.
What Changes When Versions Have a Home
Generic file storage wasn't built for iterative creative work. Here's what you stop worrying about:
- Stop losing previous versions when you save over files
- No more ‘Song_v1_final_FINAL_actually_final.wav’ naming chaos
- Go back and hear any earlier bounce whenever you want
- See which feedback each new version was meant to address
- Collaborators always know which version is current