Conference audience watching a panel on stage

Why Panels Are the Hard Case

A single presenter reading a script is the easy case for dubbing. One voice, clean turns, predictable pacing, no ambiguity about who is speaking.

A panel discussion inverts every one of those properties. Four or five people, unscripted, interrupting each other, finishing each other's sentences, laughing over answers, talking across a moderator who is trying to move things along. Add a room microphone picking up all of them at once, or lapel microphones with substantial bleed between them, and you have audio where the speech of two people is genuinely mixed in the same signal.

This matters commercially because panels are a large share of the content organisations most want to localize. Conference libraries, webinar archives, executive roundtables, expert interviews, podcast episodes with guests. The content is valuable, the format is difficult, and the gap between a good result and a bad one is wider than for scripted content.

The good news is that most of the difficulty is concentrated in a small number of identifiable problems, each with a known approach.

Separation Comes First

Everything downstream depends on knowing who said what, and when.

Diarization partitions the audio into speaker turns without knowing who anyone is: speaker one from 0:04 to 0:19, speaker two from 0:19 to 0:31. Accuracy is good on distinct voices with clean turns and degrades sharply with overlap, similar voices, and poor audio.

Speaker identification maps those anonymous labels to actual people. Usually a short manual step, sometimes automated where enrolment samples exist.

Source separation goes further, splitting a mixed signal into per-speaker streams. This is what makes overlapping speech tractable, and it is the step that most improves results on panel content.

The single most valuable input to all three is separate microphone channels. Where a panel was recorded with individual lapel or boom microphones onto separate tracks, use them. Diarization becomes nearly trivial, separation is unnecessary, and per-speaker audio quality is far higher than the room mix.

This is worth pushing upstream. Asking an events team to deliver multitrack audio alongside the stereo mix costs them very little at capture time and transforms what is possible in localization. Where the recording already exists, check whether multitrack was captured and archived even if only the mix was delivered — frequently it was.

Handling Overlap

Overlapping speech is where panel dubbing either works or falls apart, and there are three viable strategies.

Separate and dub both. With per-speaker streams, each speaker's overlapping speech is dubbed independently and the results are recombined in the same temporal relationship. This preserves the interaction and is the highest-fidelity approach. It requires good separation and produces overlapping dubbed audio that must be mixed carefully so that neither voice is unintelligible.

Prioritise one speaker. Choose the speaker carrying the substantive content — usually not the person interjecting — dub them fully, and reduce or drop the other. This produces cleaner, more intelligible output at the cost of some interactional texture. For informational content where comprehension matters more than atmosphere, it is often the better choice.

Sequence the turns. Where the overlap is brief, dubbing the two turns consecutively rather than simultaneously produces intelligible audio at the cost of a small timing divergence from the picture. Works for short interjections, breaks down for sustained cross-talk.

The choice should be made per content type and recorded as a project decision rather than made ad hoc per overlap. Informational panels generally favour prioritisation; conversational content favours separation and preservation.

What does not work is ignoring the problem. Feeding overlapping speech to a pipeline as if it were sequential produces transcripts that interleave two speakers' words into one nonsensical stream, and everything downstream inherits the error.

Microphones set up for an interview

Casting the Panel

Multi-speaker content needs voice casting decisions that single-presenter content does not.

Distinctness is the primary criterion. Listeners identify speakers by voice, and two panellists with similar synthetic voices become impossible to tell apart — a much worse experience than in the original, where visual cues and familiar voices help. Choose voices that differ in pitch, weight, and pace, not merely in name.

Match the demographic register, not the exact voice. A dubbed voice does not need to resemble the original speaker's voice. It needs to be plausible for the person on screen and consistent with the register they are using.

Preserve gender presentation unless there is a specific reason not to. Mismatches are distracting and read as errors.

Give the moderator a distinct voice with a different energy from the panellists. Moderator turns are usually short and functional, and a voice that reads as facilitative helps listeners follow the structure.

Keep the mapping stable across a series. The same executive appearing in six webinars should have the same voice in all of them. This means voice assignment is a per-person asset, not a per-video decision.

Where cloned voices are used, the consent and disclosure requirements apply per person, which is more administration on a panel than on a solo presentation. A panel where three of five speakers consented to cloning and two did not is a perfectly workable mixed configuration, and it needs to be tracked.

Timing and Turn Structure

Conversation has a rhythm that scripted content does not, and preserving it is most of what makes a dubbed panel feel natural.

Turn boundaries carry meaning. A fast interruption reads as urgency or disagreement; a pause before answering reads as consideration. Dubbing that normalises every gap to a uniform interval flattens the interaction.

Do not fill natural pauses. Where the target language is more concise, the temptation is to let the dubbed turn expand into the silence that followed. Preserving the silence preserves the conversational texture.

Where the target language is longer, turns will collide. Options are compressing delivery slightly, allowing a turn to run into the next speaker's start, or trimming the translation. Trimming is usually best for informational content; slight overlap is more natural for conversational content.

Laughter, agreement noises, and backchannels — the "mm-hm" and "right" that listeners produce while someone else talks — should generally be preserved from the original audio rather than synthesised. They carry no lexical content, they are recognisable across languages, and synthesising them rarely sounds convincing.

Names in address. Panellists address each other by name constantly. Ensure names are pronounced consistently and correctly across every speaker's turns, which requires a pronunciation entry per name rather than leaving it to the system.

Moderator interjections are frequently clipped in the original and need care so they do not become unintelligible when dubbed.

What to Fix at the Source

More of this problem is solvable at recording than at localization, and it is worth telling the people who record.

  • Record each speaker to a separate track. This is the single highest-value change.
  • Use individual microphones rather than a shared room mic.
  • Position microphones to minimise bleed between speakers.
  • Ask the moderator to manage overlap — a brief "let him finish" costs nothing live and saves substantial work later.
  • Capture a few seconds of each speaker alone at the start, which gives enrolment samples for identification and reference audio for voice work.
  • Record a room tone sample for use in reconstructing gaps.
  • Keep the multitrack archive, not just the mix.
  • Have the moderator state each speaker's name at their first turn, which helps both the audience and the identification step.

Where a content programme regularly localizes panel content, a short capture specification handed to the production team pays back repeatedly.

Team reviewing a project plan on a shared screen

A Working Checklist

  • Ask for multitrack audio before starting; check the archive even if only a mix was delivered.
  • Run diarization and speaker identification before transcription, not after.
  • Apply source separation to overlapping regions where per-speaker tracks are unavailable.
  • Choose an overlap strategy per content type and record it as a project decision.
  • Never feed overlapping speech to the pipeline as if it were sequential.
  • Cast voices that are clearly distinct in pitch, weight, and pace.
  • Match demographic register and gender presentation rather than the original timbre.
  • Give the moderator a distinct, facilitative voice.
  • Keep speaker-to-voice mapping stable across a series as a per-person asset.
  • Track consent and disclosure per speaker where voices are cloned.
  • Preserve turn boundaries and natural pauses rather than normalising them.
  • Retain original laughter, agreement sounds, and backchannels instead of synthesising them.
  • Add a pronunciation entry for every panellist's name.
  • Give the production team a capture specification for future recordings.

Frequently Asked Questions

Can AI dubbing handle people talking over each other?

With separation, yes; without it, no. Overlapping speech in a single mixed channel produces interleaved, nonsensical transcripts that corrupt everything downstream. Source separation splits the overlap into per-speaker streams that can each be dubbed, and separate microphone tracks from the original recording make the problem disappear entirely. Establish which of these you have before quoting the work.

Should overlapping turns stay overlapping in the dub?

It depends on the content. Preserving the overlap keeps the conversational texture and suits discussion-led content where the interaction is the point. Prioritising the speaker carrying substantive content produces clearer, more intelligible output and suits informational panels. Decide per content type and apply it consistently rather than making the call overlap by overlap.

How many distinct voices do I need for a panel?

One per speaker, including the moderator, and they must be clearly distinguishable. Listeners rely on voice to track who is speaking, and two similar synthetic voices on a five-person panel make the content genuinely hard to follow. Distinctness in pitch, weight, and pace matters more than any resemblance to the original speakers.

What if only some panellists consented to voice cloning?

That is a normal and workable configuration. Use cloned voices for those who consented and cast generic synthetic voices for those who did not, keeping all of them distinct from one another. Track consent per person, not per video, and make sure the pipeline cannot use a voice asset without a linked consent record.

Should laughter and agreement sounds be dubbed?

Generally not. Backchannels, laughter, and agreement noises carry no lexical content, are broadly recognisable across languages, and rarely sound convincing when synthesised. Preserving them from the original audio keeps the conversational texture intact and avoids an uncanny result.

How do audience questions get handled?

Usually badly, because they are the worst audio in the recording — a distant voice picked up by a stage microphone, often with the questioner facing away from it. Where a roving microphone was used, the audio is workable. Where it was not, the practical options are to have the moderator repeat each question, which good moderators do anyway, or to caption the question from whatever is intelligible and dub only the answer. Decide which before transcription rather than discovering the problem at review.

Should the moderator's turns be translated in full?

Yes, but they need different handling. Moderator turns are short, functional, and often clipped in the original, and they carry the structure of the discussion — who is being asked what, and when the topic changes. Compressing or dropping them to save timing space removes the listener's map of the conversation. Where space is tight because the target language is longer, trim panellist answers rather than moderator turns.

What is the highest-value thing to change about how panels are recorded?

Recording each speaker to a separate track. It costs the production team almost nothing at capture time, makes speaker identification trivial, removes the need for source separation, and substantially improves per-speaker audio quality. A short capture specification handed to whoever records your events repays itself on the first panel.


Related reading: Speaker Diarization Explained | Conference Video Translation | Interview Translation Guide