Why I Built MixDiagnose

I started out as a producer. Not a mastering engineer — a producer. I'd finish a mix, feel pretty good about it, send it off to mastering, and get back the same notes every single time: "too muddy in the low mids", "stereo width is off on the highs", "LUFS are too hot, pull it down 2 dB."

And every time, I'd think: why couldn't I have caught that myself?

The problem is that producers can't see what's wrong. You can only hear it. And ears lie — especially on monitors that aren't telling you the truth, in a room that's flattering the bass, after you've been listening for six hours and your brain has decided everything sounds fine.

So I started building something that would give me an objective diagnosis before I paid for mastering. Not a vibe check. Not a "sounds good to me." Actual measurements: where's the mud, where's the harshness, what's my LUFS, is my stereo width collapsing, is my dynamic range flat.

That became MixDiagnose.

"You shouldn't have to be a mastering engineer to know if your mix is ready."

That's the whole philosophy. MixDiagnose won't make your mix for you. It'll tell you what's wrong, show you where, and grade how bad it is — so you can fix it yourself before you spend money on mastering, or before you upload something you'll regret.