Glitch production migrated from damaged hardware into software simulation of failure states

Through the late 1990s and 2000s, as DAWs and laptop production became dominant, glitch techniques migrated from physical hardware manipulation into software. Artists splice small sample cuts and simulate failure states using trackers (Jeskola Buzz, Renoise), modular/patching environments (Reaktor, Max/MSP, Pure Data, SuperCollider, ChucK), and DAWs (Ableton Live, FL Studio). This raised a persistent question about the genre: whether software glitch is the corruption of intact music through post-production processing, or the composition of new work from digital detritus as raw material. Oval’s Popp framed his own practice as the latter — taking ‘seemingly unusable fragments’ as source material rather than applying glitch as a stylistic overlay.

Examples

Renoise and Jeskola Buzz (trackers) suit sample-level micro-editing; Max/MSP and SuperCollider let you write signal-processing routines that generate or extend failure states programmatically — the same corrupted-data aesthetic, now scripted.

Assessment

Name three software environments used in glitch production and state the two competing views of what software glitch processing does to source material.