CleanɆrⱤoⱤ

The Error Balm Series – The full story behind enabl.ed’s glitch trilogy

So yeah. error balm vol.3 is done. It’s real now. It’s out now, and for those of you who’ve been following this strange little breadcrumb trail of fragmented beats, half-healed synth scars, and glitchy resurrections from corrupted hard drives—this article is for you.

You might’ve caught the teaser for it (if not, you can look at it here):

 
 
 
 
 
View this post on Instagram
 
 
 
 
 
 
 
 
 
 
 

A post shared by Clean Error Records (@cleanerrorrecords)

This is not an album drop post. It’s the full unpacking of why the error balm series exists at all. What each volume represents. Why the sounds flicker the way they do. And how it connects to something bigger—the identity of Clean Error, the idea of musical residue, and what it means to let go of old tracks that still haunt you.

Back in 2017, I was sitting on a heap of unfinished material. Like, a lot—track snippets/ideas, sound design ideas, file experiments, sessions with no endings. Stuff that never made it into anything, some of it just rotting on hard drives. Around that time, life itself was kind of…in glitch mode. Personal shifts, connections with other artists growing and breaking, the classic identity struggle of “what is my sound?” A feeling where I was trying to evolve the Clean Error identity but the future is still loading.

So I figured: why not just build from the debris?

Volumes 1 and 2 of error balm came out of that realization. The tracks aren’t polished “album cuts” by traditional standards. A lot were incomplete, half-born, or pure resample-driven frankenpieces. And that’s exactly why they mattered. They were a balm, not a bandage- something that didn’t cover the errors, but accentuated them. Amplified their texture.

And yes, the balm part? That came from beard balm. Back when I had hair on my head and thought beard care routines were self-care rituals. lol… But the metaphor stuck—balm as something that makes the rough stuff beautiful. You don’t erase the error, you make it glisten.

.WAV files don’t need to be perfect—they just need to survive.

That quote stuck with me during this whole project. Because honestly, a lot of the error balm series exists not because I wanted to finish tracks, but because the tracks refused to be forgotten.

See, a good chunk of the early error balm material was built from literal remnants—files rescued (barely) after I switched machines in 2022. Entire sessions gone. Projects I’d worked on in FL Studio… Toast. What remained were the rawest of exports—16-bit WAV bounces, some of them weirdly truncated, some baked with heavy clipping, aliasing, low-level hiss. Think of them like charred pages from a lost book. No stems. No MIDI. No undo button.

At first, I was furious. Then I realized: this was the project.

I started treating those fragments like archaeological finds. I didn’t try to fix them—I framed them. I looped old pads with crust still on them. I resampled glitched out intros. I layered half-finished takes over new percussion grids and watched something else take form. Some of the most crucial textures on Vol.1 and Vol.2 were literally just misaligned bounces from 2018 that I pulled into Ableton and mangled further.

There’s something strangely poetic about working with a sound that’s already damaged and knowing—deep down—that it probably sounds better because of the damage. Like, that moment where you realize the distortion on the tail of a snare was a limiter kicking in at the wrong moment, and instead of smoothing it out, you just loop it and let it breathe.

Even with all the tech we’ve got now—clean multiband transient designers, denoisers, oversampled resynths—it’s tough to replicate the kind of character you get from unintended failure. The hardest part wasn’t restoring the fidelity. It was resisting the urge to over-clean. Some of those compression artifacts, clipped hats, wonky stereo fades? They are the mix. They’re what gave this trilogy its unpolished, human shape.

They’re the emotional residue of sessions that glitched and collapsed—but still left behind something worth hearing. That’s why I called it error balm. I wasn’t trying to heal the music. I was trying to show the beauty in the wound.

A “Legacy Error is my term for a recurring sonic idea—or glitch, motif, sample, rhythm structure—that appears across different compositions over time. It’s not just a reused sound. It’s a kind of artifact. A mistake I never fixed that evolved into a core element of the Clean Error aesthetic.

Think of them as thematic ghosts or audio anomalies that persist across tracks. They’re the reason some pieces feel linked, even if they were written years apart. Legacy errors are passed down. Reused. Mutated. They connect tracks that don’t seem like they should be connected.

These are the collection of ‘Legacy Errors” from Vol.1 and 2: 
Legacyɹoɹɹǝ v.1.0
Legacyɹoɹɹǝ v2.2
Legacyɹoɹɹǝ v3.4
Legacyɹoɹɹǝ v0.1 (Bonus)
Legacyɹoɹɹǝ v4.9.3
Legacyɹoɹɹǝ v5.5.7
Legacyɹoɹɹǝ v6.3

and in Vol.3:
Legacyɹoɹɹǝ v10.5.3

One thing that started happening naturally through these volumes was a shift toward piece-built tracks. I’d build one section, leave it, make another, and weeks later realize they could be fused. And so I started adding version suffixes to tracks like “4.9.3”—and yes, those numbers mean something. Lets use this track as an example: ‘Legacyɹoɹɹǝ v4.9.3

-The first digit -‘4’ is the legacy error ID, meaning this track stems from the fourth major error motif or concept in my system. This could be a certain drum style, synth patch, or compositional structure that first showed up in an earlier piece—and is now being expanded or mutated.

-The middle number -‘9’ is the number of fragments or compositional pieces fused to create the track. I treat each fragment as its own mini-composition. Could be a drum loop, melody, FX chain, ambient bed, etc.

-The last number -‘3’ is the version of the track. Sometimes I make multiple arrangements or alternate endings. If you see a third number, it means there are at least that many iterations.

So a track suffixed like “4.3.2” means it’s the fourth track in that legacy theme, made of three stitched-together parts, and you’re hearing version two.

If the third number’s missing? You’re hearing the only version. There are no alternates. No B-sides. That’s the final relic.

This format became a ritual for me. It shaped how I worked. Instead of forcing a track to bloom in one go, I embraced the mosaic process. The musical Frankenstein-ing. It’s not efficient, but it’s personal. And by Vol.3, this was just how I worked. I didn’t even label the versioning anymore when I released the final product but its labeled in the session file. There’s something powerful about becoming your own crate digger. Going back into your catalog—not to remix it, but to reintegrate it. To build a new context around an old mistake. That’s what legacy errors let me do. They become reference points that carry emotional and structural weight.

You can hear them evolving over the course of the error balm trilogy:

-In Vol.1, they’re almost accidental. Artifacts of lost projects that found their way into other tracks.

-In Vol.2, I start doing it intentionally—grabbing loops from earlier sessions and folding them into new pieces.

-By Vol.3, it’s the entire system. Almost every track contains a deliberate reuse of earlier material, whether it’s a processed version of a Vol.1 drum loop or a mangled FM synth motif from a track that never got released.

I made the v7, 8 and 9 Legacy Errors…but those tracks didn’t make the cut, but 10 did. I just wasnt happy with how v7, 8 and 9 was sounding. But now when I produce this term will reside within my production relm and now itll be come something else.

Calling this volume stable might sound ironic if you’ve heard it. There’s still grit. Still fracture. Still that signature enabl.ed compression-splintered shimmer and off-grid rhythmic shuffle that’s been living in my music for years. But this time, the chaos feels held. Directed. Intentional.

Unlike the first two volumes, error balm vol.3 was produced entirely in 2024 and finalized in April 2025. No ancient renders. No lost files from dead laptops. No stitched-together artifacts from half-rendered ghost folders. Everything on this one came out of one focused period of creative energy—filtered, refined, resolved.

That doesn’t mean it abandoned its roots. You’ll still hear sounds recycled and recontextualized—some drums and tonal FX are literally lifted from Vol.1 and Vol.2, then filtered through new processes, frozen, bounced, and mangled again. But instead of being bound together by necessity like the earlier volumes, Vol.3 was about control. About setting up a tightly framed sonic world, then letting myself roam within it.

I don’t mean stable in the clean, sterile, overly-slick production sense. I mean stable as in consistent. Cohesive. This volume stays in one lane—not to limit itself, but to explore depth over width. I deliberately avoided the more scattered genre-hopping tendencies of earlier works. Instead of darting between glitchy ambient, broken-beat Braindance, and abstract techno, I kept this one zoned into a specific bandwidth of IDM: post-clicks+cuts, post-Autechre, emotionally fragmented but melodically aware.

The limitation was the freedom.
Like, how far can you go within one frequency palette? How much emotion can you squeeze out of a detuned FM bell and a broken kick loop? How weird can it get before it breaks character?

Vol.3 challenged me to not just throw paint at the wall and call it “experimental”—but to shape every texture, every transition, every melody around a single, evolving atmosphere.

A huge part of why Vol.3 sounds the way it does is because I finally transitioned to Ableton Live as my main DAW. Prior to this, I was doing most of my work in FL Studio.

Switching to Ableton cracked everything open. Suddenly I had precision—automation curves that actually made sense, native devices that didn’t crash halfway through rendering, and access to Max for Live and other tools, which became a full-on playground.

With Max and other tools, I could:

Inject chaos on purpose—not just by accident.

The tools didn’t just make things cleaner—they made glitches predictable. I was no longer just reacting to random errors. I was designing around them. Controlling the fracture. Deciding when a melody should fall apart, and when it should just barely hold together. That’s a huge shift from the first two volumes, where the structure was often determined by what samples I had left, what session didn’t crash, or how well I could fake a cohesive ending.

Ableton gave me that final push I needed to finish Vol.3 in a way that still felt fractured—but mature. Refined glitch. Composed instability. Part of me needed this record to feel held because so much around it wasn’t. Between personal shifts, creative fallout with a label (see broken flow section), and feeling like I was constantly being asked to “pick a lane” sound-wise, Vol.3 became the space where I could actually do that—not by compromise, but by choice.

The decision to stay in a lane here wasn’t about pleasing listeners or chasing genre conformity. It was about proving to myself that I could focus. That I could make a record that sounded like it belonged to a singular vision—without losing the chaos that makes my music mine.

It’s stable in the same way that a glitched VHS loop eventually settles into rhythm. You still see the noise, but now it’s part of the grid.

broken flow – (a transitional release born during volume three, caught in the crossfire)

Before I even knew error balm vol.3 would close the series, I had already started working on another project—something looser, more playful, and originally meant to be collaborative. That project was called broken flow, and it was always meant to be the next evolution of enabl.ed after the trilogy.

Not a sequel. Not a reboot. More like the transitional glitch – a moment of stylistic drift recorded in real time, during the production of vol.3. Some of the melodic ideas and rhythmic sketches for broken flow were literally written on the same days as vol.3 sessions. You can hear their shared blood—similar drums, overlapping textures—but where vol.3 was tightly focused, broken flow was designed to breathe. To wander. To get lost on purpose.

The original concept for broken flow was to do something more spontaneous and collaborative. A collection intentionally designed to unravel and re-thread rhythm. Each track explores off-kilter timing, where fractured melodies and glitch-warped sequences seem to drift—but never collapse. The foundation lies in a contrast between distorted and clean pinched drums, creating a tension between looseness and control. The “broken” rhythms aren’t broken by mistake; they’re broken on purpose, with glitches acting as the glue that keeps the entire flow from falling apart. It’s IDM that breathes unevenly, but still holds a pulse.

I’d been talking with another record label I respected about doing this release, and the energy was promising.

But that never happened.

Instead, the entire thing quietly fell apart over something I didn’t fully see coming: concerns about artistic integritycentered, in part, around vague assumptions tied to the use of AI, and broader existential questions about “trust” and “authenticity” within the Clean Error ethos. You know—real philosophical stuff. The kind of discourse normally reserved for forums that still argue over whether vinyl “feels warmer.”

One of the actual sticking points?
Apparently, the presence of AI-generated artwork on Clean Error releases was enough to convince some folks that the entire labelmusic, intent, process, everything—must be fake. Synthetic. Deceptively automated. Which is not only a reach, it’s a textbook logical fallacy.

Let’s break it down:
Just because an album cover is clearly made using AI-assisted visual tools, that doesn’t mean the music—or the artist behind it—is artificial:

That’s like saying an Autechre track doesn’t count because they used generative patching in Max. The method is the music. That’s like assuming every piece of art made with generative prompts is soulless—when half of traditional digital art relies on brushes someone else coded. That’s like saying a digital painter isn’t a real artist because they used Photoshop layers instead of oil on canvas. Welcome to 2025. See the problem?

This is guilt by associationa sort of aesthetic panic response that goes:

If the cover looks like AI, the content must be AI, the artist must be AI, and now my entire sense of musical purity is spiraling.”

Look… the artwork on Clean Error releases is often created with generative tools. That’s not a secret. It’s part of the label’s visual language. But that doesn’t mean it’s done lazily. It’s curated. It’s styled. It’s directed. It’s not just clicking “make image” and uploading it to Bandcamp—it’s another layer of texture. Another collaboration with controlled chaos. Just like the music.

And let’s be real: Clean Error has never been about traditional purity. It’s been about intentional instabilityboth visually and sonically. The idea that one aesthetic choice (AI-generated visuals) invalidates the whole project is a bad faith argument. And unfortunately, it was enough to make “some people” back away without a single conversation.

Honestly?
If the artwork was hand-drawn in charcoal and the music was still glitched, resampled, and full of unstable rhythms, they probably would’ve called it “authentic.” But because a tool was used that made them uncomfortable, it became easier to dismiss the whole thing as fake.

That’s the danger of aesthetic gatekeeping disguised as moral critique.

Clean Error has always been open about process. If anything, it might be too open. So when people make up a narrative about deception based purely on visuals and music… it says more about their insecurities than it does about the label.

To be clear, the departure wasn’t mutual. It came swiftly, without a real conversation, and without space for clarification. What hurt most wasn’t the disagreement itself—it was the dismissal. A full severing of ties based on speculation, without ever sitting down to ask why things sound the way they do, or how the process actually works behind the scenes.

I’ve always been open about how I work. My methods are unorthodox, sure—nonlinear session building, heavy resampling of my own material, rendering ideas in fragments and stitching them together like collages. But that is the core of what enabl.ed and Clean Error are about. It’s not about imitation. It’s about iteration. Chaos not as a bug, but as a compositional choice.

The fact that this entire collaboration dissolved over assumptions—without any actual conversation—was disappointing. Especially in a scene like this, where connection and trust between artists and labels should mean something more. I understand we all have our boundaries and values, but if there’s no room to even talk before judgment, what are we building?

For anyone curious, I’ve already addressed Clean Error’s relationship with AI, its tools, and how I feel about their ethical use in music in this blog post here:
https://www.cleanmyerror.com/error-node-blog/cleanerror-a-story-driven-label-and-ai/

…which I encourage anyone to read if they’re trying to understand where I stand on that.

The fallout with the label won’t stop broken flow. It just changed its shape—and maybe made it more necessary than ever. I do plan on releasing it on Clean Error this year so everyone will get to hear it.

…and look—if the ultimate accusation here is that I’ve been dishonest with people, or that Clean Error is some kind of secret AI-run ghost machine, then you really have to wonder: why on earth would I be writing this entire blog post? Why would I attach it directly to the release? Why would I publicly archive all of this—my working process, my intentions, my errors, and my own disappointment—on a platform that’s literally connected to the music?

Because if my grand deception plan was to mislead the public and operate in total secrecy, then I’m really doing a terrible job. Maybe I should’ve just quietly dropped a few Bandcamp links and disappeared into the fog like a proper scammer. Instead, here I am explaining the very accusations I was supposedly trying to hide, in full, on the official release page. Seems like an odd strategy for someone allegedly trying to pull one over on everyone—including those who made the accusation in the first place.

So yeah—if this is deceit, it’s got a weirdly transparent, footnoted, emotionally vulnerable approach. Almost like I’m just… telling the truth. What a concept!!!

I use digital tools. I use modern plugins. Yes, I experiment with generative systems and modulation randomness. But I am not outsourcing expression to algorithms. The glitches are mine. The fractures are built by hand. The errors were earned. And yet, this ‘label’ I was collaborating with suddenly pulled out. No conversation, no resolution—just a snap judgment and severed ties. My whole sound identity—was being reduced to a false narrative. It was one of the most disheartening moments I’ve had in music.

And to any new musicians reading this, or anyone else navigating similar spaces: be careful who you open up to. It’s easy to believe that this scene is full of like-minded people who understand your process, your heart, your weird little obsessive production quirks—but some will turn their backs on you in a second. No conversation. No questions asked. One day you’re talking about collaboration and pushing the sound forward, and the next you’re getting ghosted over rumors.

It’s sad, and it’s happened to a lot more artists than just me. This industry, even in its tiniest underground forms, can be harsh—especially in scenes like ours. The experimental, post-IDM niche already has a small audience, and most of us are operating out of love and obsession, not profit. So it makes it even harder when the very people who claim to be about “community” are quick to distrust or dismiss without a single honest conversation.

It shouldn’t be like that. We’re not the mainstream. We’re not some over-saturated techno market or pop machine. We’re in the margins on purpose. We’re building from dust and noise and emotion. If anything, we should be more collaborative and more supportive than ever. But the truth is, even this scene—this strange, beautiful glitch world—feels diluted sometimes. Not in the creative sense, but in the trust. In the way people treat each other.

So just… be mindful. Protect your energy. Share your art, but keep your boundaries.

The idea that using tools like Max for Live tools or modular MIDI effects somehow invalidates the authenticity of my work? That’s not a critique—it’s a fundamental misunderstanding of what experimental electronic music even is.

We’ve always embraced broken machines. Circuit-bent gear. Tape warble. DSP freakouts. From the earliest Rephlex days to modern-day glitch artists pushing generative systems to beautiful extremes—this is part of the language. We don’t fear new tools. We corrupt them. That’s the lineage Clean Error belongs to.

error balm taught me to turn left over creative ideas and digital loss into a format. To let lost tracks be part of the mix. And Vol.3? That’s the calm at the edge of that chaos. Still twitchy, still cracked—but finally stable enough to move forward.

I’m grateful for everyone who stuck with this series, especially folks like Igloo Magazine who wrote thoughtful reviews about the 1st volume: https://igloomag.com/reviews/enabl-ed-errorbalm-v1-clean-error
&
2nd Volume: https://igloomag.com/reviews/enabl-ed-errorbalm-v2-clean-error

Your support and the support of the listeners, Clean Error fans, FRGMNT members that enjoyed it… helped make this feel worth continuing, even when the process itself felt frustrating and invisible.

Vol.3 is the send-off. But it’s not the end.

See you in the flow.

enabl.ed

Leave a comment: