{"id":18,"date":"2026-03-01T17:23:36","date_gmt":"2026-03-01T15:23:36","guid":{"rendered":"https:\/\/charagma.co.za\/wordpress\/?p=18"},"modified":"2026-03-01T17:23:36","modified_gmt":"2026-03-01T15:23:36","slug":"missing-in-action","status":"publish","type":"post","link":"https:\/\/charagma.co.za\/wordpress\/index.php\/2026\/03\/01\/missing-in-action\/","title":{"rendered":"MISSING IN ACTION"},"content":{"rendered":"\n

Yes\u2026 the last post was about three weeks ago. I spoke about how busy I was with the \u201cBreaths of Wood\u201d<\/em> album, how things were progressing \u2014 and then disaster hit.<\/p>\n\n\n\n

Let me settle you immediately: this was industry disaster, not personal disaster. (Not an excuse but LIFE)<\/p>\n\n\n\n

Murphy\u2019s Law #8756576599: \u201cIf something can go wrong\u2026 it will.\u201d<\/p>\n\n\n\n

First up: WordPress.
Suddenly several problems started crawling out of the woodwork. Before anyone panics \u2014 this was not WordPress doing something wrong. It was simply a misalignment between me and the platform at this stage of my journey. I\u2019ll get back to that.<\/p>\n\n\n\n

Then SoundCloud.
Their automation system and I had a disagreement. Not their fault. Not my fault. But somewhere in between, we just could not find common ground to solve it.<\/p>\n\n\n\n

And then the label\u2026
\u201cYou know your deadline is Friday\u2026 so where is it?\u201d
My reply: \u201cI\u2019m having some technical issues.\u201d
Their reply: \u201cPlease indicate in our contract where that became my problem. This sounds like a YOU problem, not a ME problem.\u201d<\/p>\n\n\n\n

Fair enough.<\/p>\n\n\n\n

That said \u2014 a lot changed in those three weeks.<\/p>\n\n\n\n

I met the deadline. Just.
Shifted a few platforms around.
And then decided to go big or go home.<\/p>\n\n\n\n

I bought a domain. (YIPPPppppeeeee!!!)<\/p>\n\n\n\n

Welcome to Charagma HUB<\/strong> \u2014 a name suggested by Jodie (and honestly, it fits perfectly).<\/p>\n\n\n\n

For clarity: I am still using WordPress. I simply moved from the old Charagma1 address to my own domain. That alone already changes the game.<\/p>\n\n\n\n

Now here is the important part.<\/p>\n\n\n\n

Before anyone assumes everything collapsed \u2014 let\u2019s turn the table.<\/p>\n\n\n\n

There comes a time in your life when you outgrow a tool. The tool still works exactly as it should\u2026 it just no longer serves what you need.<\/p>\n\n\n\n

Think about your first microphone.
It still works. Probably perfectly.
But at some point you move to a cardioid condenser \u2014 not because the first one failed, but because your standards, your workflow, and your expectations evolved.<\/p>\n\n\n\n

Platforms are no different.<\/p>\n\n\n\n

Over the past few weeks I learned more about platform automation than I ever expected to. It was uncomfortable. It was messy. But it made something very clear:<\/p>\n\n\n\n

Just like a microphone, a platform can be outgrown.<\/p>\n\n\n\n

As we grow in the industry, certain features stop being luxuries and become necessities. And when there is friction in the system, growth demands movement.<\/p>\n\n\n\n

So yes \u2014 over the next few weeks you will notice changes.<\/p>\n\n\n\n

At one point, all my tracks will temporarily disappear from various DSPs. It will look dramatic. It might even look alarming. But they will return through a new distributor once everything is properly aligned.<\/p>\n\n\n\n

The HUB (www.charagma.co.za<\/a>) is still under construction, but sections are already live and opening as I progress. Contact details are active, so if a link fails during this transition, you can still reach me directly.<\/p>\n\n\n\n

The album is done.
The infrastructure is shifting.
The foundation is being rebuilt stronger.<\/p>\n\n\n\n

This is my first post from the new WordPress.<\/p>\n\n\n\n

Exciting.
A little scary.
Necessary.<\/p>\n\n\n\n

Thank you for staying through the shift.<\/p>\n\n\n\n

Lastly “Welcome to Charagma HUB.”<\/p>\n\n\n\n

This is my latest release. Hope you enjoy it. It is part of the future Avalon Album.<\/p>\n\n\n\n

\n