How to organize a sample library so you can find any sound.

Why does every sample library turn into a mess?

Because packs are organized by the people who sell them, not by the person who uses them. A pack arrives as Label Name - Deep House Vol 3, with its own folders, its own naming habits and its own idea of what a "top loop" is. Ten packs later you have ten filing systems, and the kick you want is in one of forty folders called Drums.

The fix is not a better pack. It is one filing system that is yours, applied to everything that comes in.

Should you organize samples by pack or by instrument?

By instrument. When you are making a track you never think "I need something from Vol 3". You think "I need a snare" or "I need a chord loop in C minor". Your top level should answer that question directly. Keeping the pack’s name further down the path is fine, and useful for licences, but the first thing you open should be the instrument.

What folder structure works for a sample library?

Few folders, each obvious, each holding one kind of sound. Here is the layout Adam Studio uses internally, eight folders with eighteen instruments under them. It works as a manual system too:

Two rules make it hold. Drums are split by where they sit in the spectrum, low, mid and high, because that is how you layer them. And harmony is kept apart from melody: a chord loop and a lead line do different jobs even when they come from the same synth.

What should a sample’s file name say?

Everything you would otherwise have to listen for. A good name carries the instrument, a word for its character, and for anything pitched or looped, the tempo and the key:

• kick_punchy_01.wav
• chords_loop_warm_rhodes_120_Fmin.wav
• guitar_loop_moody_122_Cmin.wav

Tempo and key in the name are the most valuable part, because they decide whether a loop fits a track before you ever press play. Most commercial packs already write them; keep them when you rename. Software can read them too: Adam Studio takes the tempo, key and instrument a file already carries in its name.

Why keep loops and one-shots apart?

They are used in opposite ways. A loop runs by itself and has to match the track’s tempo and key. A one-shot is a single hit or note that fires when something tells it to: a pattern, a pad, a key. Mixed together, you waste time auditioning four-bar loops when you wanted a single clap. Inside each instrument folder, a loops and a one-shots subfolder is enough.

How do you keep a sample library tidy for good?

• One root folder. Everything lives under it, so a backup, a move to a new computer, or a scan is one folder, not twenty.
• An inbox. New downloads land in _inbox and get sorted in one sitting, not dragged straight into the library.
• Prune on arrival. If you would never use it, do not keep it. A smaller library you trust beats a bigger one you avoid.
• Keep the licence. Leave each pack’s licence file next to its sounds, or note where it came from. Rules differ; the free sample map shows how much.
• Back it up. A library is years of collecting. One external copy is the minimum.

Can software organize a sample library for you?

Yes, and it does not have to move anything. Adam Studio’s library scan works on the folders you already have: choose a folder (packs inside packs are fine), press Analyze, and it reads every file’s instrument, tempo, key, and whether it is a loop or a one-shot, then files it into the eight folders above. The filing is Adam’s own index; your files stay exactly where they are. With an AI key connected, the scan also reads each sample’s genre and style from closed lists, so a search for a style means the same thing across every pack.

A few details that matter in practice:

• It reads wav, aif, mp3, flac and ogg. Apple Loops in .caf are not read.
• Only file names ever leave your computer, and only to the AI company whose key you entered. No audio is uploaded.
• It runs in the background while you play, and every folder you feed it gets a chip, so you can look at one pack at a time or take it back out.
• If it read a file wrong, you can correct it in the table on the AI tab, and your correction wins over any later scan.

Then the index does the job a folder tree cannot: when you type an idea and press CREATE, Adam casts each part from the whole library at once and gives every player a crate of up to ten matching samples. The tidy library becomes something you play. There is more on that in making beats from your own sample folder.

Questions people ask