Most half-finished psytrance projects don’t die because the sounds are weak. They die at bar 96, when the kick and bass have been chugging for two minutes and the producer realises nothing is actually happening. In psytrance the arrangement is the drama — no patch, no mix trick and no mastering chain will rescue a track that forgets to move.
TL;DR
- Sketch the whole track as eight 32-bar blocks before you write a note — roughly 8–9 minutes at 138–145 BPM.
- Finish the kick+bass loop before arranging. Everything else reacts to that groove.
- Add an element every 8 bars in the first half; strip one every 8 bars in the second half.
- End the first break in a beat of silence. Nothing hits harder than nothing.
- Automation of filters, reverb sends and delay feedback is what keeps a repetitive genre alive.
- The peak adds one new element, not ten. The outro belongs to the DJ.
The macro blueprint before you touch a MIDI note
Open a fresh project at your target tempo — 140 BPM is the middle of the road for full-on, 145–148 for forest and hi-tech, 138 for progressive — and drop eight arrangement markers spaced 32 bars apart. At 140 BPM a 32-bar block is about 54.8 seconds, so eight of them lands you at roughly 7:20, or closer to 8:30 with a decent reverb tail. That’s the sweet spot for DJ sets and festival play.
This is the reference grid I sketch every psy track onto before writing anything:
| Block | Bars | Approx time (140 BPM) | What’s playing | Energy |
|---|---|---|---|---|
| Intro | 1–32 | 0:00–0:55 | Atmos, FX, filtered kick from bar 17 | Low |
| Build 1 | 33–64 | 0:55–1:50 | Kick + bass + percussion + first melodic hook | Rising |
| First Break | 65–96 | 1:50–2:45 | Drums out, pads/vocal/lead, riser into drop | Suspense |
| Drop 1 / Groove | 97–160 | 2:45–4:35 | Full groove, main lead, calls and responses | High |
| Second Break | 161–192 | 4:35–5:30 | Drop the kick, keep bass or pad, tension riser | Suspense |
| Peak | 193–256 | 5:30–7:20 | Everything back in + one new lead layer or acid line | Peak |
| Outro Build-down | 257–288 | 7:20–8:15 | Strip layers every 8 bars, filter down | Falling |
| Outro | 289–320 | 8:15–9:10 | Kick + one percussion loop for DJ mixing | Low |
The block sizes aren’t sacred — plenty of great tracks run 24- or 48-bar breaks — but a first-time arrangement built on this grid finishes. A first-time arrangement built on vibes doesn’t.
Kick and bass first, arrangement second
Psytrance lives and dies on the kick-bass relationship, and arranging around an unfinished low end is the fastest way to abandon a project a week later. Get an 8-bar loop of just kick and rolling 16th-note bass sounding correct before you write anything else. The kick’s fundamental usually sits around 50–65 Hz, the bass fills the 80–200 Hz pocket, and the two should never occupy the same frequency at the same instant.
My working process for the loop:
- Pick a punchy kick with a short body — roughly 90–140 ms from transient to noise floor. Longer kicks smear into the offbeat bass and kill the roll.
- Sidechain the bass to the kick. Fast attack (under 1 ms), and set release by ear so the bass has climbed back to full level by the next 16th note. At 140 BPM that 16th is about 107 ms — start there and tune until the roll swings.
- High-pass the bass around 60–70 Hz so it stops fighting the kick’s fundamental.
- Low-pass around 180–220 Hz. Any higher and the bass will chew into your lead’s territory later.
If that 8-bar loop can hold your attention for a full minute on its own, you’ve earned the right to arrange. If it can’t, no clever arrangement move will save it — change the kick or rewrite the bass pattern before you go further.
Writing the intro: 32 bars of restraint
The intro has two jobs: give a DJ 32 clean bars to mix into, and set the emotional colour of the track. Bars 1–8 are atmosphere only — a filtered pad, a reverse cymbal, a distant vocal or a field recording. Bars 9–16 introduce one percussive element, usually a shaker or a filtered hi-hat loop, sat a few degrees off-centre. Bars 17–24 the kick enters, but heavily filtered — a low-pass around 200 Hz automated to open across the next 8 bars. Bars 25–32 the kick is fully open, and a tom fill or riser signals the transition on bar 32.
The most common intro mistake is bringing the bass in early. Don’t. The bass entry is your first big moment at bar 33; play it now and you’ve spent it. Same for the main lead — keep the intro melody-free, or hint at the melody with a texture nobody will recognise as a hook. You want the listener leaning in, wondering what the track actually sounds like.
One move that never fails: take your main lead patch, play a single sustained note, print a 4-bar reverb tail, reverse it, and drop it in at bar 29. It seeds the hook subconsciously without giving anything away.
Build 1: one new element every 8 bars
Bars 33–64 is where the track becomes a track. At bar 33 the bass slams in with the kick — this is a real moment, so leave two bars of just kick and bass to let it breathe before layering. Then:
- Bars 33–40: kick, bass, closed hi-hat on offbeats.
- Bars 41–48: open hats or shaker pattern, plus a noise sweep or ride crash on beat 1 of each 4-bar phrase.
- Bars 49–56: introduce the first melodic element — a short plucky sequence, not the main lead. Keep it living in roughly 400 Hz–2 kHz so it sits above the bass without eating the lead’s future real estate.
- Bars 57–64: add a counter-percussion layer (bongos, glitched vocal chops) and open a filter on the pluck to push tension into the break.
The rule I audit against every 8 bars: either a new element enters, an existing pattern changes, or a filter/send is moving. If nothing has changed for 16 bars, the listener has already checked out. Bar 64 needs a clear exit signal — a crash, a tom fill or a full-track downward pitch bend — because on bar 65 the drums vanish.
Browse Psy Trance packs at Myloops →
The first break: less is more, but plan the exit
Breaks are where amateur psy arrangements collapse. The kick drops out at bar 65 and the producer panics — in comes a huge lead, a vocal, four pads and a supersaw stack. Don’t. The break’s job is to reset the ear so the drop hits harder, not to stuff the silence.
A 32-bar break I keep coming back to:
- Bars 65–72: kick and bass gone. Keep the pad from the intro, add a filtered vocal or short melodic phrase. Send the pluck into a long reverb (4–6 second decay).
- Bars 73–80: state the main lead melody for the first time, half volume and heavily low-passed (cutoff around 1.5 kHz).
- Bars 81–88: open the low-pass over 8 bars; start a snare roll on bar 85 that doubles every 2 bars — 8ths, then 16ths, then 32nds.
- Bars 89–96: full riser — noise sweep, uplifter, reverse cymbal, sub drop on bar 96 beat 4. Mute everything on the final 16th note for a beat of silence before the drop.
That silence is the single most effective trick in the genre. Half a beat of nothing after 32 bars of building tension makes the drop feel twice as loud. Draw a mute automation on the master (or a stereo bus) for the last 16th of bar 96 and trust it — you’ll unmute it in the mix a dozen times before you believe it works, then leave it alone.
Drop 1: this is where the track earns its BPM
Bar 97 is the payoff. Kick and bass slam back in at full level, the main lead reveals itself, and the temptation is to lay everything flat for the full 64 bars. Don’t — the drop needs internal dynamics too, or it flatlines by bar 130.
Break the 64-bar drop into four 16-bar phrases:
- Bars 97–112: full groove — kick, bass, all percussion, main lead stated cleanly.
- Bars 113–128: main lead out, replaced by a call-and-response between two shorter melodic hooks panned hard left and right. Gives the ear a rest before the lead returns.
- Bars 129–144: main lead returns with a harmony a fifth or an octave above, plus a rhythmic FX element (glitched vocal, acid squelch) landing every other bar.
- Bars 145–160: strip the lead again. Run a 16-bar filter sweep on the bass — low-pass from about 200 Hz down to 100 Hz and back — to create a wobble that telegraphs the second break.
Ride the reverb send on the lead throughout: dry when it’s stating the melody, noticeably wetter (send up around 6 dB) when it’s a supporting texture. That single automation is the difference between a static drop and a drop that breathes.
The second break: shorter, weirder, more emotional
The second break at bar 161 runs 32 bars — half the setup of the first — because the listener already knows the track. Nothing needs reintroducing. This is your emotional peak, not your energy peak, so take a risk: introduce a melodic idea you haven’t used yet, or reharmonise the main hook over a different chord.
Structurally, drop the kick but keep the bass rolling, or the opposite — try both against the arrangement and pick the version that serves the emotion. Add a lusher pad than anything so far, a vocal phrase, or an exposed solo line. Around bar 177 start the build back, reintroducing percussion every 4 bars this time rather than every 8 (you’re accelerating toward the peak, not the drop), and land a big riser and impact on bar 192.
One arrangement move that reliably works: at bar 189, cut everything except a single pad note, let it ring for 2 bars into a large reverb, then slam the peak in at bar 193. The contrast between exposed pad and full peak groove sells the moment better than any FX sample.
The peak: add one new element, don’t rewrite the track
Bars 193–256 is the biggest section of the track and the place producers most often overreach. The peak should feel like “the drop, plus one more thing.” That one thing is usually:
- An acid line (303-style resonant sweep) weaving through the existing groove.
- A harmony layer on the main lead, panned wide with a small delay offset — 7–15 ms between left and right — to widen the stereo image without smearing the centre.
- A new percussive layer — a tribal loop, ethnic drum, or a driving tom pattern.
Reuse the 16-bar phrase structure from Drop 1 with the new element woven in. From about bar 241 onwards start pulling elements out one by one — harmony first, then acid, then the extra percussion — so by bar 257 you’re back to the core groove ready for the outro build-down.
A subtle move that pays off: automate the master bus compressor’s threshold down 1–2 dB across the peak. Everything glues slightly harder and slams slightly more, and the listener feels the “arrival” without you piling on more sounds to signal it.
Browse Psy Trance packs at Myloops →
Automation is where dead arrangements come alive
If you strip a good psy track down to raw MIDI, the note data is often boring — the same 4-bar bassline for five minutes, the same lead phrase repeated a dozen times. What makes it interesting is automation. Something should be moving every 8 bars.
The four lanes I always end up drawing:
- Bass filter cutoff. Not big sweeps — subtle 200 Hz movements over 16 bars. Adds life without changing the pattern.
- Lead reverb send. Dry on statements, up around 6 dB on tails and transitions.
- Delay feedback on FX sends. Push feedback from around 30% up to 70% into breaks, then snap it back to 30% on the drop. The delay tail smears into the break, then the drop feels dry and immediate by contrast.
- Percussion volume. Dip the shaker or hat loop by 3 dB every 4 bars and swell it back. Creates micro-breaths in the groove that the ear reads as “live”.
Draw automation after the arrangement is roughed in, not while you’re writing. Try to automate during composition and you’ll disappear into details before the structure is solid.
Transitions: three moves that always work
Every block boundary — bars 32, 64, 96, 160, 192, 256 — needs a transition, but not necessarily a big FX sweep. Three reliable moves:
The reverse tail. Print a bar of whatever element is starting in the next section, reverse it, drop it into the last bar of the current section. Instant psychological bridge, no sample library required.
The snare roll into silence. Snare 8th notes for 2 bars, 16ths for 1 bar, 32nds for 1 bar, then a 16th of silence before the downbeat. Old trick, still works.
The tom fill. Three or four toms tuned in a descending or ascending pattern across the last bar. Organic, no FX sample dependency, doesn’t get tired.
Rotate them so the track has variety: reverse tail into the first break, snare roll into the drop, tom fill into the second break, reverse tail again into the peak. Ears tire of the same transition used four times in a row.
The outro: 32 bars for DJs, not for you
The outro isn’t an artistic statement, it’s a service to DJs. From bar 257 you’re stripping elements out on the same 8-bar clock you used to add them in, mirroring the intro. By bar 289 you should be down to kick and one percussion loop — that’s what a DJ mixes their next track over. Hold that for 32 bars, then a final crash and a short reverb tail at bar 320.
Two things to check on the outro:
- Kick pattern and tempo are unchanged from the intro — no half-time flip, no cheeky tempo shift, nothing that breaks beatmatching.
- No melodic elements in the last 32 bars. Any lingering melody makes the outgoing track clash in key with whatever the DJ mixes in next.
Make the outro too musical and DJs will mix out early — nobody hears the section you were proud of. Give them 32 boring bars and they’ll play the whole record.
The bottom line
A psytrance arrangement isn’t a mystery. It’s a repeating pattern of “add for 32 bars, break for 32 bars, add more, break, peak, strip down, out.” The power of the genre comes from how ruthlessly it commits to that structure while using filter automation and transition moves to keep the surface alive. Build the eight-block skeleton first, then write parts into each block, and you’ll finish tracks instead of abandoning them at 90 seconds.
Five principles carry most of the weight: the kick-bass loop has to earn its place before anything else happens, the intro has to hold back, the first break has to end in silence, the peak adds one new element rather than ten, and the outro belongs to the DJ. Nail those and the rest of the arrangement mostly writes itself.
Print your first full arrangement, listen on headphones or in the car the next morning, and at every 8-bar mark ask: did something change? If the answer is yes every time, you’ve got a track. If not, you know exactly where to open the project and fix it.




