Should you mix loops before sending them to producers?

Should you mix a loop before sending it? Lightly, yes, or label it honestly as raw. What you should almost never do is master it: no limiter on the master bus, no loudness push, no squashing the dynamics. The collaborator is going to add drums and bass on top, and a loop that is already loud leaves them nothing to work with.

"Mixed or unprocessed" is a real choice, and both are useful to different producers. This guide covers what each one means for a loop, what to leave in and what to take out, how to treat the low end and the stereo image, and a checklist to run before you bounce.

What "mixed" and "unprocessed" mean for a loop

A loop is not a song, so mixing it is a smaller job than mixing a record. Producers commonly use the words like this:

• Mixed means the parts are balanced against each other, obvious EQ problems are fixed, light compression is gluing the sound together, and the effects that belong to the sound are printed into the file. It is ready to write over: drop it in a session, add drums and bass, and it holds together.
• Unprocessed means raw. Levels are rough, nothing is glued, effects may be missing, and there is plenty of headroom. It is for a collaborator who wants to do the mixing themselves and would rather not undo yours.

Neither is better. A mixed loop gets you to an idea faster. An unprocessed loop gives a producer with strong opinions more control. The mistake is sending one while implying it is the other.

Why most loops should not be mastered

Mastering, in the way most people mean it for a loop, is a limiter on the master bus plus a push towards commercial loudness. That is the wrong job for a loop, for three reasons.

• The loop is not the whole record. Drums, bass and often vocals are still to come. A loop already at the ceiling has no space for them, and the collaborator ends up turning your loop down, which wastes the work the limiter did.
• Limiting changes the balance. A limiter reacts to the loudest element. When the collaborator adds a kick under it, you cannot take the limiting back out; the squashed transients are in the file for good.
• Loudness is the last decision, not the first. It gets made once, at the end of the finished beat, by whoever finishes it.

The same goes for heavy clipping, aggressive saturation on the master bus and "loud" presets. If the loop only sounds good loud, it is a sign the sounds themselves need work.

Headroom, stated honestly

Leave real room between your loudest peak and 0 dBFS. There is no single correct figure, and anyone quoting one as a rule is simplifying. What matters is the principle: your peaks should sit well below 0 dBFS, and nothing on the master bus should be catching them.

• Take the limiter off the master bus before you bounce. If you are monitoring through one, bypass it for the export.
• Check the peaks on the master meter over a full loop pass, not just the first bar.
• If you are at 24-bit, quiet signals are safe to raise later, so lower peaks cost you nothing. The sample rate and bit depth guide explains why.
• Bounce at the level that leaves room, then name the file or label the upload so nobody thinks it is quiet by mistake.

A quiet loop is easy to turn up. A clipped loop cannot be turned back down into shape.

What to leave in and what to leave out

Treat the file as a part, not a product.

Leave in the things that are part of the sound itself:

• Character effects: a tape wobble on a sample, a phaser on the keys, a filter sweep that defines the hook, the reverb that makes a pad feel like a pad.
• Distortion or saturation that gives the sound its identity rather than its loudness.
• Pitch and time effects the melody depends on.

Leave out the things that belong to the finished beat:

• Master-bus limiting and loudness maximisers.
• A heavy low end that will fight a bass. If the loop is going to get an 808 or a sub, your own sub bass is competing with it.
• Reverb and delay throws that fill the gaps the collaborator needs for drums and vocals.
• Anything you cannot remove again later, like a long tail baked over the loop point.

The test is simple: would the loop be a different loop without it? If so, print it. If it is only there to make the loop sound finished, leave it off.

Low end and stereo image

The low end is where loops most often get in the way.

• High-pass where the bass will go. If the loop is a melody, chords or a sample, filter out the frequencies below where it really needs to sit. That clears the space a bass or 808 will use. Do it gently and listen with the full loop playing.
• Keep what remains in the low end mono. A common convention is that sub and bass frequencies are centred. Wide low frequencies cause phase problems and weaken on mono speakers.
• If you are not sure the low end is wanted, say so. A loop that includes its own bassline should say so in the title or the notes, because a collaborator will either keep it or mute it.

For width, widen the highs rather than the lows. Panned guitars, stereo pads and wide reverbs are fine, but check the loop in mono before you bounce. If the melody disappears or sounds hollow when summed, a stereo effect is cancelling itself out and the collaborator will find out the hard way, perhaps on a phone speaker.

Print the effects or send it dry?

There is no universal answer, but there is a way to decide.

• Print effects that shape the sound: if the loop is recognisable because of the delay on it, bake it in.
• Send dry when the effect is something the collaborator may want to change, such as a long reverb on a lead that will have a vocal on top.
• Offer both. If a loop depends on its effects but a collaborator would reasonably want the dry version, say you can send stems or a dry bounce.

Send it Mixed if... send it Unprocessed if...

A decision list, since most producers end up here anyway.

Send it Mixed if:

• The balance between the parts is part of the idea.
• You already know the EQ choices are right and would not want them undone.
• You want the loop to sound good in the first ten seconds, to someone who has not got a session open yet.
• The loop is meant to be dropped straight over and written on top of.
• You do not expect the collaborator to want to rework the sounds.

Send it Unprocessed if:

• The sounds are rough and you would rather the collaborator shape them to their own beat.
• You are unsure about levels or EQ and would rather not lock in a mistake.
• The loop is a sketch or a starting point, and the rest of the character will come later.
• You are looking for a collaborator who likes to mix, such as someone who wants to run the loop through their own chain.
• You would rather leave every decision about loudness and tone to them.

If you are torn, send it mixed lightly and keep the headroom. A balanced loop with room left over is usable in almost every case.

A pre-bounce mix checklist for a loop

Run through this before you export.

1. Master bus limiter and clipper bypassed or removed.
2. Peaks checked across the whole loop pass, with clear headroom below 0 dBFS.
3. Parts balanced against each other, with nothing dominating the rest.
4. Low end high-passed where a bass or 808 will go.
5. What is left of the low end is centred, and the loop checked in mono.
6. Harsh resonances tamed with EQ, without taking the character out of the sound.
7. Light glue only: gentle bus compression, with the transients still alive.
8. Character effects printed, loudness effects left off.
9. Reverb and delay tails fade out, or wrap cleanly across the loop point.
10. Exported as a WAV at your project's sample rate, 24-bit, and named with its key and tempo as in naming your loop files.

Label it so they know what they are opening

A collaborator who thinks they are getting a mixed loop and opens a raw one will assume something is wrong with it. The reverse is worse: they start mixing a loop that was already treated, and double up compression and EQ. The label fixes that.

Put it where they will see it before they download: in the title or the first line of your message. Say which it is, and mention anything that matters, such as whether it has its own bassline or whether stems exist. Sending loops to producers covers the rest of the packaging.

How this works on ColabLoop

When you upload a loop to ColabLoop, you tag its mix state. "Mixed" means levels, EQ and glue are done and it is ready to write over. "Unprocessed" means raw, with headroom left in, for a collaborator who wants to mix it. Neither is the default, so you choose, and the label shows on the loop's page so a collaborator knows what they are opening before they ask to build on it.

You can see the same tag on other producers' loops while you browse. Browse the loops and look for the one that matches how you like to work.

Questions producers ask

Should I master my loops before sending them?

No. Mastering means limiting and loudness, and the collaborator still has to add drums and bass. A loop that is already loud leaves them no room, so keep the master bus free of limiters and leave real headroom.

How much headroom should a loop have?

There is no single figure, so avoid anyone who gives you one as a rule. Keep your peaks well below 0 dBFS with nothing limiting the master bus, and export at 24-bit so that turning it up later costs the collaborator nothing.

Should I send stems with my loop?

Offering them is a good idea if the loop's balance is likely to be a sticking point, such as a loop with its own bassline. Whichever bounce you send first, make it the one you would be happy to hear built on.

Should I put a high-pass filter on a loop?

If the loop is a melody or a sample and a bass will go underneath, a gentle high-pass clears that space. Keep whatever low end remains centred, and listen to the loop in mono afterwards to check nothing has hollowed out.