Building a Trance Template in Logic Pro From Scratch

You open Logic, hit “Empty Project,” and forty minutes later you have a tempo, a kick channel, two buses and no music. The idea you had in the shower is gone. This is not a discipline problem — it’s a design problem. You are re-making the same twenty decisions every single time.

A template freezes those decisions. This post walks through building one for trance: project settings, channel skeleton, gain staging, send FX, sidechain routing, arrangement markers, and the rules that keep the template from turning into bloat.

Why a Template Exists: Killing Decision Fatigue

A template is not a preset pack. It is a container of decisions you already made and never want to make again: what sample rate you work at, where the reverb lives, how the kick ducks the bass, what your bus colors mean.

The measurable goal is simple. From double-clicking the template to hearing the first sound should take under sixty seconds. If it takes longer, something in the template is unfinished. Everything below is judged against that number — not against how impressive the mixer looks.

Project Settings: Tempo, Sample Rate and Grid

Set the tempo to 138 BPM. You can change it per project in two seconds, but starting from a real trance tempo means your delay times, LFO rates and sidechain releases are already in the right neighborhood.

Under File > Project Settings > Audio, set the sample rate to 44.1 kHz. Under Recording, set the bit depth to 24-bit. 44.1 kHz is the distribution target for every streaming platform and every club playout system; recording at 96 kHz only to resample down doubles your CPU load for a synth-based genre with almost no acoustic capture in it. 24-bit gives you the noise floor headroom that matters.

Time signature 4/4, and set your grid to think in 8-bar blocks. Trance phrases are 8, 16, 32 bars. Set the Cycle area to 8 bars at bar 1 so loop playback starts correct.

Turn Smart Tempo off — set the project mode to “Keep” rather than “Adapt.” Smart Tempo exists to follow the tempo of material recorded without a click. In a genre where every element is generated on a fixed grid, it adds an analysis pass to every imported file and occasionally flex-times a sample you never asked it to touch.

Channel Skeleton: Signal Layout With Track Stacks

Six Summing Stacks: Drums, Bass, Leads, Pads, FX, Vocals. Each stack gets its own bus, each bus goes to the stereo output. Nothing hits the master directly.

Naming beats color. Color tells you which group a channel belongs to at a glance; it does not tell you which of your four pad layers is the one with the filter sweep. Use a prefix convention and stick to it: DR Kick, DR Clap, DR Ride, BS Sub, BS Rolling, LD Supersaw A, PD Wide. When the project hits sixty channels, the search field in the Mixer becomes your primary navigation tool, and search only works on disciplined names.

Color the stacks, not the children. Six colors is a legend you can hold in your head; twenty is noise.

Gain Staging: Headroom Before the Master

Target roughly -18 dBFS RMS on each individual channel. Aim for peaks around -6 dBFS on the group buses. The master gets a metering plugin only — no limiter, no “mastering chain” sitting in the template.

The reason for the empty master is that a limiter in the template lies to you. You stop hearing the buildup of level across the arrangement because the limiter is absorbing it, and by the time you remove it for the real master, the mix is already stacked 4 dB too hot.

Correct levels with a Gain plugin in the first insert slot, not with the fader. The fader is your automation lane. If you use it for static level correction, every fader automation you write later is offset from the position you carefully set, and rebalancing a group forces you to rewrite automation instead of nudging one number. Put Gain first, then EQ, then everything else.

Send FX: Two Reverbs, Two Delays, One Rule

Four send buses, created once, present in every project:

• Short plate, roughly 1.2 s decay — for drums, plucks, anything that needs body without tail.
• Long hall, 4–6 s decay — the breakdown reverb.
• Dotted 1/8 delay — the trance delay. At 138 BPM this is the one that makes plucks move.
• 1/4 delay — wider, slower, for lead stabs and vocal throws.

On every send bus, put a high-pass at 200–300 Hz and a low-pass at 8–10 kHz before the reverb or delay. Low-frequency content in a long reverb turns the mix to mud faster than anything else, and uncontrolled highs in a tail make the reverb sound like a separate, brighter track sitting on top of the mix.

The rule: no insert reverbs. Not because of CPU — modern machines don’t care. Because a mix sounds like one room when everything shares the same reverbs. Ten channels with ten different insert reverbs sound like ten recordings glued together. Sends force a common space, and the amount of that space becomes a single automatable number.

Kick and Bass: Baking Sidechain Into the Template

Route the kick to a dedicated bus in addition to its normal output — a silent trigger copy. In Logic: on the kick channel, add a send to an unused bus, set that send to 0 dB and set the bus’s aux output to “No Output.” The aux now carries the kick signal but produces no sound.

On the bass channel, insert Compressor, enable the side chain, and select that trigger bus in the Side Chain dropdown at the top right. Now the bass ducks to the kick even when you mute the kick for a test — the trigger is independent of what you hear.

Starting values that make sense at 138 BPM: ratio around 4:1, attack as fast as the compressor allows (0–1 ms) so the duck begins on the transient, threshold set so you see 4–6 dB of gain reduction on each hit. Release is the number that matters. At 138 BPM a quarter note is roughly 435 ms; a sixteenth is roughly 109 ms. Set release so the bass has fully recovered before the next kick lands — typically somewhere between 100 and 250 ms for a four-on-the-floor pattern. If release runs longer than the gap between kicks, the bass never returns to full level and the low end sounds thin and pumping rather than tight.

The alternative is a volume shaper: a repeating envelope drawn over one beat, applied to the bass channel. Use the compressor when you want the duck to respond to the actual kick — different kick layers, variations, fills. Use the shaper when you want the exact same curve every bar regardless of what the kick does, which is usually the case in the drop. Keep the compressor in the template; the shaper is a per-track decision.

Arrangement Skeleton: A 7-Minute Structure With Markers

Drop a marker set into the template so the timeline is never blank:

That is 256 bars — a little over seven minutes at 138 BPM, which is the DJ-friendly length the genre expects. The 32-bar intro and outro exist for mixing, not for listening.

Markers do more than label. Looking at a labeled timeline turns “what should I write” into “what goes in bars 65–128,” which is a decision you can actually make. Leave the Cycle area on the first 8 bars of the drop — that’s where you’ll spend most of your programming time. Leave a tempo automation point at the start so you don’t have to create the track when you decide the breakdown should ride at 136.

Instrument Presets: Supersaw, Pluck, Rolling Bass

Three starting patches carry most of a trance track:

• Supersaw lead — Alchemy or Retro Synth, saw oscillator, 7 voices of unison, detune in the 20–30 cent range, slight stereo spread. This is the genre’s signature sound.
• Pluck — short amp envelope, decay around 150–250 ms, filter envelope tracking the amp envelope, resonance modest.
• Rolling bass — 1/16 gate pattern, filter cutoff low, short release so notes stay separated.

Save these as Patches in the Library, not as loaded instruments inside the template. A template with instruments pre-loaded takes longer to open, and the moment a patch depends on a third-party plugin or a sample library, the template stops being portable — a fresh machine or a reinstall gives you a project full of “plugin not found.” Patches load in two clicks and travel independently.

Saving the Template and Versioning It

File > Save as Template. Logic writes to ~/Music/Audio Music Apps/Project Templates/, and your template appears in the “My Templates” section of the startup dialog. That folder is part of the Audio Music Apps directory — if your backup strategy skips it, you lose your template along with your channel strips and patches. Back it up or sync it; iCloud Drive works, but verify the file actually exists on a second machine before you trust it.

Version with a date stamp: Trance 138 — 2025-03.logicx. Keep the previous one. When a change turns out to be wrong two months later, you want the old file, not your memory of it.

The discipline rule: only update the template at the end of the month. Every project produces the urge to “quickly fix” the template mid-session. That urge is how templates accumulate half-finished chains that were right for one track. Write the change down, batch it, apply it once.

Where the Template Slows You Down

A bloated template hurts in two ways. It takes longer to open, and — worse — unused channels are mental noise. Scrolling past fourteen empty percussion tracks to find the one you need costs attention every time you do it.

More than 40 channels is usually waste. A typical working trance template lands somewhere around 25–35 channels: six to ten drum tracks, two or three bass channels, three or four lead and pad tracks, four send buses, six group buses, and a handful of FX and automation lanes. Everything beyond that tends to be channels added “just in case” during one project and never removed.

Review the template every third project and delete channels you never opened. The ones that usually go first are duplicate percussion layers, a third or fourth reverb send that only ever got used once, and vocal channels in an instrumental workflow. Deleting a channel you might need someday costs you fifteen seconds when that day comes. Keeping it costs you attention on every session.

What To Do Next

Open an empty project today. Build only the six Track Stacks and the four send buses, set the tempo, drop the markers, save it as a template. Load no instruments and no samples. That version is enough.

Start your next three tracks from it and keep a note of every channel, plugin or routing you add by hand. At the end of the month, look at the notes: anything that appears in all three goes into the template. Anything that appears once does not. That list — not a tutorial — is what your second version should be built from.