BlogResearch
How to fix an AI music transcription
The errors automatic transcription makes, how to spot them by ear and eye, and what a language model with the score’s own editing tools fixed on public recordings.
The short answer
An automatic transcription usually hears most notes but writes them badly. Our solo piano draft of a public-domain Für Elise recording had all 130 notes plus 67 extra, 66 of them overtones written as notes, in E major and 6/8 instead of A minor and 3/8. A proofreading pass by a language model working with the score’s own editing tools removed every extra note and set the key, meter and pickup right, in both of two runs. On guitar it helped less, and in our tests it never brought back a note the draft missed.
What goes wrong in an automatic transcription?
A transcription model hears pitches and times; a score also needs a key, a meter, bar lines and note values someone can read. Five errors account for most of what we see in drafts:
- Ghost notes. A piano string sounds overtones with each note, and the model can hear the octave above as a key of its own, struck at the same moment.
- Pieces of one note. A held note can come back as two, a singer’s slide into a note as a short wrong note before it, a vibrato as a wobble between two pitches.
- The wrong key. Every pitch can be right and the signature wrong: Für Elise’s A minor needs no sharps, but its G sharps and D sharps make a model guess E major.
- The wrong meter. Note values doubled or halved (6/8 for 3/8), or a 3/4 piece read in 4/4.
- Bar lines in the wrong place. A piece that starts on an upbeat needs a short first bar, and a steady recording drifts off its bar lines when the tempo is a fraction of a beat a minute out.
How can you check a transcription yourself?
Play the score against the recording, a few bars at a time, and look for these:
- Notes stacked an octave apart that the recording does not play: the upper one is usually a ghost.
- Where phrases end. The note they come to rest on, and its chord, is usually the key; compare it with the key signature.
- Count the first phrase. If its strong beats fall in the middle of bars, the meter or the first bar line is wrong.
- Very short notes before longer ones a step away: in singing these are slides into the note, not notes of the tune.
- Rests and ties scattered through a passage played legato: the notes are probably right and their lengths written badly.
What does an AI proofreading pass do?
ScoreStarling’s AI refine is a switch in the upload form for solo piano and for one instrument or voice. After the transcription, a language model reads the draft and edits it with the tools a person has in the editor, in a fixed order. We took that order from the strongest model we tried, which proofread six drafts with the same tools and no limit on time or steps:
- CleanCode finds ghost notes and the pieces of one note, from the notes and the recording
- StructureMeter, tempo, the first downbeat and the key
- ReadThe whole score once, against the piece’s returning phrases
- WriteSpelling, hands, held notes and readable rhythm
- FinishEmpty bars after the end removed, the page checked
It is told the recording is the judge: never re-transcribe, arrange, simplify or transpose. Its last message says what it changed and which bars to listen to again.
What does a fixed transcription look like?
Here is the opening of the Für Elise test, as the draft wrote it and after the pass. The draft is hard to read but holds every played note; the pass deleted the copies, set Beethoven’s key and meter, and gave each hand its own staff.
Before: the transcription
After AI refine
The 19-second Gymnopédie recording on our piano recording to sheet music page went wrong another way: the draft is in 4/4, with the left hand’s chords on the upper staff among the melody. Both runs of the pass ended with Satie’s notes in all eight bars, every pitch, note value and staff, in 3/4 and D major.
Before: the transcription
After AI refine
How well does it work?
We ran it twice on each recording with a reference transcription, on October 12, 2026, with the model it uses, OpenAI’s GPT-6.1 Sol. A note counts as right when a reference note has its pitch and starts within 0.1 seconds; F1 combines missed and extra notes, so 1.0 is every note and nothing else.
| Recording | Draft F1 | After F1 | Extra notes | Key and meter after |
|---|---|---|---|---|
| Für Elise, opening (piano, 24 s) | 0.795 | 1.000 | 67 → 0 | A minor, 3/8 (draft: E major, 6/8) |
| Bossa nova guitar solo (GuitarSet) | 0.839 | 0.887 | 25 → 12 | E major, 4/4 |
| Bossa nova accompaniment (GuitarSet) | 0.696 | 0.716 | 46 → 26 | E major, 4/4 |
On two sung recordings from a research dataset whose licence keeps them off this site, F1 went from 0.78 to 0.89 and from 0.79 to 0.87, and the share of bars that start with a note rose from about a third to nine in ten or more.
Seven recordings, six of them under a minute, make a diagnostic sample, not a benchmark. The guitar recordings gain little because their drafts’ errors are mostly missed or merged notes, which a proofreading pass cannot recover.
What can’t it do?
- Bring back a note the draft missed. Every gain in the table came from removing extra notes: missed notes stayed missed in every test.
- Tell every real note from an extra one. On four of the five recordings with a reference it removed one to six real notes along with the extra ones; on the accompaniment, six of 117.
- Judge a recording without a reference for you. On a 2:48 pop piano recording it removed the draft’s ghost octaves and kept the left hand’s figure on the lower staff, but whether every removed note was a ghost can only be checked by ear.
- Work on band recordings, which have several parts in one mix.
How long does it take?
A few minutes after the transcription finishes: one to four minutes on our test recordings of 19 to 82 seconds, and under three minutes on the 2:48 piano recording. The score is ready when the pass ends, with a few sentences on what it changed.
Sources
- Für Elise, Internet Archive, Public Domain Mark 1.0
- Erik Satie, Gymnopédie No. 1, Wikimedia Commons
- GuitarSet 1.1.0, Xi, Bittner, Pauwels, Ye and Bello, Zenodo (CC BY 4.0)
- High-resolution Piano Transcription with Pedals by Regressing Onset and Offset Times, Kong et al., 2020
- A Lightweight Instrument-Agnostic Model for Polyphonic Note Transcription and Multipitch Estimation, Bittner et al., Spotify, 2022
Questions and answers
Why does my piano transcription have notes an octave too high?
A piano string sounds its overtones along with the note, and the strongest is an octave up. A transcription model can hear one as a second key struck at the same moment. In our draft of a 24-second Für Elise recording, 66 of the 67 extra notes sat an octave or another overtone above a note being played.
Why is my transcription in the wrong key?
The notes can all be right and the key signature still wrong, because the key is a reading of the music, not a sound. Our Für Elise draft had every pitch right but four sharps (E major) instead of A minor. Look at where phrases come to rest: the note and chord they end on is usually the key.
Can AI fix a transcription completely?
No. A proofreading pass removes what should not be there and rewrites what is there. In our tests it never brought back a note the draft missed, and on four of five recordings it also removed one to six real notes along with the extra ones. Listen to the bars it says it was unsure of.
Does the AI pass change my music?
It should not: it is told never to arrange, simplify or transpose. Each change is saved as a new version of the same score, so undo steps back through them to the plain transcription.