Welcome back. This is Folder Hygiene for Samples Masterclass, drum and bass at 170 BPM, intermediate level, inside Ableton Live. And yeah, this sounds like the boring admin part… until you realize messy samples are one of the biggest creativity killers in DnB.

Because at 170, you don’t have time to “browse.” You need to decide. Kick and snare first, then tops, then break layers, then bass and FX. If your library fights you, you audition less, you commit later, and the tune never gets to the fun part.

So today we’re building a system that makes you faster. Not just organized for the sake of it, but organized the way DnB actually gets built.

By the end of this lesson, you’ll have four things:
One: a DnB-first master sample folder with a simple hierarchy.
Two: Ableton’s Browser set up with Places and Collections so your best sounds are one click away.
Three: a “170 BPM Drum Starter” template rack, plus a repeatable break-slicing workflow.
Four: projects that actually travel properly, using Collect All and Save, so you don’t open an old session and get the dreaded “missing files” nightmare.

Alright. Let’s start with the foundation.

Step one: create a master folder structure. One location. One. Not “some stuff in Downloads,” some on the desktop, and some in random pack folders. Pick a drive and commit.

On Mac, something like Music, Sample Library.
On Windows, ideally a dedicated drive like D: Sample Library.

Inside, you’re going to create a clean, DnB-optimized structure. And here’s the main idea: keep it shallow. Three clicks max to reach what you want. If you bury snares inside ten layers of subfolders, you will stop exploring and start settling.

At the top level, make an INBOX folder. Call it 00_INBOX, To Sort.
Then your main categories: DRUMS, BASS, FX, VOCALS, MIDI, RACKS for Ableton, and a PROJECT_EXPORTS folder.

Inside DRUMS, keep it practical: Kicks, Snares, Hats and Tops, Perc, and Breaks.
Then a few subcategories that actually help: punchy kicks, subby kicks, and a layer folder for clicks and tops. For snares, tight, ringy, neuro, and maybe claps and rims. For breaks, clean, crunchy, and folders like Amen and Think if you use those constantly.

And I want you to notice the philosophy here. This layout mirrors arrangement priorities at 170. Kick and snare decisions happen early, constantly. Tops and breaks drive motion. Bass and FX come once the groove is locked. Your folders should match that reality.

Now step two: the INBOX rule. This is the difference-maker.

Any new sample pack goes into 00_INBOX. Always. No exceptions.
Do not start dragging stuff into your Kicks folder mid-session. That’s how you end up with half-sorted chaos and duplicate files everywhere. The goal is: writing time is for writing. Sorting time is for sorting.

So give yourself a routine: ten minutes, twice a week.
During that sort session, do three things.
One: delete obvious junk. Demo audio, talking intros, redundant versions you’ll never touch.
Two: move samples into your structure.
Three: rename cryptic files so they become searchable.

And quick coach tip: create a “quarantine” folder for problem files. Call it 99_QUARANTINE, Fix Later. If something has a weird sample rate, corrupt preview, nonsense name, or it’s just annoying to deal with right now, throw it in quarantine and keep writing. Quarantine protects your momentum.

Step three: naming conventions that actually help in Ableton.

Ableton’s search is only as good as the words in your filenames. So we’re going to use a format that’s boring, consistent, and extremely effective:
TYPE, CHARACTER, KEY, BPM, SOURCE.

For example:
SNARE_Tight_FSharp_170_RTRD.
KICK_Punchy_NoKey_170_SineLayer.
BREAK_Amen_Crunchy_170_Vinyl.
HAT_Closed_Bright_NoKey_170_PackX.

A few teaching notes here.
First, drums often aren’t tuned to a single key in a meaningful way, so use NoKey. Don’t invent a key just to fill the slot.
Second, BPM tags are most useful on loops like breaks. If it’s a one-shot, BPM isn’t essential, but if you’re building a 170-focused writing crate, adding 170 can still help you filter quickly.
Third, your “character” words are gold. Tight, ringy, crunchy, airy, distorted, clean. These are the words you actually think in when you’re choosing sounds.

And if you’re worried about deleting stuff, here’s a safe middle ground: use a Do Not Use marker. Prepend ZZZ_ to files you don’t like. On monthly cleanup, if it’s still ZZZ and you never rescued it, delete it with confidence.

Step four: set up Ableton’s Browser with Places and Collections.

Open Ableton Live. Go to the Browser. Under Places, click Add Folder.
Add your key folders: 01_DRUMS, 02_BASS, 03_FX, and 06_RACKS.

Now Collections. This is where the speed comes from.

Set up a color system with DnB intent. Something like:
Red for go-to kicks.
Orange for go-to snares.
Yellow for rolling tops.
Green for breaks.
Blue for bass one-shots.
Purple for FX and atmos.

Then the rule is simple. When you find a sound that survives in a real beat, right-click it and add it to a Collection. This is curation, not hoarding.

Extra coach habit: don’t tag something just because it sounded cool once at 2 AM. Tag it after it survives two different projects. Then your Collections become a proven toolkit, like a DJ crate, not a warehouse.

Now step five: build your “170 BPM Drum Starter” Drum Rack.

Create a new MIDI track and drop a Drum Rack on it. The main win here is consistency. You want muscle memory, so your hands always know where kick, snare, and hats live.

Use a classic DnB map:
C1 for kick.
D1 for snare.
D-sharp 1 for a snare layer, like noise or top.
A-sharp 1 for closed hat.
C-sharp 2 for open hat.
D-sharp 2 for ride.
Then percs above that.

Now we’ll add simple, repeatable processing chains using stock Ableton devices. The goal is not to “finish” your drums forever. The goal is to get to a solid, punchy starting point fast.

On the Kick pad, add EQ Eight first.
High-pass around 25 to 30 Hz. That’s cleanup, not tone-shaping.
If it’s muddy, dip around 200 to 350 Hz by a couple dB with a medium Q. Don’t overdo it.

Then Drum Buss.
Drive somewhere around 5 to 15 percent to add density.
Crunch at zero to ten percent if you want grit.
Boom: be careful. DnB subs are sacred. If you already have a sub bassline, too much Boom on the kick can turn the low end into soup.

Then Saturator.
Soft Clip on.
Drive one to four dB, just to thicken and control peaks.

Now the Snare pad.
EQ Eight: high-pass around 90 to 120 Hz so it doesn’t fight the kick and sub.
For crack, a small boost around two to four kHz.
For air, maybe a gentle lift around eight to twelve kHz if it needs it.

Then Drum Buss. Drive five to twenty percent depending on the vibe.
If you need more bite, either push Drum Buss transients slightly, or use Saturator soft clip for that controlled smack.

For Tops, don’t process every hat individually at first. Group your hats and rides to a bus. On that bus:
Auto Filter high-pass around 200 to 400 Hz with a gentle slope. That keeps low-end clutter out of your groove.
Glue Compressor: attack about 3 milliseconds, release auto, ratio two to one, and aim for just one to two dB of gain reduction. You’re gluing, not crushing.
Then Utility: widen to about 120 to 160 percent, but keep checking mono. Wide hats can be amazing until they vanish on a mono system.

Now save this rack into your RACKS folder, DrumRacks, with a clear name like 170_DnB_DrumStarter. And here’s an advanced habit: version your racks. If you improve it, don’t overwrite silently. Save v02, v03, and keep a tiny changelog text file so you remember what changed.

Step six: break hygiene. This is where jungle energy becomes reusable.

Take an Amen or Think break. Drop it on an audio track. Set your project to 170 BPM.

Turn Warp on.
For classic breaks, set warp mode to Beats.
Preserve Transients.
Envelope somewhere around ten to thirty to tighten the hits.

Then right-click the clip and choose Slice to New MIDI Track.
Use Slice to Drum Rack, slice by Transient.

Now rename the rack like BREAK_Amen_Sliced_170_Crunchy, and save it into your racks folder under DrumRacks, Breaks.

Here’s the teacher trick that levels this up: don’t leave the slices as a random dump.
Go into the sliced rack, and reorganize it like a playable kit.
Move the best kick-ish hits into your kick note zone.
Move ghost snares into a consistent zone.
Move hats into their zone.
The goal is that every break rack feels familiar under your fingers. That’s how you stop “auditioning breaks” and start “playing breaks.”

And arrangement tip: use sliced break energy under your clean kick and snare.
In the verse, filter the break hats and ghost notes so it’s subtle.
In the drop, bring the full break layer in for motion, while your programmed tops keep it modern and controlled.

Step seven: fast auditioning at 170 without killing the vibe.

The main rule: audition in context.
Loop an 8-bar section with your kick and snare and a basic hat pattern. This becomes your testing ground.

In Ableton’s browser, turn on Preview, set the preview volume so it matches your session, and then drag candidates directly onto the correct pad in your rack.

Give yourself a hard limit: if it’s not better in ten seconds, undo and move on. This is how you keep momentum.

Optional intermediate power move: quick A/B on snares.
Duplicate the snare chain, put two snares on two chains, and use Chain Selector mapped to a macro to flip between them instantly. That way you choose with your ears, not by memory.

Also consider creating a “170 transient test loop” in your template: kick on 1 and 3, snare on 2 and 4, steady hats. Keep it ready. Every time you audition, you’re hearing the sample in the exact same musical situation.

Step eight: stop missing files forever.

Before you send a project, collaborate, or archive, go to File, Collect All and Save.
Enable files from Places, and enable files from elsewhere.

That second option is the one people forget. And it’s the reason projects break later. Collect All and Save is basically you packing the entire song into a self-contained suitcase. No dead links.

Now, a key separation rule from a workflow perspective:
Your master library is for one-shots, curated loops, favorite breaks, go-to FX, racks, and proven tools.
Your project folder is for resamples, renders, and song-specific edits, like “my snare but pitched, layered, clipped, and printed for this tune.”
If it only makes sense inside this song, it stays inside the song folder. That keeps your master library clean and your projects portable.

Step nine: monthly cleanup. This is the maintenance that keeps the whole system fast.

Once a month, remove duplicates. Remove “maybe later” junk. Your browser is not a museum.
Aim for a curated set where you can grab about ten kicks, ten snares, twenty tops, and ten breaks without scrolling forever.

And here’s an advanced variation you can adopt if you’re ready: a two-speed library.
Make a WRITING_CRATE folder that’s small and curated. Your top 50 to 200 items.
And keep the full library as a DIGGING_ARCHIVE.
During writing sessions, you live in the writing crate. When you want to hunt for new inspiration, that’s a separate intentional activity, in the digging archive. This one change alone can make you feel twice as fast.

Okay, quick common mistakes to avoid as you implement this.
Don’t create too many categories. If you have forty hat folders, you built a maze.
Don’t sort in the middle of writing. Use the INBOX.
Don’t rely on pack folder structures. Packs are organized for marketing, not for your brain.
Don’t rebuild the same drum chains every session. Save racks.
Don’t warp breaks inconsistently across projects. If you like Beats mode with transient preserve, keep it as your default for classic breaks so your groove stays predictable.
And don’t ignore Collections. Color tags are your personal best-of list.

Now let’s do a 20-minute practice to lock it in.

Set up a new Live set at 170 BPM.
Load your 170_DnB_DrumStarter rack.
Choose two kicks: one punchy, one subby layer.
Choose three snares: tight, ringy, neuro.
Choose six tops: closed, open, ride, shaker, and two extras.
Then color-tag one kick and one snare into your go-to Collections, but only if they actually work.

Add one break, warp it with Beats, transient preserve, envelope ten to thirty.
Slice to Drum Rack.
Rename and save it properly as a break rack.

Then write an 8-bar loop:
Bars one to four: clean programmed drums and light tops.
Bars five to eight: add sliced break hats and ghost notes, and make a fill on bar eight.

Don’t export. The win is speed and organization, not perfection.

Let’s recap the big idea.
Your sample library should reflect how DnB is built: kick and snare, tops, breaks, bass, FX.
Use an INBOX, sort on a schedule, and keep folder depth sane.
Name files for search.
Use Places and Collections to curate proven winners.
Save Drum Racks and sliced break racks so you stop reinventing the wheel.
And lock projects with Collect All and Save so nothing breaks later.

If you want to go one step further after this lesson, build the homework challenge: a Zero-Scroll Writing Crate for 170 BPM. Ten kicks, ten snares, twenty tops, ten breaks, ten FX, all ready-to-use. Add it to Places. Time yourself building a starter loop three times, and try to cut your time by 20 percent by the third run.

When you’re ready, tell me your current top-level folder names, or describe what’s in your Ableton Places and Collections. I’ll help you decide what to merge, what to rename, and what belongs in a writing crate versus the archive, without breaking your existing projects.