Use the Exclude field without over-constraining

Exclude is the field people reach for after a disappointing take, and it is the easiest one to misuse. It works — but it competes for attention with everything you asked for positively, and a long exclusion list reliably makes results worse rather than cleaner.

Exclude removes; it does not steer

An exclusion says "not this." It does not say what to do instead.

auto-tune removes a processed vocal character. It does not produce a warm natural vocal — that has to come from the vocal direction in Style. If you exclude something and do not replace it with a positive instruction, the model fills the gap with whatever the genre defaults to, which is frequently the thing you were trying to avoid in the first place.

The reliable pattern is a pair: exclude the character you do not want, and state the one you do.

Exclude what happened, not what might

The useful entries in an exclusion list come from listening, not from imagination.

After a take where the vocal arrived drenched in reverb, heavy reverb is a precise, earned exclusion. Adding heavy reverb, distortion, auto-tune, lo-fi, muddy mix, clipping before you have generated anything is guessing, and each guess spends attention that the positive instructions needed.

Three or four entries is a lot. Beyond that you are usually describing a style problem that belongs in Style.

The cases where it is genuinely necessary

Two situations where an exclusion is not optional:

Instrumentals. vocals in the Exclude field is what stops stray humming, ad-libs and wordless vocal pads. Leaving the lyric box empty is not sufficient — models frequently add a vocal texture anyway because the genre implies one. This is the single most common reason an "instrumental" comes back with singing on it.

A specific recurring artefact. If the same unwanted element survives two or three versions despite changes to Style, name it explicitly. At that point it is not noise, it is a default the genre keeps reasserting, and only an exclusion will displace it.

When exclusions stop helping

If you have four or more entries and results are still wrong, the exclusion list is not the problem.

A long list is usually a symptom: the positive description is too vague, so the model is falling back on genre defaults, and you are trying to subtract your way to a sound instead of describing it. Fixing the Style line — a more specific genre, a named instrument, a clear vocal direction — will do more than another exclusion.

Leave the field empty when you have nothing real to put in it. An empty Exclude field is not a missed opportunity, and there is nothing to paste into Suno when it is empty. Constraints you did not need still cost you.

How this fits the loop

Treat an exclusion like any other change: add one, generate, listen. If the artefact is gone and nothing else got worse, keep it. If the take got flatter or more generic, the exclusion was competing with something you wanted — remove it and fix the positive instruction instead.

That is the same discipline as changing one variable at a time, applied to the field where it is most tempting to skip it.