Why Your Cue Falls Apart the Second the Director Plays It on a Laptop

You spend three weeks on a cue. You send it. The director plays it on the laptop that is open in front of them, and comes back saying it feels empty.

They are not wrong, and neither are you. They heard a different piece of music from the one you wrote.

Know What the Laptop Actually Removes

A typical laptop speaker produces almost nothing below 400Hz. Not less. Nothing.

Work out what that deletes from an orchestral cue. Double basses, gone. The bottom of the cello section, gone. Timpani, gone except for the stick noise. The left hand of the piano, gone. Every low synth pad holding the harmony together, gone.

What is left is the upper harmonics of those instruments, which is why the cue is still recognisable while feeling hollow. The ear reconstructs a suggestion of the missing fundamentals from their harmonics, so the director hears something thin rather than something broken, and describes it as empty because that is genuinely what it is.

The friction is that this is invisible in your room. Whatever you monitor on goes lower than a laptop, and the better your setup the wider the gap between what you approved and what they played.

Run the 400Hz Test Before Every Send

This takes fifteen seconds and it is the single most useful habit in this guide.

Put a high-pass filter on the master bus at 400Hz, 24dB per octave, and play the cue. You are not fixing anything, you are auditioning what the client will get.

Then judge one thing only: does the cue still make its point. Not whether it sounds good, it will not, but whether the shape, the harmony and the emotional direction still arrive.

If they do, you are fine. If the cue becomes aimless, the material carrying it lives below the client's playback and you have a real problem to solve rather than a mix to tweak. Take the filter off before you render, obviously, and the annoyance is exactly that: leaving it on and shipping it has happened to everyone who uses this test.

Playing connects you to YouTube, which may set cookies.

Put the Identity Between 500Hz and 4kHz

Every playback system in the chain reproduces the midrange. Laptop speakers, phone speakers, car stereos, the cheap monitors in an edit suite, all of them.

So whatever makes the cue itself has to be in that band. Not everything, but the identity: the melodic line, the harmonic movement that carries the emotion, the rhythmic figure that gives it drive.

This is an orchestration instruction rather than a mixing one. If your cue's identity is a sub drone and a low ostinato, no mix decision will move it into the midrange, and the writing has to do it.

The cost is that a midrange-heavy cue can feel small on good monitors, which is where the balancing act lives. The answer is not to choose one, it is to build the cue so it works in the midrange and then add the low end as reinforcement rather than as foundation.

Give Every Low Line an Upper-Octave Partner

The practical technique that follows from all of the above.

A double bass line alone dies on a laptop. The same line doubled by cellos an octave up survives, because the cello octave sits where the speaker works, and the ear hears the bass through it. On a full system you get both and the cue is unchanged.

The same trick applies everywhere. Timpani doubled quietly by a low tom with more stick. A sub drone doubled by the same pitch class two octaves up at a much lower level. A piano left hand supported by a cello line rather than left to carry the harmony alone.

Keep the partner well under the original, often 8 to 12dB down, so it is not audible as a separate part on good monitoring. It is not there to be heard. It is there so that something is heard when the fundamental is gone.

The catch is that this thickens the midrange, which is already the most crowded part of an orchestral mix, so every doubling you add competes with the melody. Add them deliberately, one at a time, checking the 400Hz test after each.

Check in Mono, Quietly, Every Time

Laptop speakers sit a few centimetres apart and are effectively mono at any listening distance. So a mono check is most of a laptop check, and it catches two other problems on the way.

Sum to mono and listen at conversation volume. Anything that vanishes was living in the sides, which for orchestral libraries usually means the hall reverb and the wide microphone positions. Anything that suddenly sounds crowded was being separated by width rather than by frequency, and width is the first thing the client loses.

Conversation volume matters as much as mono. Masking is worse at low levels for low frequencies and better for midrange, so quiet playback is a closer model of a laptop than loud playback through one speaker.

The friction: you will not enjoy this check, and it is tempting to skip it on the cue you feel best about. That is the one it catches.

Do Not Mix on the Bad Speaker

One thing this guide is not saying: none of this is an argument for working on laptop speakers.

Mix on the best monitoring you have, because that is what tells you what is actually in the file. Check on something small and unflattering, because that is what tells you what survives. The two jobs are different and the mistake is doing both on the same speaker.

Composers who mix on small speakers overcompensate in the low end almost without exception. The cue then sounds correct on the laptop and bloated on a stage, which is a worse failure than the one they were fixing, and much harder to hear coming.

Then Tell Them What to Play It On

Last, and it is not a mix technique at all.

When you send a cue, say what it wants. One sentence asking them to listen on headphones or proper speakers where possible costs nothing, and it converts a fraction of the empty-sounding feedback into feedback about the actual music.

It will not work every time, because a director watching a rough cut on a laptop is going to play it on the laptop. Which is why the four checks above exist, and why they run before the email rather than after the reply.