Engineering Multiple Peaks in a Headline Set

You've run a set before. You know the shape: open low, build steady, land your peak somewhere past the halfway mark, then ease it out. That arc works — it's the shape most planning guides teach, including ours, and for a 45–90 minute slot it's usually all the room needs.

Then you get booked for something bigger — a proper headline slot, 90 minutes or two hours, the only name on the poster. You reach for the same single-peak shape and something goes wrong. Either the room falls off a cliff after your big moment with 40 minutes still to fill, or you never quite let it peak at all, rationing energy across too much time until the whole set sits at the same medium simmer. Neither is a planning failure exactly — it's a scale failure. The framework you learned was built for one climb. This slot needs two or three.

One peak is a beginner's arc

The single-peak model still does its job at 45–90 minutes — the “beginner” in this heading is about scope, not skill. Our own DJ set planning guide is the foundation this article builds on: anchor track, build, one peak around the 55–70% mark, one landing. If you haven't run that framework at least once, start there — everything below assumes you already know what an anchor track is and roughly how a build works.

The problem is runtime, not skill. A single peak gives a room one moment to remember and maybe 15–20 minutes either side of genuine intensity around it. Stretch that same shape across 90 or 120 minutes and one of two things happens. You hit your peak on schedule and spend the back half managing a slow, unavoidable decline — the room came to dance for two hours and got one climax and an hour of cool-down. Or you sense that gap coming and stretch the build to fill it, holding back so long the energy never actually arrives — 70 minutes of “almost there” with no release.

A headline slot has room for more than one story. The fix isn't a different framework — it's running the one you already know more than once, deliberately, with proper spacing between each run: two or three build-to-peak arcs instead of one, each bigger than the last, with real valleys in between where the room gets a chance to catch its breath before you ask it to climb again.

The wave model: build, peak, release, repeat

Think of a headline set as a series of waves rather than one long climb. A wave is one full cycle: a build, a crescendo, and a valley. Chain two or three of these back to back and you've got a multi-peak set. This assumes you already know what build, maintain, and release mean at the single-transition level — our energy flow guide covers that vocabulary if you need a refresher. Here we're operating one level up: sequencing multiple of those cycles across one slot, not managing a single transition.

A wave breaks into three parts. The build is 4–6 tracks, climbing roughly 1 BPM per transition along with rising tension — more percussive elements, tighter arrangements, less headroom in each track's mix. The crescendo is a tight 3–4 track cluster at the top of that climb — your biggest tracks for this particular wave, sequenced for maximum impact back to back. Then the valley: energy drops by roughly 15–20% over 2–3 tracks. Not a full reset — you're not taking the room back to your opening energy, you're easing off the top just enough that the next build has somewhere real to climb to.

Valley depth matters more than it looks like it should. Drop too little and your next build has nowhere to go — you're already close to the ceiling, so the second crescendo barely registers as a step up. Drop too much and you're re-earning ground you've already covered — a valley that goes back to opening-level energy can waste 10 or more minutes climbing back to where you already were, minutes you don't have in a tightly paced slot. The valley's job is contrast, not amnesia.

Why you hold your best track back

Before you sequence anything, rank your prepared tracks by impact — which ones actually move the room, not which ones you personally rate highest. Most DJs preparing for a big slot make the same mistake: they play their best track early because they're excited and want to grab the room fast. That burns your ceiling in the first 20 minutes, and everything after it plays like a comedown, even the tracks that are objectively good.

Call your single strongest track your banker — the one you're most confident will land, whatever the room. Don't play it first. Save it for your final crescendo, when the room has already been through one or two waves, has trust in what you're doing, and is primed to go somewhere it hasn't been yet. Your #2 track — strong, but not quite the banker — is a better fit for your first peak. It proves you can deliver early without spending the one card you can't get back.

Leave 1–2 genuine wildcards unslotted entirely — don't assign them to a specific wave in your prep. Hold them as a live call, to drop in if a crescendo is landing harder than expected, or the room is asking for something you didn't plan for. A fully pre-slotted set has no room for that decision; a set with a couple of tracks held back on purpose does. The allocation, in short: banker for the final peak, your second strongest for the first, wildcards kept loose for whichever wave actually earns them.

Reading whether the room has earned the next peak

The plan gets you into the valley. Whether you come back out of it on schedule is a judgement call, and the room tells you the answer if you're watching for it. Tells worth checking between tracks, not just at the end of a crescendo: hands staying up after the last track fades versus dropping the moment the energy eases — the first means the room is still with the last peak and ready for the next, the second means you spent it. Bar and phone drift is the other obvious one — if people are heading for a drink or checking their phones during what should be your crescendo, that peak didn't land the way the track selection suggested it would on paper, and pushing straight into another build won't fix it.

The honest test is whether the last crescendo got a reaction, or just polite dancing. Polite dancing means the room is following you out of habit, not because you've earned the next climb — hold the valley 2–3 tracks longer than planned rather than force the build on schedule. This is exactly the situation a live-confirmation tool is for: Live Mode's crowd energy slider lets you register what the room is actually doing and get suggestions that match it, rather than sticking to a plan that assumed a room that isn't quite the one in front of you. The plan tells you where the waves should sit. The room tells you when to pull the trigger on each one.

The pacing math: spacing your peaks so they land

Spacing is the part most DJs get wrong the first time they try a multi-peak set. A second peak needs roughly 15–20 minutes, or 4–6 tracks, of real separation from the first before the room reads it as a genuinely new moment rather than a continuation of the one before it. Stack two crescendos less than about 10 minutes apart and they blur into one messy peak with a slightly odd shape in the middle — the room doesn't get two moments, it gets one moment that lasts too long and dips oddly halfway through.

Worked example: a 90-minute headline slot in tech house. Our Set Length Calculator puts tech house pacing at around 20 tracks per hour, so a 90-minute slot is roughly 30 tracks total. Split that across two waves — the right count for this length, more on that below — and you're looking at about 15 tracks per wave, roughly 45 minutes each:

• 0:00–0:45 (wave one): a 6-track build from your opening energy (0:00–0:20), a 4-track crescendo carrying your #2 track (0:20–0:28), then a 5-track valley into the second half (0:28–0:45).
• 0:45–1:30 (wave two): a 6-track second build off that valley (0:45–1:05), a 4-track final crescendo built around your banker track (1:05–1:13), then a 5-track close easing the room down to your landing (1:13–1:30).

Two things to notice. First, the crescendo gap: centres at 0:24 and 1:09, a 45-minute span — well clear of the 15–20 minute minimum, which is what makes the second peak read as an escalation, not a repeat. Second, both valleys here run longer than the general 2–3 track range above — splitting 30 tracks across two waves instead of three means each wave carries more weight, and needs more recovery room to earn its next climb.

Two waves or three: matching peak count to slot length and genre

Slot length sets the baseline for how many waves you can actually fit without stacking them too close together:

• 60–90 minutes (support or shorter headline slot): two waves. Enough runtime for one proper build-peak-valley cycle and a second, bigger one to close on, without either feeling rushed.
• 90–120 minutes (a proper headline slot): three waves. This is the sweet spot the wave model is really built for — room for a genuine escalation across three peaks rather than just two.
• 120+ minutes (a marathon slot): three to four waves, but flatten the amplitude of each one. Don't try to make every wave bigger than the last across four cycles — you'll run out of ceiling by wave three and have nothing left for the close. Keep the later waves closer in intensity to each other and let variety in texture and groove do more of the work than raw energy increases.

Genre changes the shape of the wave itself, not just the count. Tech house and techno favour tighter, faster waves — energy is carried by drums and texture more than melody, so a build can move through 4–5 tracks in 12–15 minutes and still feel earned. Melodic house and progressive want fewer, longer, bigger waves, because the tracks themselves run longer and the builds inside individual tracks need more room to develop — two big waves across 100 minutes will often outplay three tighter ones in that genre, even on a slot long enough to fit three.

Three ways multi-peak sets fall apart

Most multi-peak sets that don't work fail in one of three ways, all fixable once you know to look for them.

1. No real valley between peaks. If you stack a second crescendo on the tail of the first without a genuine energy drop in between, the room never registers it as a new peak — it just reads as the first one running long. The valley isn't optional filler; it's what makes the next climb legible as a climb.
2. Playing the banker too early. Front-load your strongest track and you've got nothing left to escalate to for the final wave. The room felt your ceiling in the first half hour, and every crescendo after that plays as a step down from what they already heard, even when the track selection is genuinely good.
3. Over-building the first wave. Push wave one too hard — too high a BPM jump, too aggressive a crescendo — and you've used up the energy and tempo headroom you needed for wave two or three. There's nowhere left to climb to, so later waves either stall at the same intensity as the first or force an unnaturally steep jump to get above it.

Building the multi-peak set in Mixgraph

The build order that works: total track count first, then each wave's shape, then the structure that holds it together. Start with the Set Length Calculator for your total track count at your genre's pace — the number you're dividing across your waves, same as the tech house example above.

Next, sketch each wave's shape individually in the Energy Arc Planner. One thing worth flagging before you open it: the tool's named “Peak” shape means sustained high energy from start to finish — a festival peak-time slot where you're on already at maximum and staying there. That's not this article's multiple-peaks technique, and there's no dedicated multi-peak preset to look for. Use the tool at the wave level instead — sketch a “Journey” shape (build, peak, cool down) for each individual wave, then chain two or three of those together yourself.

Then lay your waves out before you touch a single track in Flow Builder. Choose Club Flow (12 slots, 60–90 minutes) for a two-wave set or Peak Time Flow (16 slots, 90–120 minutes) for three. Each slot marks a structural waypoint in the wave — the start of a build, a crescendo, the low point of a valley — not a literal one-slot-per-track restatement of the calculator's total track count; the two tools work at different levels of detail, and that's fine.

Assign each slot an Energy Strategy — Build, Steady, Ease, or Mix up — matching what that slot represents in the wave. Build for each build run, Steady for each crescendo cluster (you want chemistry held high and consistent through that stretch, not still climbing), Ease for each valley, and Mix up for the wildcard slots you're holding for a live read. A 3-wave Peak Time Flow works out to something like 2 Build and 2 Steady and 1 Ease per wave across 15 of the 16 slots, with 1 Mix up slot left as your wildcard. That's the actual mechanism for encoding two or three build-valley-peak waves into one flow, rather than eyeballing the spacing and hoping it holds up on the night.