Why Your AI Track Stops at 18 kHz

Put a spectrum analyzer on a lot of AI-generated songs and you'll see the same shape at the right edge. The energy runs along normally, then drops off a cliff somewhere around 18 kHz. Above that line there's almost nothing.

When I measured my own work in October, 28% of the masters and 22% of the unmastered files had a steep roll-off between about 17.7 and 18.6 kHz. That's not a few odd files. It's more than one song in four.

Where the cliff comes from

It comes from the source. The generator, or the way it encodes the audio it hands you, cuts the very top before you ever download anything. A brick-wall cutoff that sharp is a classic sign of lossy encoding, the same thing an MP3 does to save space. You see it in WAV downloads too, because a WAV made from audio that was already cut keeps the cut.

The masters show it slightly more often than the raw files. That isn't mastering causing it. The two groups aren't the same songs, and some albums have more masters than raw files in the set, so the numbers don't line up one to one.

Mastering can't put it back

Once the information above 18 kHz is gone, it's gone. EQ can only turn up what's there, and turning up nothing gives you nothing. An exciter or a saturation plugin can generate new high harmonics from the material below, and sometimes that adds a little air, but it's new sound, not the original top end. Push it and you get a fizzy, brittle sheen that's worse than the cliff.

So when someone asks me to "open up the top," I'll check where the content actually stops before I promise anything.

Does it matter?

Less than it looks. Most adult hearing doesn't reach 18 kHz, and lossy streaming formats trim the extreme top anyway. A track that stops at 18 kHz can sound bright and finished.

Where it does show is when the cutoff is lower, down around 15 or 16 kHz, or when it's uneven. Cymbals lose their shimmer, breaths sound clipped, and the whole song feels a little boxed in next to a commercial reference. Track Lab marks a roll-off below 17.5 kHz as worth a look and below 15.5 kHz as a problem.

What you can do about it

Check before you send. Drop the file into a free spectrum analyzer or into Track Lab and look at the right edge.

If the cliff is there, look for a better source. Download the WAV from the desktop site rather than the phone app, and compare a second export of the same song. If every version stops in the same place, that's the generator, and it's fine to move on.

Don't try to fix it yourself with an exciter before mastering. Send the honest file and tell me you noticed it. I'd rather work from the real top end, cut and all, than from one that's been faked.

The top of the spectrum is decided before mastering starts. Look at it while you can still pick a different file.

Josh, Founder, JG BeatsLab

Want this handled on your track? I master AI-generated music by hand, one song at a time, and every master comes with a Mastering Dossier that shows what I did and why. Book mastering or take the 3-minute scorecard to see where your workflow stands.

JG BEATSLAB SCORECARD

Where does your AI music workflow stand?

Ten questions, about three minutes. You'll know which stage you're in and what to fix first.

Take the scorecard

Or get the free guide.

Previous
Previous

How a Song Should End

Next
Next

Stems or a Stereo Mix? What to Send for Mastering