Your level
0/5
🏆
Listen to this genre to level up
Description

Algorave is a form of dance music culture where the music is created and manipulated live through code, with the performer writing algorithms on stage that generate rhythm, melody, and timbre in real time. The audience typically sees the code projected, turning the act of programming into an expressive, improvisatory performance.

Sonically, algorave draws on club styles like techno, house, acid, and rave, while embracing experimental tactics from glitch, IDM, and live algorithmic composition. Expect driving tempos (often 120–160 BPM), polyrhythms, euclidean patterns, evolving loops, and raw, percussive sound design that foregrounds process, pattern, and transformation.

History
Origins (late 2000s–early 2010s)

Algorithmic music and live coding communities (notably TOPLAP, founded in 2004) laid the groundwork by framing programming as a performative, improvisatory act. In 2011, Alex McLean and Nick Collins coined the term “algorave” to describe rave-oriented live coding. The first algorave events followed in 2012 in the UK, bringing algorithmic composition squarely into club contexts.

Tools and aesthetics

Algorave coalesced around open-source environments such as SuperCollider, TidalCycles, FoxDot, and later Sonic Pi, which allowed performers to quickly sketch, refactor, and transform patterns during a set. Projected screens made the compositional process visible, emphasizing transparency, risk, and liveness. Musically, the scene fused UK rave sensibilities (techno, house, acid) with IDM/glitch experimentation and code-based pattern languages (euclidean rhythms, list transforms, stochastic processes).

Global spread (mid–late 2010s)

By the mid‑2010s the movement had grown into an international network spanning Europe, the Americas, and Asia–Pacific, supported by DIY promoters, university labs, and art/club hybrids. Festival showcases, media features, and community-run conferences helped normalize algorithmic performance in dance venues, while workshops broadened participation and emphasized accessible, open tools.

2020s and beyond

During the 2020 pandemic, algorave activity shifted online via livestreams and distributed festivals, accelerating tool development and remote collaboration. Hybrid events later returned to clubs, with the scene continuing to value openness, community learning, and experimentation—keeping code-as-performance central while engaging with contemporary club sound and culture.

How to make a track in this genre
Setup and tools
•   Choose a live-coding environment oriented to rhythm and synthesis (e.g., TidalCycles + SuperCollider, FoxDot, Sonic Pi). Use low-latency audio drivers and map a reliable clock (MIDI or internal). •   Prepare a minimal sample pack (kicks, claps, hats, stabs) and a few synth definitions for bass, leads, and noise textures.
Rhythm and form
•   Aim for club tempos (120–160 BPM), often around 130–150 for techno/acid feels. Start with a 4/4 pulse, then introduce syncopation. •   Use pattern languages (euclidean rhythms, polyrhythms, tuplets) to generate evolving grooves. Layer several short loops and vary density over time. •   Employ structural macros: 8–32 bar sections, call-and-response between drum groups, periodic drops, and tension via filter/open-hat risers.
Harmony and melody
•   Keep harmony sparse and modal; dance focus favors timbre and rhythm. Use short scales (minor pentatonic, Phrygian, Dorian) and ostinati. •   Algorithmically vary motif length, transposition, and contour (e.g., rotate, shuffle, random walk with constraints) for subtle evolution.
Sound design and texture
•   Combine simple subtractive basses with acidic resonant leads and metallic FM hits. Accent groove with glitches, bitcrushing, and short granular bursts. •   Live-map parameters (filter cutoff, resonance, decay, distortion) to LFOs or code-driven envelopes for motion. Sidechain or duck elements for pump.
Live-coding tactics
•   Code in small, reversible edits: duplicate a pattern, mutate, audition, then swap. Use versioned buffers or history to recover quickly. •   Introduce variation via functions (every, sometimes, degrade, scramble), probability gates, and per-step modulation. •   Build breakdowns by thinning layers, widening reverb, or filtering bass; re-enter with full-spectrum drums and bass stabs.
Performance practice
•   Project your code to share process—embrace risk and visible improvisation. Keep CPU headroom; test transitions and clock stability pre‑set. •   Balance novelty with dancefloor clarity: ensure a consistent kick and bass foundation while experimenting in mid/high layers.
Influenced by
Has influenced
No genres found
© 2025 Melodigging
Melodding was created as a tribute to Every Noise at Once, which inspired us to help curious minds keep digging into music's ever-evolving genres.