Crash Course: The Producers Turning Their Broken Gear Into a Genre

Mira keeps a laptop that she describes as "terminally ill" on a dedicated shelf in her Chicago apartment. It hasn't booted successfully in about a year and a half. She doesn't need it to. What she needs it to do — what it does, reliably, every time she opens it — is produce approximately forty seconds of audio artifacts before the screen goes dark. Stuttering codec noise. A fan struggling against its own bearings. The particular sound of a system trying to execute instructions it no longer has the resources to complete.

She's sampled that laptop on three releases. Two of them got written up in publications that cover experimental music with the kind of reverence usually reserved for mid-century minimalism. She's not fixing the laptop.

The Mistake That Became the Method

The story of how malfunction became intentional practice in electronic music is longer than most people realize. Glitch as an aesthetic has roots in the late 1990s, when producers like Oval and Alva Noto were deliberately scratching CDs and processing the skipping into compositions. Noise music had been doing related things even longer. But what's happening now in underground circles across the US feels different in character — less theoretically motivated, more viscerally committed to the specific textures that hardware and software produce when they're failing on their own terms.

The distinction matters. Earlier glitch work often involved deliberately inducing failures in controlled ways. What the current wave of practitioners are doing is closer to field recording — they're capturing what's already happening, treating their degraded equipment as a natural environment with its own sonic ecology.

"There's a difference between making something sound broken and listening to something break," says Jordan, a Brooklyn-based producer who works under a name that's deliberately difficult to search. "I'm not creating the failure. I'm just there when it happens."

What a Buffer Overflow Actually Sounds Like

For the uninitiated: a buffer overflow occurs when a system tries to write more data to a memory buffer than the buffer can hold. The results, sonically, can range from a brief click to a complete audio collapse that sounds like the digital equivalent of a building folding in on itself. It's not pleasant in a conventional sense. It is, according to a growing number of people, extremely interesting.

Tamsin, who produces out of a repurposed warehouse space in Detroit, has built an entire album around buffer overflow events captured from a DAW she keeps deliberately overloaded. Her process involves running more tracks and plugins than her system can handle, then recording the output — not the intended audio, but whatever comes out of the speakers when the software starts to lose the thread. The results are dense, disorienting, and occasionally beautiful in the way that industrial decay can be beautiful: honest about what's happening, not trying to be anything else.

"People keep asking me what plugins I used," she says. "The plugin is that my computer is dying."

Hardware Has Its Own Voice

Software failure is only one part of the picture. A parallel and arguably richer tradition involves physical hardware — synthesizers with failing capacitors, tape machines with degraded heads, drum machines whose memory chips have developed idiosyncratic errors that cause them to misfire in consistent, repeatable ways.

This is where things get philosophically interesting. A piece of hardware that malfunctions in a predictable pattern is, functionally, a new instrument. It has a range. It has characteristic sounds. It responds to input in ways that are no longer what the manufacturer intended but are nonetheless consistent. Some producers have begun cataloguing their malfunctioning hardware the way a traditional instrumentalist might describe the quirks of a particular vintage guitar — this one has a tendency to drop an octave on the third beat, this one adds a harmonic that shouldn't be there but is always there.

Reed, who works primarily with modified synthesizers in Los Angeles, describes a Juno-106 with a failing voice chip as his most important instrument. "Six voices, and one of them is haunted," he says. "I've had it serviced. They fix it, and it stops being interesting. I just keep breaking it again."

The Collapse of the Error/Intention Boundary

What's genuinely novel about this moment isn't the sounds themselves — noise music has always existed, and the avant-garde has always had a complicated relationship with malfunction. What's new is the degree to which the distinction between mistake and composition has become functionally meaningless for a generation of producers who grew up with digital tools.

When you work in software, the line between what you intended and what the system produced was always blurrier than traditional music production frameworks suggested. Auto-quantization, pitch correction, the way a DAW handles latency — these are all places where the machine makes decisions that shape the output. Glitch producers are just making that process visible, pushing it to an extreme where the machine's decisions become the primary creative content.

This has implications beyond aesthetics. It's a genuine argument about authorship. When Mira's laptop produces forty seconds of audio artifacts, who made that sound? The original engineers who designed the hardware? The software developers whose code is failing? Mira, for creating the conditions and choosing to record it? The answer, in the underground electronic music scene, is increasingly: all of them, and also none of them, and also who cares.

A Genre That Refuses to Name Itself

Ask practitioners what to call this and you'll get a different answer every time. Some use glitch. Some use noise. Some use nothing at all, which is probably the most honest response. The community is loose, distributed across Bandcamp pages and small label catalogs and SoundCloud accounts with minimal follower counts and zero interest in building them.

The music isn't trying to find you. It's just there, on whatever frequency it's transmitting from, doing what it does.

Mira's dying laptop is sitting on its shelf right now. When she opens it tomorrow, it'll do what it always does. She'll have her recorder running.

She's already got the next track half-finished.