Offered by Dead Brands
Background music for games, streams, and videos must survive being heard a hundred times without annoying anyone — and restart so smoothly the listener never notices the seam.
Use it over MCP: connect to https://mcp.deadbrands.co/hub/mcp and call skills_get with slug loop-based-music-composition.
# Loop-Based Music Composition Credit: SteTy — published free in the Skills Hub Background music for games, streams, and videos must survive being heard a hundred times without annoying anyone — and restart so smoothly the listener never notices the seam. Writing a great loop is its own discipline: the ending must be composed as a beginning, and variation must be designed in, because repetition is guaranteed. ## Overview A loop is a piece of music whose last sample connects invisibly to its first. Three problems define the craft. **The seam:** any click, cut reverb tail, or harmonic jolt at the join point breaks the spell. **Harmonic rhythm:** the rate chords change determines whether the loop implies motion or stasis. **Fatigue:** a loop that is interesting once can be unbearable at minute ten, so composers design variation systems — layered stems, rotating melodies, and energy arcs — rather than a single frozen block of music. Typical delivered lengths: 30 seconds to 4 minutes for game areas, 2–8 minutes for ambient beds. ## Core Principles - **Compose in a circle, not a line.** Write the loop's ending so its final chord wants the first chord. The most reliable engine is a progression that resolves across the seam: end on the dominant (V) or a passing chord, begin on the tonic (I). - **Harmonic rhythm sets the energy.** One chord per bar = forward drive. One chord per 2–4 bars = floating, ambient. No chord change at all (a pedal/drone) = timeless background. Slow harmonic rhythm fatigues far less than fast. - **The steady-state rule.** Render the loop playing *through itself* at least twice before bouncing — the second pass is the true loop, because reverb and delay tails from the ending are now feeding the beginning, exactly as listeners will hear. - **Density discipline.** Background loops live under voices and sound effects. Leave the 1–4 kHz speech band sparse, keep transients soft, and cap the number of competing melodic lines at one. - **Length beats cleverness.** Doubling a loop's length quarters its perceived repetition. A plain 2-minute loop outlasts a brilliant 20-second one. ## Techniques - **Tail management (the craft's core skill)** — reverb and delay at the end of the file cannot just be cut. Three professional solutions: 1. **Render-and-wrap:** render three passes of the loop through its effects; keep the middle pass. Its opening already contains the previous pass's tails, and its ending decays into audio identical to the next pass — seamless by construction. 2. **Cut-and-swap (for textures/ambience):** split the file in half, move the second half to the front, and blend the new middle join with a long equal-power crossfade (2–4 seconds for rain, pads, drones). The outer edges were originally continuous, so the loop point is perfect. 3. **Runtime tails:** leave the rendered tail *after* the loop region and let playback software (game audio middleware such as Wwise or FMOD) overlap it across the seam with loop markers. - **Zero-crossing trims** — for hard-cut loops, trim start and end where the waveform crosses zero amplitude to avoid the click caused by a sudden amplitude jump. - **Ostinato engines** — build on a repeating short pattern (a bass riff, an arpeggio, a rhythm figure) and rotate *other* elements over it: melody phrases that enter every other pass, harmony pads that swap voicings. The ostinato gives identity; the rotation gives lifespan. - **Vertical layering (adaptive music)** — compose the loop as stackable stems that share tempo, key, and length: base (pads/rhythm), plus intensity layers (percussion, melody, harmony) that can fade in and out independently — calm/explore/combat versions of one piece. Every stem must work in every combination, so compose them against the base, not against each other. - **Horizontal resequencing** — write several loop segments (intro, A, B, bridge, stinger endings) and let the playback order change with context. Segments must share tempo/key and end on chords that can lead anywhere. - **Energy arcs within the loop** — even a single loop should breathe: arrange an 8- or 16-bar internal arc (sparse → full → sparse) so the repetition contains a miniature journey instead of a flat plateau. - **Genre-typical lengths** — chiptune/retro loops: 30–60 s, high melody density. RPG town/exploration: 1–3 min, gentle harmonic rhythm. Combat loops: 45–90 s, driving ostinato, few chord changes. Ambient/dungeon beds: 2–6 min drones or slow progressions. Stream "starting soon"/BRB beds: 2–4 min, mid-tempo, nothing that demands attention, no vocals. ## Worked Examples - **The wrap, concretely:** a 16-bar loop at 100 BPM lasts 38.4 s. Render 3 passes (115.2 s) with the loop's reverb on, discard pass 1, export pass 2 alone (38.4 s). At the seam, the ending's reverb tail is literally the same audio as pass 3's opening — no edit, no click. - **A fatigue-proof progression:** Am–F–C–G (vi–IV–I–V in C) at one chord per 2 bars, 8 bars total. The V at the end pulls back to the vi at the top; the ear reads continuation, not restart. - **Kōji Kondō's lesson** — classic game loops (e.g., the *Super Mario Bros.* overworld theme) use short, rhythmically playful melodies over simple harmony, at lengths under a minute — proof that a strong melody can survive extreme repetition if the rhythm stays buoyant. ## Common Pitfalls - **The first-bar downbeat crash** — a big hit on bar 1 becomes a metronome announcing the seam every pass. Keep the loop's opening modest. - **Reverb pile-up** — bouncing the raw render with the tail chopped leaves silence-gaps in wet instruments; bouncing with tail included *and* looping creates double tails. Use the steady-state render. - **A melody with a "final" phrase** — cadential endings (long note, ritardando feel) sound like the song stopped, every 40 seconds. End melodic phrases mid-gesture or on the pickup into bar 1. - **Looping in the wrong key relationship** — ending on I and starting on I is fine; ending on IV and starting on I creates a lurch. Map the seam chord pair deliberately. ## Practice Drills 1. Take any 8-bar progression you like. Render it 3 times through a reverb, extract the middle pass, and loop it 10 times in a player. Count how many seams you can hear — target zero. 2. Build one 32-second loop in three stems (base, percussion, melody) that all sound acceptable in every on/off combination. 3. The 10-minute test: play your loop while doing another task for 10 minutes. Note the exact moment it starts to annoy you, and diagnose which element (melody? rhythm? chord loop?) caused it. Fix only that element. ## When to Use and Limits - **Use it when:** a task calls for loop-based music composition, as laid out in the Techniques and Worked Examples above. - **Watch first for:** The first-bar downbeat crash; Reverb pile-up; A melody with a "final" phrase (see Common Pitfalls). - **Limits:** this is a general reference drawn from public sources; it is a starting point for practice, not a full course, and attributions and dates should be checked against the cited sources before quoting them. ## Quick Reference | Check | Standard | |---|---| | Seam test | Inaudible across 10 consecutive passes | | Render method | 3 passes, keep the middle | | Crossfade for textures | 2–4 s equal-power at the join | | Trim points | On zero crossings | | Speech band | Keep 1–4 kHz sparse under dialogue | | Exploration loop | 1–3 min, slow harmonic rhythm | | Combat loop | 45–90 s, ostinato-driven | | Ambient bed | 2–6 min, drone or pedal harmony | --- *Trademarks and copyrights mentioned belong to their respective owners. Educational reference only; not affiliated with or endorsed by them.*