A music quiz over a video call fails in a specific, predictable way, and it is almost never the quiz’s fault. It is the audio. The host presses play, the room hears something that sounds like a radio underwater, and half the guesses are wrong for reasons that have nothing to do with knowing the song.
Two things cause it, both fixable in under a minute once you know what they are. Then there is a third problem — delay — which is not fixable at all, and which means one rule of the in-person game has to be thrown away.
Problem one: voice processing is destroying the music
Every video-call platform runs aggressive processing on your microphone by default: noise suppression, echo cancellation, automatic gain control. All three exist to make a human voice intelligible in a bad room, and all three are actively hostile to music.
Noise suppression treats sustained non-speech sound as noise, which is a fair description of a cymbal, a synth pad or a bassline. Automatic gain control ducks the volume the moment anyone speaks. Echo cancellation removes whatever it thinks it has heard before, which includes the loop the song is built on.
So if you play music into your microphone — phone speaker pointed at a laptop, or just the song playing in the room — the platform will systematically dismantle it. The music arrives thin, wobbly and missing exactly the parts people recognise songs by.
Never hold a phone up to the microphone
It is the first thing everyone tries and the worst available option. It stacks every processing artefact on top of room reverb and the phone speaker’s own limits. If you take one thing from this page, take this one.
Problem two: you are sharing video, not audio
Screen sharing does not share sound unless you explicitly tell it to, and the checkbox is easy to miss because it appears in the share dialog rather than in settings. What each platform calls it:
| Platform | What to enable |
|---|---|
| Zoom | In the share window: Share sound, then choose High fidelity music mode in its dropdown. Also turn on Original sound for musicians in audio settings. |
| Google Meet | Share a Chrome tab rather than a window or the whole screen, and tick Also share tab audio. Only tab sharing carries audio. |
| Discord | Screen share carries application audio on desktop. Raise the server or channel bitrate if you can; Discord is the most forgiving of these for music. |
| Teams | Include computer sound in the share tray. It is off by default and resets between calls. |
Sharing computer sound rather than microphone sound also bypasses problem one entirely: the audio never goes through the voice pipeline, so nothing suppresses it. This is the whole fix, and it is why browser-based games are much easier to run over a call than anything playing out of a speaker in your room.
Problem three: delay, which you cannot fix
Everyone on the call hears the clip at a slightly different moment, and the spread is not small — comfortably enough to decide a race. Someone on hotel wifi may be a second or more behind someone on fibre. Nothing you configure changes this; it is the network.
Which means first-to-shout does not work over a video call. It is not slightly unfair, it is measuring connection quality. Any competitive format that resolves ties by speed is broken here.
Three formats that survive it:
- Written rounds. Everyone writes their answers privately — paper, notes app, a private message to the host — and they are revealed at the end of the round. Nobody is racing anybody, so latency stops mattering completely. This is the default for remote play and it should be.
- Teams in breakout rooms. Play the clip to everyone, then send teams to breakouts for ninety seconds to agree an answer. Slower, and much more social — the discussion is the entertainment, not the guessing.
- Second-device buzzers. Players buzz on their own phone against a shared clock rather than through the call. Still imperfect, because the audio arrived at different times, but far closer than shouting into a microphone.
More on why format choice matters more than difficulty in the rules and variants guide.
A pre-call checklist
- Test with one person before everyone arrives. Five minutes earlier, one friend, one song. Every problem on this page is obvious within ten seconds of a real test and invisible without one.
- Ask everyone to use headphones. Not for their benefit — for yours. Speakers mean the song comes back into their microphones and gets re-transmitted a beat late, which is what turns a clean clip into a smear.
- Mute the room by default. Guessing happens in the chat or on paper. Fifteen open microphones on a call is not a quiz, it is a noise floor.
- Use longer clips than you would in person. Add five to ten seconds. Compressed audio over a call is genuinely harder to identify than the same clip in a room, and you are compensating for the medium rather than making it easier.
- Have the answers where you can see them. You cannot read the room over a call, so you cannot tell whether silence means thinking or means your audio dropped. Being ready to move on quickly is the substitute.
What to do when the audio fails mid-game
It will, once. The recovery is to stop immediately rather than play three more songs hoping it settles: re-share, confirm with one person that they can hear it, then replay the song you lost. A round played through broken audio is a round everybody scores badly on for no reason, and it takes the energy out of the rest of the night far more than a two-minute pause does.
If the clip itself is missing rather than the audio route being wrong — one song silent, the rest fine — that is a different problem with a different fix, covered in why one song has no clip when the rest of the playlist does.
GuessSong turns any public Spotify playlist into this game. No login, no app, no sign-up.
Start a game →Read next
- How to Host a Music Quiz Night That People Actually Enjoy — A practical guide to running a music quiz for friends: how long a round should be, how to seat the room, what to do about the person who knows every song, and the five mistakes that flatten a good night.
- Why One Song Has No Clip When the Rest of the Playlist Does — Five reasons a single track goes silent in a Spotify-based music game — remaster suffixes, differently credited artists, rotated URLs, catalogue gaps and throttling — and how to tell which one you are looking at.
- Twelve Music Quiz Rounds That Are Not “Name That Tune” — Twelve rounds that need nothing but a playlist and a host, sorted by what they do to a room: what each one tests, who it lets win, and where it belongs in a running order.