Behind 'Forbidden Shaman': Why the Dirtiest Sound in the Track Was the Whole Point

The title came first. That's not usually how it works for me — most tracks live nameless for months while I figure out what they actually are. But "Forbidden Shaman" arrived as a phrase before a single note existed, and the whole production became an attempt to justify it.

What does a forbidden shaman sound like? Not mystical. Not ancient. Not the cinematic version — the robes, the smoke, the reverb-drenched chant. Something that operates outside sanctioned channels, that deals in energy nobody else wants to touch, that works precisely because it doesn't ask for permission. That version of the concept is inherently aggressive. The forbidden part is the point.

Where "(Nasty)" Came From

The version of this track that I originally finished was cleaner. More controlled. The drop had the right energy but sat within the range of what I'd done before — textured, dense, but ultimately restrained. I played it back a few times and knew something was missing.

The problem wasn't the mix. It wasn't the arrangement. It was that I'd written a track called Forbidden Shaman and made it polite. A shaman who asks permission isn't forbidden. They're just unusual.

So I rebuilt the drop. Not from scratch — the bones were right — but I pushed the saturation further than I normally would, distorted elements I usually keep pristine, and let certain frequencies clip in ways that would typically send me back to fix them. The result was something that felt genuinely unruly. Not broken. Intentionally rough. That's what earned the (Nasty) qualifier in the title.

I put it in brackets because it's a descriptor, not a genre tag. The track is Forbidden Shaman. The version you're hearing is the nasty one. There's no other version. The title just tells you what you're about to experience.

Ritual Without Religion

I'm not interested in shamanism as a spiritual practice, and I wasn't trying to make music about it literally. What I was interested in was the structural idea of it — someone who channels something beyond themselves, who acts as a conduit for energy that's larger and less polished than the normal world allows.

That concept maps onto production in a way that made sense to me. When a track reaches a certain state in the studio — when the bass is resonating at the right frequency and the whole room starts to vibrate slightly and something about the combination of sounds stops feeling like decisions you made and starts feeling like something you found — that's the condition I was trying to construct and capture.

It doesn't always happen. When it doesn't, the track sounds like work — like the result of decisions, which it is, but you don't want it to read that way. When it does happen, the track sounds like it had to exist. Forbidden Shaman is the second kind. The (Nasty) rebuild is when it crossed into that territory.

The Bassline Architecture

Most of the track's aggression lives in the low end. The bassline in the drop isn't a melody — it's a pressure system. It doesn't resolve. It pushes. The note choices are intentionally unresolved, sitting at the edge of dissonance without tipping into it, which creates a sustained tension that the track never fully releases.

That choice was deliberate. Resolved bass is satisfying in a way that immediately passes — you get the payoff and it's done. Unresolved bass creates a kind of urgency that persists through the listening experience, even when the track is technically doing something relatively simple. The listener is always slightly waiting for a release that never quite comes. That's the forbidden energy made structural.

The high end of the track is doing the opposite — sharp, cutting, almost brittle in places. The combination of thick unresolved low end and aggressive high end with relatively scooped mids creates the physical impact the track needed. It's not a comfortable frequency balance. It's not supposed to be.

The Part I Almost Cut

There's a section roughly two-thirds through the track where everything drops to nearly nothing. A single tonal element, barely there, in a space that feels enormous after the density that preceded it. I almost cut it every time I listened back during production. It felt like a break in momentum — like the track lost its nerve for eight bars before coming back.

I kept it because I eventually realized it was doing something the rest of the track couldn't do alone. You don't fully understand how loud something is until you've heard the quiet. The near-silence section makes the final section of the drop hit differently — it resets your perception of the track's ceiling right before it goes back above it. Without the break, the end is just more of what came before. With it, the end feels like something new even though it's returning to familiar territory.

The shaman knows when to stop moving. The stillness is part of the ritual, not a pause in it.

Listen Now

Spotify · Apple Music · YouTube Music

FAQ

What does "Forbidden Shaman" mean?

The title came before the production. The concept was a figure that channels energy outside sanctioned channels — something that operates by its own rules and derives its power from not asking permission. The production became an attempt to translate that idea into sound: aggressive, unresolved, operating at the edge of what I'd normally allow. The forbidden part isn't decorative. It's structural.

Why is "(Nasty)" in the title?

The first completed version of the track was too controlled for what the title promised. The (Nasty) subtitle marks the rebuilt version — the one where I pushed the saturation past where I'd normally stop, let certain elements clip intentionally, and accepted the result rather than cleaning it up. It's a descriptor for the version of the track that actually earned the name. There's no clean version. This is the one that exists.

What is the production approach on the drop?

The drop is built around an unresolved bassline — note choices that sit at the edge of dissonance without fully tipping into it. This creates sustained tension rather than payoff. Combined with an aggressive, brittle high end and scooped mids, the frequency balance is physically uncomfortable in a specific way. That discomfort is the point. The track is not trying to be pleasant. It's trying to be present.

Why does the track go nearly silent in the middle?

The near-silence section two-thirds through resets perceptual context before the final section. Without it, the ending is just more of what came before. With it, the same material sounds like something new — the quiet recalibrates what "loud" means. The stillness is part of the ritual, not a break from it. A shaman who never stops moving isn't channeling anything; they're just thrashing.