Programming Trance Arpeggios That Drive the Track (Not Just Fill Space)

Most trance arps sit in the mix like wallpaper — a 16th-note plucky thing chugging under the pads, adding energy in theory and doing nothing in practice. The good ones do the opposite: they tell the listener where in the phrase they are, they set up the drop before the drop arrives, and they become the part people hum on the way home. Getting there has almost nothing to do with which preset you pick. It’s about how you sequence the notes, how you gate them, and how you let the arp fight — or duck — the rest of the track.

TL;DR

• Use the built-in arpeggiator to sketch, then print to MIDI and edit by hand. Every good trance arp is a written line.
• Break uniform 16ths with one sustained note per bar — that single move separates “composed” from “computed”.
• Gate defines sub-genre: ~45% for classic plucks, 85%+ for rolling uplifting arps. Automate it across the arrangement.
• Sidechain the arp to a silent “ghost kick” in the breakdown so the pump keeps implying the four-on-the-floor.
• Layer arps across octaves with different filter movement, not different notes. Two of pitch/timbre/movement must differ, never all three.

Print the arpeggiator, then kill it

Ableton’s Arpeggiator, FL’s piano-roll arp, Logic’s Arpeggiator plugin — they’re all fine for finding a shape in ten seconds. They’re all terrible for finishing a track, because everything they generate has the same tell: uniform note length, uniform velocity, no phrasing. Any experienced listener clocks it inside four bars.

The workflow:

1. Drop the arpeggiator on a MIDI track, hold your chord. Start with Up, 1/16, 2 octaves. Play it back against the bass and pads.
2. Print it to MIDI. In Ableton, drag the clip out with the plugin active to bake the notes; in FL, right-click the pattern and use “Get MIDI file from selection” or just render to a new pattern; in Logic, use Bounce Region In Place with “Include Instrument MIDI Effects” ticked.
3. Delete the arpeggiator. You’re now editing raw notes with no plugin masking your mistakes.
4. Extend the last note of each bar so it sustains into beat 1 of the next bar. Single biggest change you can make.
5. Nudge two or three notes per bar 5–15 ticks off-grid — but nudge the same notes the same way in every bar. That’s phrasing, not sloppiness.

Once you’re free of the plugin, you can do the things that actually make an arp feel written: skipping the “and of 4” to leave breathing room, stuttering a note twice at 1/32, pulling one note down an octave for a bass answer. None of those exist in an arpeggiator’s dropdown menu.

The two-note-length rule

Thirty-two bars of uniform staccato 16ths is exhausting. Listen to any Gouryella, Airwave or Above & Beyond arp with headphones and count — there is always at least one long note per bar. The ear needs somewhere to land.

The technique is simple: keep 14 of your 16 notes short (roughly half a 1/16), and extend one or two of them to a full 1/8 or 1/4. Where you place the long note is the whole game:

• Long note on beat 1 → grounded, anchored, big-room feel.
• Long note on the “and of 2” → syncopated, pushes the phrase forward.
• Long note on beat 4 → tension, sets up the next downbeat.
• Long note on the last 16th → carries across the barline, gives you the flowing uplifting feel.

Shift the long note every two bars and your 4-bar loop suddenly has internal shape. Push it further across eight bars: bars 1–2 anchor on beat 4, bars 3–4 shift to the “and of 2”, bars 5–6 return home, bars 7–8 go all-staccato as a mini-build. You’ve written an arrangement inside a single arp.

Velocities matter as much as lengths. Never leave everything at 100. A rough template: 100 / 80 / 100 / 90 across the 16ths, with the pattern accents pushed to 110–120. Then route velocity to filter cutoff on the synth, modestly — accents crack the filter open a little further and the arp instantly breathes.

Gate is the genre switch

Gate — how much of each note’s duration sounds before the next one starts — is the single control that turns the same notes and the same synth into uplifting trance, psy, or tech-trance. Everything else is dressing.

If you’re programming by hand, gate is just note length. If you’re using a step sequencer, it’s usually the knob labelled Gate. The rough map:

• 30–45%: Tech-trance and progressive stabs. Lots of air between notes; reverb tails do the gluing.
• 45–60%: Classic pluck. Enough decay to hear the pitch, enough silence for the next note to punch.
• 60–80%: Modern uplifting. Notes almost touch. Add a touch of glide and it fills out.
• 85–100%: Rolling/legato lead. Notes overlap. Switch the synth to mono with 20–40ms portamento for the sliding sound.

The move most producers miss: gate isn’t a fixed setting for the whole track. Automate it. Open to 90%+ in the breakdown for the legato, emotional feel; close back down to 55% at the drop so the arp punches between the kick and bass hits. One automation lane, huge arrangement payoff.

The amp envelope release is doing part of this job too. Short release (20–50ms) tightens up low-gate patterns and keeps them percussive. Long release (200–400ms) smears high-gate patterns into a pad-like wash — useful for fading the arp in from silence at the start of a breakdown.

Beyond root-5th-octave

Every trance tutorial teaches root, 5th, octave. It works, and it’s why every beginner arp sounds like every other beginner arp. Three ways out:

Add the 7th. In A minor: A, E, G, A. Suddenly wistful instead of triumphant. This is the interval that separates the emotional ASOT-era leads from the polite ones.

Use a non-chord tone as a passing note. Root, 5th, 6th, 5th — in a minor key the 6th sits a semitone above the 5th and creates a beautiful rub. For a darker mood, try root, ♭6, 5th, octave.

Write contour, not scales. Instead of climbing predictably, sketch a shape — down, up, up, down. The arp becomes a mini-melody that happens to imply the chord. That’s how you get earworms instead of texture.

A worked example in A minor. Bar 1: A3, E4, G4, E4, A3, C5, E5, C5. That’s not up-down-up-down, it has a shape. Bar 2 keeps the rhythm but moves under an F major chord: F3, C4, E4, C4, F3, A4, C5, A4. The listener hears a line moving over changes, not an arpeggiator running.

Browse Trance packs at Myloops →

The ghost-kick sidechain

Sidechaining the arp to the kick in the drop is table stakes. The trick most people miss is doing it in the breakdown — when there is no kick at all.

Set up a hidden trigger channel: an empty MIDI track with a kick sample routed to a bus that goes nowhere audible. Program a four-on-the-floor into it. Feed that bus into the sidechain input of a compressor on the arp. During the drop, real kick and trigger kick are in unison, so you get standard pumping. During the breakdown, the real kick drops out but the trigger keeps firing, so the arp keeps pumping in time with the kick that isn’t playing.

Two things happen:

1. The listener’s brain fills in the missing kick because the pump implies it. Emotional payoff lands twice as hard when the real kick finally returns.
2. The arp keeps moving while everything else goes static, so the breakdown doesn’t turn into a puddle of pads.

Compressor settings: ratio 4:1 to 8:1, attack as fast as the plugin allows (0.1–1ms), release dialled to the tempo. At 138 BPM a quarter note is about 435ms, so a release somewhere in the 80–150ms range gives a clear pump that recovers before the next hit — start at 100ms and tune by ear until you can see the gain reduction meter fully return to 0 just before each trigger. Threshold set for 6–10dB of reduction on peaks.

Volume-shaper plugins (LFO Tool, Kickstart, ShaperBox) do the same job with a drawn curve and no routing. Same principle: shape it to the kick pattern and leave it running when the kick is gone.

Layering without turning it to mud

One arp is fine. Two arps done right is what separates a demo from a release. Two arps done wrong is a frequency traffic jam at 400Hz.

The rule: your two layers must differ on at least two of these three axes — pitch range, timbre, filter movement. Never all the same. Never all three different, or they stop sounding like one instrument.

A reliable stack:

• Layer 1 — main arp. Supersaw, 5–7 unison voices, moderate detune, filter opening over 8 bars. Lives roughly 400Hz–4kHz. This is the layer you actually hear.
• Layer 2 — sub arp, octave down. Same MIDI transposed down. Different patch — square or a duller saw, low-passed hard around 800Hz. Sits 6–10dB below the main. Adds body, not notes.
• Layer 3 (optional) — pluck accent, octave up. Triggered only by high-velocity notes (above 100). Bright, short decay, high-passed at 1kHz. Almost a pitched hi-hat.

EQ them out of each other’s way. High-pass the main at 200–300Hz. Low-pass the sub around 700–900Hz. That leaves a clean handoff in the 300–500Hz zone where you can scoop a dB or two on the main to make room for the sub. The top-octave pluck lives above 1kHz and doesn’t need to fight anyone.

Panning: main centre, sub centre (low-mid information stays mono or you lose punch on club systems), top-pluck widened with a stereo tool or duplicated hard L/R with 8–12ms of delay on one side for a ping-pong sparkle.

Filter automation is the arrangement

A timbrally static arp is background. A filter that moves across the build is the build. Everyone knows the slow low-pass sweep works — the reason it works is worth pulling apart.

1. Sixteen bars before the drop, cutoff nearly closed. You should barely hear the arp — more a muffled thump than a note.
2. Automate the cutoff up to roughly 60% open over the first 8 bars. S-shaped curve, not linear — humans hear the acceleration.
3. Bars 9–15, ramp faster: 60% to 85%. This is where the ear starts leaning in.
4. Last bar of the build, snap fully open. This is the reveal.
5. In the drop itself, drop the cutoff back to 75–80% so the arp doesn’t fight the main lead. Fully open again halfway through the drop for the second peak.

Automate resonance alongside cutoff. Start around 20%, push to 40–50% at the top of the build (bars 14–15), pull back to 25% in the drop. Resonance during the build adds the whistling top that pulls the ear forward; too much in the drop and it turns aggressive fast.

Pair the sweep with reverb send automation — dry at the start of the build, ~30% wet at the peak, back to 15% in the drop. High-pass the reverb return at 800Hz so the tails don’t wash out the low end.

Browse Trance packs at Myloops →

When to break the 16th-note grid

Straight 16ths isn’t a rule, it’s a default. Some of the most memorable trance sequences break the grid on purpose.

Dotted 8ths. Notes every three 16ths. Three-against-two feel over the 4/4 kick — hypnotic, not confusing. Layer a dotted-8th delay on top and you have the classic dub-trance sequence sound.

The 3-3-2. Group eight 16ths as 3+3+2 instead of 2+2+2+2 — hits on beat 1, the “and of 2”, and beat 4. It’s the tresillo, and it’s the rhythmic backbone of most modern melodic house and progressive trance because it feels danceable without being obvious.

Silence as rhythm. Program 16 slots, fill 9 or 10. The gaps become the groove. This is how psy and tech-trance basslines carry their weight — the missing notes are as important as the played ones.

Polyrhythm across layers. Main arp on straight 16ths, second layer on a repeating 5-note pattern. They phase against each other and lock back up every 5 bars. Sounds like clever composition, is basically free.

Whichever you use: audition the rhythm against kick and bass in isolation. If the arp groove sounds worse without the kick, dropping the kick back in won’t fix it — it’ll just mask it.

Getting the arp and bass to talk

Beginners program arp and bass on the same rhythmic grid and wonder why the low end feels weak. When both parts hit every 16th, they mask each other and the bass loses its punch. Complementary rhythm is the whole game — arp plays where the bass doesn’t, and vice versa.

Standard trance bass pattern: off-beat 8ths — the “and” of every beat. That leaves the downbeats and the odd 16ths free. Your arp can hit on-beats and even-numbered 16ths without stepping on the bass.

If your arp genuinely needs to be straight 16ths, use a second sidechain — arp accents triggering a compressor on the bass with 2–3dB of reduction — so the bass steps aside for the arp’s important moments and returns immediately.

Frequency-wise: high-pass the arp at 200Hz minimum, 300Hz if the bass has real weight up top. Low-pass the bass at 250Hz for a clean split, or push to 500Hz for more character and then scoop a dB or two on the arp in the 200–400Hz region. Watch a spectrum analyser on the master through the drop — masking around 150–300Hz is where trance mixes go muddy.

Note choice matters as much as EQ. If the bass hammers the root on the offbeat, don’t have the arp hammer the root on every downbeat too. Send the arp to the 5th or the octave over root-bass moments. Two voices moving against each other reads as arrangement; one voice doubled reads as a blob.

The bottom line

A great trance arp isn’t a preset plus an arpeggiator plugin. It’s a written line — with phrasing, dynamics, deliberate gaps and a job in the arrangement. The patch is maybe 20% of it. The other 80% is note-level editing, gate automation, layered octaves and the way the arp negotiates with the kick and bass around it.

If you build one habit from this article, make it printing the arpeggiator output to MIDI immediately and editing from there. Everything else — the two-note-length trick, the ghost-kick sidechain, the layered stack, the filter build — assumes you have actual notes to shape. Preset-based arps sound like presets. Edited arps sound like songs.

Next time an arp feels flat, don’t reach for a new patch. Open the MIDI, change three note lengths, drop the velocity on half the notes, and automate the filter. Nine times out of ten the arp was fine — it just wasn’t being played the way a producer would play it.