Welcome back. This is an advanced workflow lesson on folder hygiene for samples, specifically if you’re chasing that 90s rave and jungle DNA inside modern drum and bass production.

And I’m going to frame this the way pros actually use samples: like orchestration. Not just “I found a cool break.” More like: I can reliably find the right break, the right stab, the right siren, in ten seconds, at the right tempo, with the right grime, and I know exactly where it came from and what I did to it.

Because the fastest way to kill momentum in a session is the classic: “Wait, which Amen is this?” Or, “Where did that snare come from?” Or worst of all, you open an old project and none of the samples mean anything anymore.

Today we’re building a system: raw to processed to exports. With naming that survives huge libraries. With a resampling pipeline so your best finds become your personal canon. And we’ll do it with stock Ableton tools, so it’s portable and repeatable.

Alright. Let’s build the ecosystem.

First concept: you need a single source of truth folder. One master root on a fast drive. SSD if possible. And you decide that this folder is law. Not Ableton. Not random downloads. Not “I’ll just grab it from this old project.” One place.

Call it something like: AUDIO_LIBRARY, then inside that, DNB_90s_Rave.

Inside, you’re going to separate three worlds.

World one is INBOX. This is where everything new lands. Downloads, renders, phone recordings, sample trades, whatever. If it’s new, it goes there. And here’s the discipline: nothing gets used in a real project until it’s sorted. This single rule prevents the slow decay into chaos.

World two is RAW. This is sacred. Raw stays intact forever. You do not overwrite raw. You do not “fix it quick.” You do not normalize and replace it. Think of RAW like source code: immutable. If RAW changes, all your old projects become archaeology.

World three is PROCESSED. This is your sound. This is where your resampled, conditioned, edited, tempo-ready assets live.

Then a fourth category that people forget: EXPORTS from projects. These are bounces that are project-specific. Sometimes they’re gold, but they’re not automatically library assets. You can promote them later.

So in practice, you’ll have folders like raw full breaks, raw break hits, tops loops, one-shots by type, rave stabs, hoovers, vox, sirens, impacts, atmos. Then in processed you’ll have things like chopped breaks at 170, resampled distorted breaks, resampled stabs, processed vox, processed drum hits.

And I want you to add a docs folder. Not optional. Put a simple text file in there describing your rules: your naming tokens, your pack codes, your loudness target. Because Ableton’s browser database is amazing until you move drives or rebuild your system. That doc is your human-readable map.

Now do the Ableton step: add this root folder to Places in the Browser. That way you’re not hunting through the OS. This becomes a first-class instrument.

Next, naming. This is where advanced people either become unstoppable or they quietly suffer.

Your file names should answer four questions immediately:
What is it?
Where is it from?
What’s the tempo or feel?
And what processing is baked in?

Use a consistent format. Type, then source or pack code, then a descriptor, then BPM or key if relevant, then process token, then version number.

So for example: BREAK_Amen_Full_165_Raw_v01.
Or BREAK_Think_ChopA_170_HPResamp_v03.
Or STAB_RaveKeys_Minor9_Fm_TapeCrush_v01.
Or VOX_1234GetOnIt_170_BandpassDub_v04.

And here’s an advanced micro-rule that makes this system actually trustworthy: if you can’t explain the change in three to ten characters, it’s not a stable library asset yet. Tokens like HP180, BP1k, Clip, Tape, MonoSub. Short, searchable, consistent.

Also, bake in provenance without clutter. Use pack codes. For example, RDAT for unknown source, VINL for a vinyl session rip, CDRJ for an old CD comp, REIS for your own resample chain. That way you can remember where something came from without a paragraph in the filename.

Now let’s talk about INBOX discipline, because this is where people pretend they’ll be organized later, and later never comes.

Set a timer once a week. Fifteen minutes. Open INBOX. Delete obvious junk. Move the rest into RAW categories. Rename as you go. That’s it. Small and consistent beats big and rare.

And here’s the mindset shift: INBOX is a gate. It’s not storage. It’s not a second library. It’s a conveyor belt.

Next, Ableton Browser workflow. The goal is auditioning speed. Because 90s rave flavor isn’t one perfect sample. It’s selection, layering, and vibe continuity.

In Live, rely on prefixes in the search bar. If you name things BREAK underscore, STAB underscore, VOX underscore, FX underscore, then searching is instant. You’re basically creating your own tagging system that works across any computer.

Turn on Auto-Preview in the Browser, and set the preview volume. This matters more than people think. If preview loudness lies to you, you pick the wrong sounds. Loud always sounds “better” in a quick audition. So calibrate it once and stop thinking about it.

Teacher tip: aim for consistency in your processed prints. Break loops can peak around minus three to minus one dBFS, roughly comparable short-term loudness across your personal library. One-shots can be slightly lower if you’re layering. You’re not mastering here. You’re making browsing honest.

Now for break digging specifically: create a dedicated audio track called AUDITION_BREAKS. Drag candidate breaks in there. Warp them. And then commit the best ones into processed. This prevents your arrangement from becoming the audition zone.

Warping defaults: for full breaks, start with Beats mode, preserve transients, and envelope somewhere around 20 to 40 as a starting point. For tonal material like stabs and hoovers, Complex Pro can work, but don’t leave it there forever. Get what you need, then resample to audio so you’re not paying CPU tax across the whole project.

Now we build the sound identity: the 90s Rave Conditioner rack.

This is where folder hygiene stops being admin work and starts being an artistic pipeline. You’re creating a consistent “treatment” that makes random sources feel like they live in the same universe.

Make an Audio Effect Rack and build a chain like this.

Start with EQ Eight. High-pass around 25 to 35 hertz to clean sub rumble. And if something’s harsh, consider a small dip in that three to six k range, but don’t do it automatically. Listen. Old rave stabs can be icepicks, but sometimes that’s the point.

Then Saturator. Analog Clip mode. Two to six dB of drive. Soft Clip on. This is the glue and density stage.

Then Drum Buss, especially for breaks. Drive and Crunch are your friends for jungle grit. Boom is powerful but it can get you into trouble fast by inventing low-end that fights your actual sub. If you do use Boom, tune it deliberately.

Then Redux for that era hint. Subtle downsample, maybe two to six. Bit reduction around ten to fourteen bits territory. Again, subtle. You’re trying to imply hardware limitations, not destroy the signal unless you want a “ruin” version.

Then Auto Filter in band-pass mode. This is your rave radio and club PA toggle. It’s also a performance tool if you resample moves.

Then Utility at the end. This is the unsung hero. Mono below about 120 hertz if needed, and gain trim to standardize loudness for browsing.

Save this rack to your User Library with a clear name and a version number. RACK_RaveConditioner_v01. Because you will change it later, and you’ll want to know which sounds were printed through which rack.

Now, resampling pipeline. This is the moment where a “cool sound” becomes a reusable asset.

Create an audio track called RESAMPLE_PRINT. Set its input to Resampling. Now you can record the output of your processing in real time. Or you can Freeze and Flatten for speed and consistency.

Use resampling record when you’re performing: filter sweeps, delay throws, manual moves. Use Freeze and Flatten when you want clean, repeatable prints.

And when you print, you categorize immediately. Not later. Later doesn’t exist. Print, name, place it in the correct processed folder, done. The whole point is to build trust.

Now break-specific hygiene, because this is where jungle libraries get messy.

One break can exist as a full loop, a one-bar, a set of chops, and a bunch of one-shots. If those live together, you’ll constantly grab the wrong thing.

So keep three tiers: Full, Chops, Hits.

Workflow: warp the full break properly first. Then slice to a new MIDI track. Use transients or sixteenths depending on the break. You’ll get a Simpler kit. Replace the default processing with your Rave Conditioner or a slightly lighter version. Then resample your chops into processed.

And I want you to consider a tempo-native split, especially if you’re deep in jungle DNA. Breaks that “like” 160 behave differently than breaks that like 175. So inside your break folders, you can split into ranges like 160 to 165, 166 to 172, 173 to 180. It sounds nerdy, but it saves warp time and preserves transients.

Next: Collections in Ableton. These are your “favorites” tags, but use them strategically.

Create a red collection for guaranteed in-set: your best breaks, your best stabs, your most reliable tools.
Blue could be dark rollers: moodier percussion and techy tops.
Green could be classic rave: pianos, hoovers, diva vox, sirens.

This is how you avoid endless browsing when you should be arranging.

Now I want to add an arrangement-minded layer to your folders. Because folders can literally make you write faster.

Have folders that map to roles: tops loops that roll for eight or sixteen bars, FX transitions like risers and downlifters, intro atmos beds like vinyl air and distant sirens, and stabs designed for call and response.

The goal is: when you open a new project, you can fill the roles. One or two breaks, one top loop, a couple stabs, a couple vox bits, a few transition FX. Without leaving your curated library. That’s how you keep momentum and consistency.

Advanced coaching add-on: QC lanes. This is huge.

Inside processed, create two folders: candidates and approved.

Candidates are fresh prints. They might be good, but they’re not trusted yet.
Approved is only sounds that have survived at least one actual tune. They worked at tempo, loudness is consistent, no clicks or DC offset, filename has enough context, and you’d happily use it again.

This stops you from auditioning “almost good” sounds forever.

Now a couple sound-design extras that really fit the 90s ethos.

Print multi-intensity versions. For a strong break or stab, make three: Lite, Core, Ruin. Lite is gentle saturation, minimal crunch. Core is your standard conditioner. Ruin is aggressive clip and redux for fills and turnarounds. This recreates that 90s performance feel where the same motif evolves across sections without changing the identity.

For vox, print pirate radio style versions. Band-pass filter, saturator soft clip, a touch of Erosion noise for grit, short bright reverb, maybe a short slap delay. Then resample. Name it like VOX something PirateBP. You will reach for these constantly.

For hoovers, print wide and mono-safe versions. Check mono with Utility. If it disappears, tame side harshness with EQ Eight in mid-side mode, or reduce stereo width before printing. Then you’ve got arrangement options instantly.

Alright, now your practice exercise. Twenty minutes. This is how you make the system real.

Pick one classic break from raw full breaks. Warp it cleanly at 170. Slice to MIDI. Then print two things: an eight-bar resampled chops loop, and a pack of ten to twenty key hits as one-shots.

Then grab two stabs and one vox from raw. Run them through the Rave Conditioner. Print them. Name them properly on export. Put them into the right processed folders immediately. And color-tag your best ones in Collections.

If you have extra time, build a quick thirty-two bar sketch: first sixteen bars filtered intro with atmos and sparse chops, then the drop with full chop pattern and a stab call and response every four bars.

Finally, the recap mindset I want you to keep.

You’re not just organizing files. You’re building a production instrument.

Raw stays immutable.
Processed is versioned deliberately.
Exports are project bounces until proven otherwise.
Candidates become approved only after they survive real usage.
Naming encodes what it is, where it came from, how it behaves, and what you did to it.
And your Ableton browser becomes a performance-ready sample launcher, not a junk drawer.

If you tell me which lane you’re aiming at, jungle tearout, happy rave, darkside, or early techstep, I can suggest a tighter folder taxonomy and two variants of the Rave Conditioner rack that match the era’s tone exactly.