A band’s song usually lives in everyone’s head. In slightly different versions.
Which is why the first rehearsal turns into the place where you find the differences. “Wait — I had that as eight bars.” “Was the solo section really that long?” You find out while five people are standing in a room you are paying for by the hour.
If there were one sheet before that. If everyone had read it and written down what they thought. Then the day you meet starts as a rehearsal.
The first draft already exists
Getting what is in your head onto a stave is enough work to stall on. But if you programmed the song in a DAW, the draft is already half done.
Drop a .mid, .midi, .musicxml, .xml or .mxl file into “Import from file” in the song list. Before anything is created, one screen tells you how long the song will be and how many notes each part has.
Press “Create song” and you have vocals, guitar, bass, keys and drums on parallel staves. Guitar and bass can be TAB. MusicXML exported from MuseScore also brings the chords, the lyrics and the repeat marks along.
This is not a sketch. It plays, and it prints. It is simply a score that nobody has agreed to yet.
One sheet instead of five
Now you hand over a link — one line in the group chat. There is nothing for them to install.
You are not the only one who can change it, either. If the drummer fixes their own stave, you never export anything again. And so that nobody breaks anything: the bars someone is writing lock automatically, edits in different places both survive, and only when two people hit the same place does the save stop and say so. Nothing is overwritten silently.
How far the link goes is up to you: band members only, anyone with the link can read and comment, or anyone with the link can edit.
The feedback arrives before the rehearsal
“That bit before the chorus — can we pull it back a little?” Explaining where “that bit” is costs a round trip every time, because nobody is looking at the same bar numbers.
With one sheet in front of everyone, you write it on the bar itself.
The other person gets an in-app notification, and clicking it lands them on that bar. Reply there, and mark it resolved once it is settled — the person who asked is told it is done. The conversation stays on the score instead of scrolling away in the chat.
(Writing feedback needs a sign-in. Reading only needs the link.)
The rehearsal can be about playing together
When the gaps surface early, the day you meet is a different day. Instead of opening with “so what do we do here”, you start by playing what you already agreed on and hearing how it actually sounds. In software terms: settle it in the prototype, then implement.
Once it is settled, show only the part you want and print — those are your A4 part sheets. To keep producing, export MIDI and go back to the DAW (repeats come out already unrolled, so it plays straight through).
If there is a song sitting unfinished in your DAW, try it with that one. You do not even need an account — the first visit without signing in offers the same import.
Related: accolva manual
