AI Sample Sorting
Every producer owns the same folder. It's called something like SAMPLES_FINAL_2, it holds years of kits, and half the files are named snap_04_bounce(1).wav. The sounds in there are great. Finding the right one mid-session is what kills the vibe. You came to make a beat and ended up doing library science.
TrapMan's answer is to have the plugin do the sorting. Drop your samples in and an on-device neural network listens to each one and files it as a kick, snare, hat or 808, automatically, in the background, before you've finished placing your first steps.
What it is
Under the hood it's a compact convolutional neural network, a CNN, the same family of model that recognizes images, trained here to recognize drums. It doesn't read filenames (thankfully, given what your filenames look like). It classifies the audio itself: the transient, the spectrum, the decay. A kick named perc_weird_09.wav still gets filed as a kick.
Two words in that description carry all the weight: on-device. The classifier runs on your machine, inside the plugin. No sample ever leaves your computer, nothing uploads to a cloud service, and there's no server round-trip to wait on. Your unreleased drum stash stays yours, and sorting works exactly the same with the Wi-Fi off, like the rest of TrapMan, which runs fully offline once activated.
How to use it
- Drag samples into TrapMan: from Finder, Explorer or your DAW's browser, straight onto lanes in the step grid.
- Keep working. Classification runs on import, in the background. There's nothing to babysit: you sequence, it sorts.
- Check the result. Each sample lands tagged as a kick, snare, hat or 808, so your session stays organized by what things are, not what they're called.
- Re-tag anything the network got wrong. The tag is yours to change: one manual correction and that sample is filed where you want it.
Honest limits
A classifier is a head start, not an authority, and it's worth knowing where it bends:
- Hybrid sounds confuse it, as they'd confuse a human. A distorted 808 that's basically a kick, a clap-snare stack, a metallic perc with a hat's spectrum: these can land in the wrong bucket.
- It only knows four families. Kicks, snares, hats, 808s. Sounds from outside that world (foley, vocal chops, textures) get filed under whichever family they most resemble.
- Re-tag it and move on. When something's mis-filed, re-tag it manually and keep working. You're correcting the occasional edge case, not auditing every import.
In practice, typical drum samples land where they belong, and the misses cluster around sounds you'd hesitate to name yourself.
Why this matters for the workflow
Step sequencing is fast because the grid keeps everything visible and one click away, but that speed dies if loading sounds takes minutes of digging. Sorting on import protects the part of beatmaking that's supposed to be instant: hear an idea, grab a kick, place steps, done. The library science happens in the background, where it belongs.
If your sample folder is still chaos outside TrapMan, the guide to organizing drum samples covers the manual habits worth keeping even with a classifier doing the heavy lifting.