How to use this site

On a phone a song opens as a practice player for the track without drums: the bar ruler (tap or drag to move), Drums to bring the drums back in, Speed without changing the pitch, Loop (the 4 bars around the playhead; drag the teal band's edges), Click (even clicks; turn Accent on for a higher beat one) and Count-in (a bar of clicks before playing and before each loop pass), and the big ▶. A Bluetooth pedal's Space and arrow keys work too. ⋯ at the top holds the downloads, the notation, recording yourself, all files, the technical log and this help. A Score tab appears when the song has notation. The front page then lists Your songs, the ones this phone opened: their ▶ carries on where you stopped, with the same loop, speed and drums. Everything below also applies; where it says to point at something, the phone shows the same information in the Files list.

1. Add a song

On the front page, paste a public link (YouTube, a direct link to a music file, or on the laptop a Google Drive share link) and press Make drumless track, or press Pick a song file: choosing the file starts it at once. On the cloud site you can also type the song's name instead of a link: Make drumless track then lists matching YouTube videos, and a tap on one starts it. The song is named after the video's title or the file's name; adding it again makes its next version. Processing starts immediately in the background. First come the drums stem and the track without drums, in a few minutes. The drum notation is made only if you tick Also write drum notation, or later Make the drum notation under the version's players; it takes from minutes up to ~10× the length of the recording. The project page updates by itself: until a result is ready, its player is replaced by a progress bar saying what is being done and roughly how long is left. A hatched, empty bar is waiting its turn. Point at a bar for the estimated percentage — it is an estimate from how long each step usually takes. (The full technical log is behind the gear button, top right.) On the cloud site the notation is made on a rented cloud graphics card (a few cents); an extra bar at the top shows the machine starting up, which usually takes 2–10 minutes, and each pipeline's results appear as soon as they are ready. You may close the page: the site keeps working for about a quarter of an hour after the last visit, and picks up where it left off at the next one. A machine that fails is replaced by another, up to five; after that the page offers Try again.

2. Versions and pipelines

backing track album take players · downloads · scores of the selected version

Each version of the piece (e.g. the backing track and the album recording) has its own tab, with its own address to bookmark or share, and a Delete this version button at the bottom. 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

blips = transcribed hits wave = original music

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 teal in the scores of the same version.

It also works the other way: tap or click anywhere in any bar, including a note or rest, and the recording plays from that bar. It uses whichever player is already playing, or the one you listened to last, or the original.

Above the score, a small two-option switch shows the piece's meter: steady (the detected time signature, barlines straightened — the default) or changing (keep the detected barlines exactly as heard). It can be switched only when the beat detector actually heard bars of unequal length; the ? next to it explains the details.

5. Downloads

Each pipeline's result files are the small icons to the right of its sonification player (point at one to see its name) — click one to download it, or drag it straight into your file manager. The green MusicXML logo opens directly in MuseScore (File → Open) and is always available; the purple MuseScore logo appears when automatic conversion succeeded. The round plug is MIDI, which plays the transcription; the { } braces are JSON files with the raw detection data.

Local drum recording

Each version can keep your own drum track in this browser. Use wired headphones. Choose what to play along to with Use as backing in the diagram or in the Backing lane below it. Press ● and then ▶ (or R, then Space): playback starts two bars early and recording starts at the playhead. From the very beginning you get a two-bar metronome count-in. Pressing ● while playing punches in at once; pressing it again punches out. Pause keeps recording armed; jumping elsewhere disarms it. Only the passage the playhead crosses is replaced, and ↶ undoes the last one. M mutes your track, S plays it alone. You never hear the microphone itself.

The ⋯ menu exports the whole song as a WAV with the mix you last listened to (the menu shows it), imports an audio file as your track, sets the latency correction (60 ms is a starting guess; changing it moves all your takes, so adjust it by ear while one plays) and clears your track. The volume slider changes only what you hear. Recordings are separate for each address, port and browser profile, and need HTTPS or localhost. Keys: Space play/pause, R record, M mute, S solo, Home back to start, Ctrl+Z undo.

On a touch screen, pinch the lanes with two fingers to zoom in and out, and tap or drag sideways to move the playhead. On a phone, Undo is in the ⋯ menu.

6. Giving feedback on the score

Turn on Comment on symbols above the score. Tap or click a note or rest to record what is wrong there (extra note, missing note, wrong rhythm… or free text). Tap empty space in a bar to comment on the whole bar, such as a wrong time signature or a missing symbol. These touches never start playback. Turn the switch off to play from bars again.

With a mouse, right-click reverses the action: it opens a symbol or bar comment in playback mode, and plays from the bar in comment mode. This does not change the switch.

Notes with saved feedback are tinted orange; bars with feedback have orange barlines. Hover to read the comment, or use the commenting action again to edit or remove it. Commenting on the score's title takes general feedback about the whole transcription. Feedback is stored with the other result files (feedback.json). On the public cloud site, saving feedback, switching the meter or deleting a version asks for the site's password once per browser.

The source code is on GitHub.

drum-transcribe

Play along without the drums

Give us a song: in a few minutes it plays here without its drums. Drum sheet music too, if you ask for it.

or

Everyone's songs