/ Use case — Learning production

Learn theory
by browsing samples.

Every file shows its key, tempo, mood, and instrument. The vocabulary stops being abstract once you've seen it next to a thousand sounds you've actually heard.

/ 01 — Where beginners stall

Starting out is hard
without context.

Four common stalls. None are about talent — they're about the file system not knowing what's in your samples.

  • / 01

    Sample-pack overload

    50 GB of free packs sit in `Downloads`. The starter pack tutorial says `pick a kick`. Which folder. Which file. Why this one.

  • / 02

    What even is BPM

    Tutorials say `play it in C minor`. Filenames say `vocalchop_03_FINAL.wav`. There is no bridge between the words and the files.

  • / 03

    Nothing sits together

    Two samples are stacked. Something clashes. Is it the key? The tempo? Without the metadata, every fix is a guess.

  • / 04

    Forgetting what you learned

    Yesterday's combo was perfect. This week the folder is gone. Lessons evaporate without an index to anchor them.

Fig. 01a / Theory in the metadata stripPer file · per browse

/ 02 — Theory in context

Theory next to
the actual sound.

Browse 50 kicks. Each one shows its tempo, key relevance, transient envelope, brightness. Patterns surface — `dark techno kicks tend to be …` — without reading a single textbook.

/ 03 — Plain-language assistant

Ask in English.
Get a sample back.

`What's a punchy 808`. `Find drums for a slow song`. `Show me something happy`. The assistant translates the question into a query against your library — no jargon required.

Fig. 02a / What's a punchy 808?Plain-English query · ranked result
Fig. 03a / `What goes with this?`Key + tempo compatibility

/ 04 — Compatibility

See why two
samples work.

Pin a sample, ask `what would go with this`. The result set filters by key, tempo, and tonal balance. After a few rounds, the rules start to make sense on their own.

/ 09 — FAQ

Questions from learners

Common questions from producers just starting out.