How to use this site

1. Start a transcription

On the front page, name the piece and this version of it, then either paste a public link (YouTube, a Google Drive share link, or a direct file link) or upload a sound/video file. Processing starts immediately in the background and takes from minutes up to ~10× the length of the recording. Reload the project page to see new results; a checklist shows what is finished. Ticking process on a rented cloud GPU rents a fast machine for the job (all results in ~5–15 minutes, costs about a cent); progress then appears in the pipeline log, and the result files show up all at once when it finishes.

2. Versions and pipelines

Each version of the piece (e.g. the backing track and the album recording) has its own tab. Inside it, independent transcription pipelines are compared: adtof (a neural network reading the drum mix; most reliable), mdx23c (splits the kit into six per-drum tracks first; can tell ride from crash but over-detects), and fused (adtof's hits, plus the per-drum tracks to tell ride from crash and judge how hard each hit was — the best of both).

3. Checking by ear: the sonification

The sonification is the original recording with a synthetic blip added at every transcribed hit (low thump = kick, snappy noise = snare, high ticks = hi-hat/cymbals). A missing blip means a missed hit, a blip with no drum under it is a false detection, a wrong-sounding blip is the wrong drum.

4. Following the score

While any player is playing, the bar you are hearing is highlighted in red in the scores of the same version.

It also works the other way: click an empty spot in any bar (not on a note — that records feedback) and the recording plays from that bar. It uses whichever player is already playing, or the one you listened to last, or the original.

If the beat detector hears bars of unequal length, the barlines are straightened automatically to the piece's usual bar length, and a checkbox appears above the results. Tick it only if the piece genuinely changes meter — then the detected barlines are kept as they are.

5. Downloads

MusicXML opens directly in MuseScore (File → Open) and is always available. The ready MuseScore file appears when automatic conversion succeeded. MIDI plays the transcription; the JSON files hold the raw detection data.

6. Giving feedback on the score

Point at any note or rest in a score: it turns blue. Click it to record what is wrong there (extra note, missing note, wrong rhythm… or free text). Notes with saved feedback are tinted orange; hover to read the note, click again to edit or remove it. Clicking the score's title takes general feedback about the whole transcription. Feedback is stored with the other result files (feedback.json).