Inside a Pro Trance Project: The Template, Bus and Colour System That Saves Hours

Open a session from a producer with a Beatport #1 and the first thing you notice is that it looks boring. Tracks are grouped, colour-coded, named like a filing system, and the mixer collapses down to maybe eight buses instead of forty. That “boring” is exactly why they finish two tracks a month while the rest of us are still hunting for the kick group at 2am.

TL;DR

• Never start from an empty session. Open a template with groups, buses, sends, sidechain, locators and a reference chain already wired.
• Lock a fixed track order — drums, bass, harmonic, leads, plucks, atmos, FX, vocals — so muscle memory replaces scrolling.
• Colour by role, not by mood. One colour per role, identical across every project you ever open.
• Mix on 6–10 group buses, not on 60 channels. The master chain is glue, not rescue.
• Bounce anything you’re not actively editing. A 30-track session finishes; a 90-track session becomes a folder of regret.

The template is the whole game

Almost every full-time trance producer I know opens the same file to start a new idea. Not a demo project with a couple of preset folders — a real working skeleton with groups, buses, sends, sidechain routing, a reference chain, and locators already dropped across the timeline. If you’re rebuilding that scaffolding every time an idea hits, you’re burning the exact twenty minutes where the inspiration actually lives.

A functional 138 BPM template contains, at minimum:

1. Empty group tracks for Kick, Clap/Snare, Hats/Perc, Sub, Bass, Chords, Pluck, Lead, Pads/Atmos, FX Risers, FX Impacts, Vocals — all colour-coded, all routed to their bus.
2. Four return tracks: short plate, long hall, dotted 1/8 delay, quarter-note delay. All sidechained to the kick.
3. A master chain doing gentle glue only — a bus comp catching 0.5–1 dB on peaks, a broad tilt EQ, then a ceiling limiter for monitoring level (not for mastering).
4. A muted reference track routed to a separate output or cue bus, bypassing the master chain entirely.
5. Locators pre-placed at bars 1, 9, 17, 33, 65, 97, 129, 161, 193 and named INTRO / BREAK1 / BUILD1 / DROP1 / BREAK2 / BUILD2 / DROP2 / OUTRO.

Save it as “TEMPLATE_138.als” or the FL equivalent. Every three or four projects, promote whatever new send, macro or utility rack keeps reappearing into the template. After a year of doing this, the template is the most valuable file on your drive — it encodes every workflow decision you’ve stopped having to make.

The track order every pro converges on

There’s a reason so many session screenshots look similar: the industry has quietly agreed on an order that works. Kick far left, then downbeat percussion, then upbeat percussion, then sub, then bass, then harmonic content from low to high, then FX, then vocals last. Obvious — until you notice how many hobbyist projects have the kick sitting in track 14 because that’s where it was dragged in.

Fixed order pays off three ways. At 1am when you want to duck pads under the lead, your hand already knows where to reach. When you’re comping a riser across a breakdown, you don’t scroll. And when you open the project six months later to bounce stems for a label, everything is where a sane person would expect it.

The order I use and see repeatedly in pro sessions:

• Kick → Kick Layers → Clap → Snare → Snare Roll → Closed Hats → Open Hats → Perc Loop → Perc Hits
• Sub → Rolling Bass → Mid Bass → Reese
• Chord Stab → Chord Pad → Piano/Bell
• Main Lead → Counter Lead → Pluck 1 → Pluck 2
• Atmos Pad → Noise Bed → SFX Loops
• Uplifter → Downlifter → Impact → Reverse Crash → Sub Drop
• Vocal Lead → Vocal Adlib → Vocal Chop

Stick to it even when you’re improvising. The moment a new synth reveals what role it’s playing, it goes into the right group — not “I’ll tidy this later.” You won’t tidy it later.

Colour coding that actually means something

Colour is not decoration. Used properly it lets your eye parse a 60-track arrangement in a second and a half. The trick is to code by role, not by vibe. If your kick is red today and orange next week, colour is doing zero work for you.

A system that holds up across hundreds of projects:

• Red — kicks and low-end drums
• Orange — claps, snares, top-loop drums
• Yellow — hats and shakers
• Deep purple — sub and bass
• Blue — chords, pads, harmonic beds
• Cyan — plucks, arps, bells
• Green — leads
• Grey — FX, risers, impacts
• Pink — vocals
• White — reference and utility

Bake it into the template so you literally can’t forget. When clips and automation lanes inherit the group colour, the arrangement view starts to read like sheet music — the shape of the track becomes visible before you’ve pressed play.

Mix on eight faders, not eighty

The biggest single workflow upgrade for intermediate producers is committing to a real bus structure. You do not mix a trance track on 60 individual channels. You mix on the group buses and only dive into individual tracks to fix specific problems.

The routing I run on almost every project — treat the numbers as starting points, not gospel:

Once this exists, mixing collapses into a manageable task: balance the eight buses against each other, then dip into a group only when something specific bothers you. The master chain sits on top doing glue work — never damage control.

Browse Trance packs at Myloops →

Naming that survives a stem export

“Serum 3”, “Serum 3 copy”, “Audio 12”, “New Audio 4” — every label A&R has opened that project and quietly moved on. Naming isn’t about tidiness. It’s about being able to hand your stems to a mix engineer or a co-writer without a two-hour explanation call.

The convention I’ve found bulletproof:

• ROLE_Descriptor_Detail — e.g. “LEAD_Supersaw_Main”, “BASS_Rolling_Sylenth”, “FX_Riser_Break1”.
• Uppercase role prefix so it jumps out while you’re scrolling.
• Never leave a track named after its plugin. “Serum” is not a role.
• For stacked layers, number from the bottom up: “LEAD_L1_Sub”, “LEAD_L2_Body”, “LEAD_L3_Air”. Anyone rebuilding your stack knows instantly what’s what.
• Sample tracks: the track name is the role, the original filename lives in the info/comment field.

When you bounce stems, these names map directly onto the exported files. A mix engineer opening “LEAD_L2_Body.wav” already knows what to do with it. “Audio 14.wav” tells them nothing except that they should charge you more.

Locators: turn the timeline into a map

Trance is a genre built on 32-bar blocks. Your session should reflect that visually before you write a single note. Drop locators at bars 1, 9, 17, 33, 65, 97, 129, 161, 193 and name them INTRO, BREAK1, BUILD1, DROP1, BREAK2, BUILD2, DROP2, OUTRO. You’ll deviate — plenty of great tracks live at 40 or 48 bar drops — but the skeleton means you’re never lost in the timeline, and jumping between sections is one keystroke instead of a scroll-hunt.

Three habits that compound:

1. Alternate locator colours between drop and breakdown sections so the timeline itself has visual rhythm.
2. Park a “PRINT” locator at bar 250 or so where bounced stems and rough renders live inside the project.
3. Keep a muted “NOTES” text clip on the top track for tempo maps, key changes, vocal timing quirks — anything you’d forget in a week.

Producers who work fast rely on the timeline as a map. If yours is a blank strip with clips scattered across it, you’re navigating blind every time you open the file.

Four sends, used everywhere

Instead of loading a fresh reverb on every synth, commit to a fixed send bank. Four returns cover roughly 95% of trance production, and the discipline of sharing them is what makes a mix cohere.

• Send A — Short Plate. Around 0.8s decay, 20 ms pre-delay, HPF around 400 Hz. Plucks, vocals, snares.
• Send B — Long Hall. 3–5s decay, 40–80 ms pre-delay, HPF around 500 Hz, LPF around 8 kHz. Pads, breakdown leads, atmospheric depth.
• Send C — Dotted 1/8 Delay. Around 30% feedback, band-passed roughly 400 Hz to 6 kHz. The classic trance delay.
• Send D — 1/4 Delay. For lead calls and vocal throws, with a light chorus after the delay for movement.

Sidechain the returns to the kick — even 2–3 dB of ducking keeps the tails from clogging the low-mids on every downbeat. And automate the send amount, not the return fader; that way the reverb tone stays consistent while individual elements move deeper into space during breakdowns.

Why this matters: reverb tone is one of the strongest cues for a track’s sense of space. When every element shares three or four verbs, the mix glues naturally. When every synth has its own random reverb, the mix sounds like a collage of demos.

Freeze, bounce, commit

A pro trance project mid-arrangement should not have 90 live plugin instances running. Twenty active tracks, sixty frozen or bounced. Two reasons.

First, headroom. Diva runs in true-analogue mode by default in a lot of templates, Omnisphere loads a full multi per instance, and a heavy Serum patch with 256-sample unison and oversampling will happily eat a core on its own. Freeze them and the CPU vanishes.

Second — and this matters more — mental commitment. Once a lead is printed to audio, you stop A/B’ing preset variations and start making arrangement and mix decisions. This is the single biggest reason bounced sessions get finished faster than live-plugin sessions.

My rule: when a synth part is arranged and I like the sound, I bounce it in place and stash the MIDI + preset on a hidden, muted track prefixed “SRC_”. If I hate it in a week, the source is one click away. Nine times out of ten I don’t hate it, the project stays light, and the mix decisions stop being negotiable. By the time you’re at final mixdown you should be looking at twenty-something audio tracks routed to eight buses. That is a mix you can finish. Ninety live synths is a project you can only abandon.

The reference track, done right

Every serious producer keeps a reference muted in every project. Not to copy it — because ears drift badly over a six-hour session, and a known-good sound one click away is the only reliable calibration.

• Route the reference to a return that skips your master chain entirely, or send it to a separate interface output feeding your monitor controller. Never let it hit your bus comp and limiter.
• Trim its gain so its loudest section lands roughly where your track’s loudest section will — for club trance that’s usually around -8 to -10 LUFS short-term. Level-matching is the whole point; louder always sounds better.
• Keep two or three references, not twenty. One for kick and bass tone, one for arrangement energy, one for overall mix balance.
• A/B every twenty minutes or so. If it’s been an hour since you last checked, you’ve probably drifted somewhere weird.

Producers who skip this end up with mixes that sound massive on their own monitors and thin on every other system. The reference isn’t a crutch, it’s a reality check.

Browse Trance packs at Myloops →

The folder structure nobody teaches

Organisation doesn’t stop at the DAW. The folder layout on your drive decides whether you can pick a project up in two years — or whether you open it and half the samples are missing.

Always run Collect All & Save (Ableton) or the equivalent packaging step (FL’s Zip Loose Files, Logic’s Consolidate, Bitwig’s Pack Project) before closing anything you care about. Samples referenced from your main library will break the moment you reorganise that library — collecting them into the project folder makes the file self-contained forever, and turns the project into something you can archive, share, or resurrect years later without a single Media Missing dialog.

The bottom line

The difference between a pro trance project and an amateur one usually isn’t the synths, the samples or the melodies. It’s that the pro finds every element instantly, mixes on eight buses, hands off clean stems, and reopens the file two years later without a single missing-sample warning. That’s not talent. It’s a system, built once into a template and refined over hundreds of sessions.

Copy someone else’s system if you have to. Pick a track order and stick to it for a month. Set up your buses and sends in a template today. Rename every track in the next session you open with a real role prefix. None of it is glamorous, and none of it will show up in the final master — but every hour you save hunting for the hat group is an hour that goes back into the actual music.

The producers finishing tracks aren’t the ones with the best plugins. They’re the ones whose projects are boring to look at and exciting to listen to. Build your sessions that way from day one and finishing stops being the hard part.