For The Record

The TruthA Statement From The Author

Published May 2026  ·  Lord Cornelius "Void-Pointer" Flesh-Meld III

01 // Authorship

What I Built, and Who Built It

My name is Lord Cornelius "Void-Pointer" Flesh-Meld III — known online as youarethecarbontheywanttoreduce and as Crüe on Discord. I am the primary author of the Discord Stereo Patcher — a native Swift macOS application that removes Discord's aggressive audio filters, restores true stereo, and unlocks high-bitrate Opus.

I believe in giving credit where it is due, and I will do that plainly. The foundational offset research for the Windows platform was not mine. That groundwork was laid before me by a community of researchers, and their contributions deserve acknowledgment. Those individuals are:

The offset finder tool in its original form was created by ProdHallow. I want to be clear about that. What I then did — with the assistance of AI tools and my own sustained reverse engineering research — was adapt and rebuild that offset finder to work correctly for macOS, discovering the correct macOS-specific offsets myself. I was the first person to accomplish this. ProdHallow later made his own attempts to do the same without success, and it was I who subsequently provided him with the working scripts through our DM conversations. His own commit history and our conversation records reflect this timeline clearly.

Geeko did some early research alongside me as well, and I acknowledge that. The macOS-specific breakthroughs — the offset discovery, the krisp.node workaround, both the ARM64 and Intel x86_64 patches, and the Swift application itself — are my work, achieved through sustained personal investment in research, tooling, and development time.

I also want to be clear about this: using AI as a development tool does not strip a developer of authorship. A carpenter who uses a power saw still built the cabinet. I directed every decision, debugged every failure, and made every call. The macOS application is mine. The Codeberg organization is mine. The macOS work is mine. The record reflects this.

02 // The Collective

How ProdHallow Entered the Picture

ProdHallow — handle prod.hallow on Discord — approached Geeko and me about joining something called the "Discord Audio Collective." He and his associate UNP Beats UK were persistent about wanting access to our work and wanting us to fold ourselves into their project.

We came to an agreement. That agreement included several specific terms, all acknowledged by all parties in a voice call: the code was not to go on GitHub — it was to remain on Codeberg only. Additionally, I was not to publish the Swift build files or make everything public until the software was polished and confirmed ready. These were not suggestions. They were agreed-upon conditions.

The v29 patcher was completed around February 19th. Within the first week or two of March — not long after those agreements were made — Geeko shared the v29 patcher in a Discord voice call side chat with another user, without asking my permission beforehand. I had explicitly stated it was not ready for distribution. It still needed work. He gave it out anyway. That was the first violation of the trust and terms we had agreed upon.

Approximately a month after those initial agreements, there was a voice call in which ProdHallow was disrespectful toward me — and not once. The context matters: he was in conversation with another user in that call about addressing an audio problem. I mentioned that a VST plugin could handle what they were describing. His response was to invoke his audio engineering degree and professional background at me — not for the first time, as I had heard it before and never forgotten it — in a way that was dismissive and condescending. I responded with measured sarcasm. I stated plainly that I too have years of experience, that having a degree in a different field does not mean I do not know what I am talking about, and that unsolicited credential-wielding directed at a collaborator is not something I will simply absorb in silence. He pivoted and proceeded to attempt to pull the ol' "comparing apples and oranges". At that point after saying a few more words, I disengaged. I did not explode. I did not rage. I walked away from a situation that was beneath me, because that was the correct and measured thing to do.

Geeko was in that call at the time of my having joined it. He left within minutes of me arriving, before any of the above transpired. He was not present for what happened between ProdHallow and I, and therefore had no direct knowledge of the specifics of that interaction.

03 // Neutrality

On Geeko's "Neutrality"

In the days and weeks following the incident with ProdHallow, I reached out to Geeko multiple times with my concerns. I preferred voice calls — not because I was avoiding a written record, but because the volume and nuance of what I needed to express made a live conversation far more practical than trying to type it all out or wrestle with dictation corrections. We did have a voice call at one point in the guitar server. I told him directly that I was considerate of his time and his new job, and he acknowledged that plainly. I also told him that I felt there was a disconnect — that I didn't feel understood — and his response was an acknowledgement and a subject change. That stayed with me.

I removed Geeko from the Codeberg organization after I had already blocked him on Discord that day — the removal came after the blocking, not before. I am clarifying this because the sequence matters. By that point it was clear that his position was one of managed distance, and our conversation had reached its end.

I want to be fair to him on one thing: I was always more than accommodating of his pace and his priorities. Development was supposed to be relaxed. He had a new job. I held none of that against him, and I said so to his face. What I could not accommodate was silence in the face of something that directly affected me and the project we had built together — and his eventual escalation into outright attack.

After I had already blocked him, Geeko sent me the longest and most cutting message of our entire relationship — into the void, knowing I would not receive it in real time. In it he called me emotionally immature. He called me a child. He made ageist remarks. He fabricated incidents — including a claim that I had publicly ranted about Claude Opus in some embarrassing way. For the record: any frustration I have ever expressed about Claude Opus was specifically about it producing incorrect outputs in spite of carefully constructed prompts. That is a developer's legitimate technical grievance, not the erratic behavior he was implying. I also have years of programming experience and am not solely a vibecoder — that characterization is simply not accurate.

He dismissed my standing up for my own work as a "pissing match." He told me to keep my Intel patches and "my goddamned fork" — as though the Intel patches, and the ARM64 patches alongside them, were minor footnotes rather than the entire macOS foundation of this project. He told me he was "done being my therapist" — a role he invented for himself in that message and never played in reality. He ended by telling me not to call him again — directed at someone who had already blocked him. Then he told ProdHallow he was available to work on macOS patches on his schedule — using the groundwork I had laid.

04 // The Record

Addressing ProdHallow's Public Statement

ProdHallow made a public statement to his server addressed to @everyone. I am going to address it directly and completely, because it contains distortions I am not willing to let stand unchallenged.

His Claim — Point 1 "Me and Crue worked together on Stereo Hub since it was originally his idea."
This is a deliberate conflation of two separate things. I gave him the concept of having his autopatcher pull pre-patched macOS nodes from my patcher's output, and I shared the krisp.node workaround I had already built. That is consultation. That is not co-developing Stereo Hub. I was building my own separate Swift application on Codeberg. He was building a Python autopatcher he branded as Stereo Hub. These are not the same project. The word "together" is being used to manufacture shared ownership over work that is distinctly mine.
His Claim — Point 2 "He constantly talked negatively about people behind their backs. I have receipts."
Vague, unsubstantiated, and designed to poison the well without producing specifics. "I have receipts" without producing them is a rhetorical trap, not evidence. I am outspoken. I am direct. When users in a support context were being deliberately obstructive, refusing to follow clear instructions, and choosing to be confrontational with the people trying to help them — I expressed frustration. So did ProdHallow. I have the screenshots to demonstrate that he expressed similar frustrations in exactly the same way. The difference is that I am not deploying it as a weapon against him.
His Claim — Point 3 "This situation started because I refused Crue's input and advice regarding my personal audio routing."
This strips the actual substance out of what happened. He reduced the incident to a simple disagreement about audio routing in order to make me look petty and ego-driven. What actually happened is that I made a reasonable suggestion about a VST, and he responded by invoking his audio engineering credentials at me in a dismissive and condescending way. Not just once was I disrespected, but three separate times in that call, in three separate ways.. I responded with measured sarcasm, stated my own experience and standing plainly, and disengaged when it was clear the environment was not a respectful one. That is not someone who cannot handle disagreement. That is someone who will not accept being talked down to by a collaborator.
His Claim — Point 4 "Crue personally sent me the source code and stated that as long as I did not upload it to GitHub, it was fine, which I respected."
To be precise and fair: ProdHallow has not yet placed my code on his GitHub repository. He has linked to the Codeberg organization, given me credit, and acknowledged my work there — and I recognize that. My concern is not what has already happened. It is what his public statements suggest may happen going forward, now that I have removed myself from the collaborative arrangement. Geeko already violated the agreed terms once by distributing the v29 patcher without my permission. The agreements we made in that voice call — that the code would not go to GitHub, that the Swift build files would not be made public until the software was ready — were verbal agreements that were already broken once. ProdHallow's GitHub repository has a MIT-style license with "Discord Audio Collective" listed as copyright holder — an entity with no legal copyright — already in place as the architecture for that project. My CC BY-SA 4.0 license has existed on my Codeberg repository since its creation. If my code ever lands in that repository without compliance with those license terms, the violations are clear, documented, and actionable.
His Claim — Point 5 "If you make your project public and open source, then it is the end of it."
Legally incorrect. Open source licenses are contracts with specific, enforceable terms. CC BY-SA 4.0 requires: proper attribution to the original author, use of the same license on all derivative works, and inclusion of a copy of the license. "Open source" does not mean anyone can do anything with the work. It means specific rights granted under specific conditions. Those conditions are not negotiable and are not erased by the existence of a public repository.
His Claim — Point 6 On AI and vibecoding — implying AI-assisted development delegitimizes authorship.
I will own something here: when I returned to the server and saw negative things being said about me publicly, I reacted by calling him a vibecoder. That was reactive and petty, and I own it. It was said in direct response to a user pointing out that his newly uploaded version was broken immediately after release — and it was not categorically untrue. What I will not accept is the implication that AI-assisted development strips authorship from the person who directed the work. I have years of programming experience. I am not solely a vibecoder. Any frustration I ever expressed about Claude Opus was specifically about incorrect outputs in response to well-constructed prompts — a legitimate technical grievance, not erratic behavior. Furthermore, the macOS offset finder in its current working form is my work, rebuilt and adapted for macOS through my own research. The file discord_stereo_patcher_gui.py that ProdHallow has in his possession carries the header "Finalized and made working by Crue." That is the record.
On the server ban: ProdHallow banned me from a server that Geeko and I built and owned together. When I returned to respond to people who were publicly saying negative things about me — people I had done nothing to — he told me that if I was going to "come back starting drama," he would ban me. He then told me I should be grateful that he still had my name on his repository page. Let it be known that after I stood against all of this behavior and blocked both of them that he has continued to use my name, without my permission, on his main repo to lend credibility to his own separate project and "collective", and then told me to thank him for the privilege. I do not require his nor anyone elses' permission to defend my own name, and I have nothing to be grateful for relating to a remark such as that.
On UNP Beats UK and "oma": By ProdHallow's own private admission, UNP Beats UK was taking their collective's work, modifying values, and slapping his name on it. He was then given admin access to the server. He subsequently declared publicly that he felt "bad energy" around me. Whether or not he has specifically benefited from my work to date, the principle stands: a person who appropriates other people's work without permission has no credibility when passing judgment on those whose work stands to be taken. "Oma" stated I had no license in my Codeberg repo — I had made the organization private specifically to protect the code. Absence of public visibility is not absence of license. My CC BY-SA 4.0 license has existed since the repository was created.

05 // Closing

Who I Am and Where I Stand

I am not going to apologize for being passionate. I am not going to apologize for being outspoken. I am not going to apologize for standing up for my work, my name, and my dignity when all three were being handled carelessly by people I had extended trust to. I have a zest for life and a directness in how I move through the world that I will not sand down to make other people comfortable.

What I will say is this: I do not offend intentionally. I have never set out to harm anyone in this situation. I prefer a strong defense to a weak offense. When someone extends respect to me, I return it tenfold. When someone comes at me with deliberate disrespect, I am going to say something. That is not emotional immaturity. That is self-respect. I can only control how I present myself — not how someone else chooses to perceive me. I will not carry the weight of someone else's mischaracterization of who I am.

The Discord Stereo Patcher is my macOS application. The Codeberg repository is my repository. The macOS work is my work. That is not changing. Anyone who wishes to build on this project is welcome to do so within the terms of CC BY-SA 4.0 — proper attribution, the same license on derivative works, no stripping of copyright. That is not a negotiation. It is the law as written.

I have not filed a DMCA takedown notice, and I do not want to. What I want is simple: decency, respect for the work, and compliance with the license terms if my work is going to be used. So long as that holds, I have no interest in escalation. If it does not — if my code ends up somewhere it was agreed it would not go, under a license it was never released under, with my name stripped from it — I will do what I have to do. That is within my rights, and it has nothing to do with petty back and forth. It has to do with the law and the truth.

The truth does not require a majority vote. It only requires someone willing to say it.

Lord Cornelius "Void-Pointer" Flesh-Meld III
youarethecarbontheywanttoreduce  ·  May 2026  ·  [ Matrix ]