Blog · Industry news

Prism: Drums Turns Drum Tracks Into MIDI

Prism: Drums converts drum recordings into editable MIDI, recognizing nine kit components. Here is what that does and does not do for a drummer who needs notation.

Aurally Sound has released Prism: Drums, an audio-to-MIDI plugin that turns recorded drum performances and loops into editable MIDI. According to Synthtopia's write-up, the machine-learning engine identifies nine drum components (kick, snare, closed hi-hat, open hi-hat, crash, ride, high tom, mid tom and low tom), captures their timing and velocity, and lets you edit, rearrange or replay the result through a different drum instrument. It runs as an ARA-integrated plugin where the host supports it, or as a standard insert effect where it does not, in VST3, AU and AAX on Windows and macOS. Processing happens locally, there is a built-in MIDI editor and drum sampler, and it is a one-time purchase at $79 with no track limit. That last part is the whole story for anyone doing drum transcription at volume.

Why this matters if you want a score out of a recording

Most drum transcription tools are built as part of a bigger audio-to-MIDI product, and drums are the afterthought. A piano-first model hears a kick and a tom as low notes on a keyboard and gives you a mess. A drum-first model that separates kick from low tom from floor tom is doing the thing drummers actually need, because the mapping from hit to staff position is the hard part of writing a drum chart.

Nine components is a specific and honest list. It covers a standard kit played in a standard way: kick, snare, both hi-hat states, two cymbals, three toms. That is enough to produce a readable chart for most rock, pop, country, gospel and worship material. It is not a full drum-kit ontology, and it does not claim to be.

The velocity and timing data is the part that matters more than people expect. A drum chart is not just which drum was hit. It is the dynamics: ghost notes on the snare, the difference between a rimshot backbeat and a light tap, hi-hat foot chick versus stick. If the MIDI carries velocity per hit, you have something you can turn into accents, and accents are what make a chart playable rather than a wall of noteheads.

What it changes in practice

If you are a drummer learning a part, this shortens the first pass. You load the track, get MIDI, and look at the grid instead of looping eight bars forty times. You still have to decide how to notate it, but the raw material is there.

If you teach, this is a fast way to build exercises from real recordings. Pull a groove out of a track, quantize it lightly, print it, hand it out. The student sees the actual pattern rather than your approximation of it.

If you produce or remix, the use case is different and arguably stronger. Replace the recorded kit with a sample library while keeping the performance's feel. Layer a 909 under an acoustic loop. Extract a groove and drop it under a different section. None of that needs notation at all.

The local processing claim deserves a mention. A lot of audio-to-MIDI tools upload your file. If you are working on a session under an NDA, or on an unreleased record, keeping the audio on your machine is not a nice-to-have. It is the difference between being allowed to use the tool and not.

What it does not change

Nine components is nine components. A china, a splash, a cowbell, a second snare, a hi-hat tambourine, a stack: none of those are in the list. They will either be assigned to the nearest recognized component or dropped. If you play a lot of auxiliary percussion, or you are transcribing a prog or fusion track with a large kit, expect to fix those hits by hand.

The recognition is trained on acoustic drums, and Aurally Sound says clean recordings produce the best results. That is a fair caveat and you should take it literally. A close-miked kit in a decent room will transcribe well. A phone recording of a live band with the drums bleeding into every other mic will not. An electronic kit with a MIDI-ish sound may or may not land where you expect, because the model is listening for acoustic timbres.

Stem separation is supported but not free of cost. The developer notes that artifacts in separated recordings may affect detection. That matches what we see across the board: separation is usually what makes a busy mix transcribable at all, but the separation itself introduces smearing, especially on cymbals and snare tails. If you have the isolated drum track, use it. If you only have the mix, separate first and budget time for cleanup. Our stem splitter is built for exactly that first step.

And the biggest thing it does not change: MIDI is not notation. A MIDI file tells you a kick hit at a given tick with a given velocity. It does not tell you that the passage is a half-time shuffle, that the hi-hat pattern is swung, or that the fill should be written as a triplet. Those are editorial decisions, and they are the ones a drummer makes. Prism: Drums gives you the data. It does not give you the chart.

Our view

This is a sensible product with a narrow, well-chosen scope, and the pricing shape is the most interesting part. A one-time purchase with no track limit sits badly with subscription audio-to-MIDI tools for anyone doing this regularly. If you transcribe drums for a living, or you teach and want to pull examples every week, that math is easy.

The trade-offs are real, though. A single-purpose plugin means a single-purpose workflow: you are in a DAW, you get MIDI, and then you leave for your notation app. If your end product is a printed drum chart, you are doing the notation work somewhere else regardless. That is not a flaw in Prism: Drums. It is a boundary, and it is worth knowing where it sits before you buy.

The open questions are the ones you would ask of any drum model. How does it handle brushes? How does it do on a swung ride pattern where the ride bell and the ride bow are close in timbre? What happens with a heavily compressed, gated 1980s snare that has almost no decay? How does it cope with a drummer who plays the hi-hat with the foot through the whole tune? None of that is answered in the announcement, and the honest answer is that you test it on your own material.

Who should care: drummers learning parts off records, teachers building material from real tracks, producers who want to keep a feel but change the kit, and transcribers who currently tap out kick and snare by hand. Who should not: anyone transcribing a large auxiliary kit, anyone working from a rough live recording, and anyone who wants a finished, printable chart out the other end. For that last group, this is a first draft generator, and the editing is still yours.

One more thing, because it comes up every time a tool like this ships. A transcription of a copyrighted song is a derivative work. Having the MIDI does not give you the right to distribute, sell or perform the resulting chart. The rules differ by country, so check with the rights holder or your local licensing body before you publish anything derived from a commercial recording.

What to do next

If you want to try the drum-first workflow end to end, the sequence is: separate the drums from the mix, convert to MIDI, import into your notation software, then edit. Our audio to MIDI converter handles the middle step for drums, piano, bass and guitar, and the output is MIDI you can open in any DAW. From there, transcribe a song to get PDF, MusicXML and MIDI out of the same pipeline, so the score opens in MuseScore, Sibelius, Dorico or Finale without retyping.

If you are weighing tools, compare on things you can check: which instruments each one supports, which export formats it produces, whether it separates stems, and whether the pricing is a subscription or a one-time buy. Our pricing page describes the shape of the offer rather than quoting numbers that move. If you want to see what other people have transcribed, Explore is a public library of shared scores. And if you are building this into a product, the transcription API is the programmatic route.

A full song usually takes a few minutes to tens of minutes depending on length and load, and the job page shows queue position, so you are not guessing. Start with one track you know well, compare the output to your own ear, and decide from there. That test tells you more than any announcement will.

Sources

Häufig gestellte Fragen

Can Prism: Drums give me a drum chart I can print?
Not directly. It outputs MIDI, which you then import into notation software like MuseScore, Sibelius or Dorico and lay out as a drum chart. The MIDI carries hit timing and velocity, not notation symbols like flams, ghost notes or repeat signs. Those you add by hand.
Does it recognize toms separately?
Yes. The nine components are kick, snare, closed hi-hat, open hi-hat, crash, ride, high tom, mid tom and low tom. Anything outside that set, such as a china, splash, cowbell or second snare, will land on the nearest recognized component or get missed.
Should I separate stems before running it?
Aurally Sound says audio from stem separation tools can be used, but artifacts in separated recordings may affect detection. If your drum track is already isolated, run it directly. If you only have a full mix, separate first and expect to fix more.
Does it send my recordings to a server?
No. Aurally Sound says all audio processing happens locally on your computer. That matters if you work under an NDA, on unreleased material, or with session files you cannot upload.
Is it a subscription?
No. It is listed at $79 as a one-time purchase with no recurring fees and no limit on tracks converted. Prices change, so check the product page before you buy.
Does the MIDI open in my DAW and notation app?
MIDI is a standard format. Drag-and-drop export puts it into a DAW project, and the same file imports into MuseScore, Sibelius, Dorico or Finale. You will still do the notation work in the notation app.

Song transkribieren

Lade einen Track hoch und erhalte bearbeitbare Notenschrift zurück. PDF, MusicXML und MIDI.