Simultaneous interpretation: planning languages, audio and listening for an event

Who interprets and who prepares the system

Define the event format and the languages participants will speak and hear. Interpreting deals with spoken language; simultaneous interpretation takes place while the speaker continues, using specific equipment. The European Commission explains interpreting types and terminology, which can help you use consistent terms when agreeing on the scope with providers.

Give the interpreting team the language combinations, topics, agenda and working hours so they can plan handovers. Supply presentations, a glossary and proper names by the agreed deadline. The provider determines staffing according to the working day, format and concurrent sessions. The receiver count tells you how many listeners will use the system; it does not settle interpreter staffing.

Identify in the proposal who books the interpreters, who supplies booths and the system, who integrates the platform and who operates on site. If GLMedia is involved, agree on which equipment it provides and who operates it. Also confirm the interpreters, availability and service conditions for that event.

Map what each workstation receives and sends

Floor is the original program audio, and its language may change within a session. Relay means interpreting from another interpreter's channel when the team agrees on that arrangement. A handover is a change in the person interpreting. You may also encounter retour, meaning interpreting into another active language. If these terms appear in the proposal, review the paths with the team; definitions are available in the European Commission's interpreting terminology.

On a Shure MXCIC, interpreters can select floor or relay channels for listening and set output channels according to the system configuration. This example shows what to record: where each workstation receives audio, what the interpreter hears and which language channel it transmits to. Check the functions of the console you choose. The MXCIC manual describes this model's functions.

Try drawing a Spanish/English discussion: when someone speaks Spanish, note what the interpreter working into English receives; when the speaker changes, trace the reverse path. This is a planning example for your matrix. If you add Portuguese, agree with the interpreters whether they will work directly or through relay and include that decision in the diagram. Also mark the channel each audience group will select.

Use consistent channel numbers and language names on consoles, receivers, the platform and files. Rehearse the handover with the interpreters: who enables each microphone, what their colleague hears and how the language output continues through the change.

Provide a workspace where interpreters can hear, see and work

Review booth sound isolation, ventilation, lighting, furniture and sightlines with the provider. The European Commission publishes references on interpreting facilities for its work. Use them to discuss how the provider will verify the requirements for the booth you plan to book.

Mark the location, access, space, power, console, microphones and compatible headphones. If the interpreter cannot clearly see the speaker or screen, agree on a video feed and test it with the people who will interpret. A curtain can hide a table, but sound isolation, listening conditions and comfort still need to be checked for the working day.

For a remote workstation, ask the interpreter to test their space, equipment, connection, microphone and headphones. Rehearse under the conditions they will use, including handovers, and provide a technical contact. Agree on how they will report lost audio and who will help restore the path.

Include audience questions, videos and remote voices

List every source interpreters need to understand: speaker, moderator, audience questions, playback and remote guests. Prepare a labeled feed and check its connection and input level. The event sound guide can help you review the patch and identify missing sources.

Provide monitoring of floor and any relay channels the team will use. Trace the paths to avoid accidentally routing an output back into its own input. The operator needs to check each point with known signals and people speaking. Read the channel label and listen to it: together, these checks establish whether the expected language is arriving.

During rehearsal, change microphones, play a video with sound and simulate an audience question. Agree on how interpreters will ask for unclear material to be repeated and who resolves the issue. If you plan to use sound from a room loudspeaker as the interpreting feed, test that arrangement with the interpreting team before relying on it.

Receivers or phones: check the entire listening path

The audience may listen through dedicated receivers or devices connected to a platform, depending on the chosen solution. Check the technology, channels, headphones, power and compatibility of every component. If you mix manufacturers, confirm in the documentation and through a test that the receivers can receive the planned transmitter.

Bosch INTEGRUS distributes audio by infrared through a transmitter, radiators and receivers on which attendees select a language. Placement and coverage are designed for that system and venue. This is one specific architecture: RF, Wi-Fi or an app needs its own design and testing. The INTEGRUS V03 manual covers installation and operation of that system.

Count the listeners who will use receivers simultaneously and add the agreed operational spares. If only part of the audience needs interpretation, this count may be lower than total attendance. Plan charging or batteries, cleaning, distribution and returns. Explain how to select a language and adjust volume, and check the units at closeout. If attendees will use their own phones, review access, network, devices and user support with the provider.

For remote and hybrid events, test the actual accounts and roles

Record the platform, account, host, roles and devices. In Zoom, enable interpretation for the scheduled session and check its conditions: it works in the main session and is managed from the desktop app. Listeners can choose a language, and interpreters have relay options. Check the account and versions you will use; the Zoom interpretation guide describes these functions and restrictions.

For a hybrid event, draw how each language reaches the room and remote audience, and how questions from both enter the system. Prepare the integration of the in-room system with the platform and agree on who operates it. Check return feeds so each participant can hear the others without receiving their own signal back.

The event internet guide can help you check connectivity and backup. Rehearse with interpreters, the host and listeners on their planned devices. Provide a technical coordination channel and agree on how to announce a recovery without unnecessarily interrupting the conversation.

Agree on the files required for each language before recording

Ask what is needed afterward: original program, language-specific audio, complete sessions or edited versions. Agree on who manages permission and consent for recording, using the interpretation and publishing. Resolve these decisions so distribution rights are not treated as if they came with the equipment.

In Zoom, local recording captures what the person recording hears, while cloud recording has its own options. The interpreter recording setting can generate an audio file for each interpretation when enabled. Check it in the event account and open a sample before agreeing on delivery. The Zoom cloud recording guide explains these settings.

With a separate recorder, prepare outputs and tracks by language, filenames and alignment with video. Make a sample and listen before the program starts. The recording and streaming guides cover delivery and transmission. Recording only a general mix does not retain independent tracks in that file.

A short rehearsal that covers every language

Schedule time with interpreters and technicians to listen to every path. Ask for a recognizable phrase in each language, an audience question, a video and the planned handover. This short sequence checks what reaches the workstation, what the listener receives and what gets recorded.

1. Confirm languages and responsibilities

   Confirm inputs, outputs, concurrent sessions, format and listeners. Agree on the interpreting provider and send the agenda and materials by the agreed deadline.

2. Test the workstation with its user

   Review booths or remote workspaces, power, sightlines, audio, console, headphones and network with the interpreters.

3. Label the routing matrix

   Identify floor, languages and any relay. Use the same names for inputs, monitoring, outputs and recording.

4. Listen to every source

   From the interpreter's workstation, test speakers, panelists, audience questions, videos and remote guests.

5. Check the audience destinations

   Select languages on receivers and the platform from different positions. Check compatibility, coverage and whether the operating instructions are clear.

6. Practice handovers and recovery

   Test interpreter changes and the agreed backup path. Define who acts and how they notify the team.

7. Open the files and close out the event

   Check samples for each language. Maintain technical support during the program and verify the return of equipment and delivery of the agreed files.

Two Zoom questions to include in rehearsal

Review the current settings for your event and test what each role receives separately.

What Zoom records when you use several languages

Check the interpreter recording option in the event account and confirm the files it generates during rehearsal.

For a bilingual event, ask whether the client needs separate audio files, playback with language selection or edited videos. These are different deliverables, each requiring its own check. Choosing a listening language in one account does not, by itself, define every recording file.

Agree on authorization to record and distribute, who will have access and how long the material will be retained. After rehearsal, review the files the account actually generated before committing to a delivery format.

The requirements and Record language interpreter option appear in Zoom's official cloud recording settings. Review them with the account administrator, since some options may be locked.

1. Enable the option with the administrator

   Confirm that cloud recording is available for the account and Record language interpreter is enabled. Check permissions and locks before bringing the team together.

2. Record recognizable phrases

   Run a rehearsal with a phrase on floor and another in each language. Include a handover, pause and audience contribution. Record from the planned account and wait for processing to finish.

3. Review the deliverables

   Open the files, identify languages and check sync, continuity and content. If you need video for each language, include editing and quality checks in the scope and schedule.

If languages overlap, test the listener and interpreter separately

Prepare separate checks for the mix an attendee hears and the input an interpreter needs.

Draw who receives floor, who listens to relay and which language each workstation transmits. Two interpreters being heard together and original audio being heard underneath interpretation may need different checks. Test one voice at a time before introducing a handover.

If the interpreter still receives a mix that prevents them from working, save the times and configuration for support. Agree on an alternative you have rehearsed and review the paths before blaming the headphones.

The Zoom interpretation guide distinguishes the interpreter's channel switching and relay from an attendee's language selection. Use these functions to prepare separate tests for each role.

1. Set up the test with separate roles

   Connect a host, speaker, two interpreters and an attendee. Record who receives floor, who listens to relay and which language each transmits. Send one voice at a time, then test the handover.

2. Check listening and output in each account

   For the interpreter, check Listening in and the output language. For the attendee, select the channel and test Mute Original Audio where appropriate. Use separate accounts to observe both behaviors.

3. Check how you will play videos

   Zoom recommends avoiding shared computer audio while interpretation is active because it is heard at 100%. If the program includes videos, coordinate another playback and mixing path and rehearse it on the planned clients and devices.

They joined the meeting but do not appear as an interpreter

Joining through an invitation does not confirm that someone has the interpreter role. Before rehearsal, check the hosting account: interpretation enabled, host permissions and a scheduled meeting with an automatically generated ID. If the setting is grayed out, ask the administrator to check the lock; resending the link does not change that permission.

With the interpreter connected through the desktop app, compare their account email with the one you preassigned. On the host's device, open Interpretation, which may be under More, and check the assignment. Start interpretation and confirm that the interpreter receives the invitation to accept the role.

Test with an attendee on another connection: one recognizable phrase from the speaker and another from the interpreter. Confirm from that attendee's position that the expected language is audible; looking only at the host panel leaves part of the path untested.

If the person still does not appear, record the client, version, operating system and role at each workstation for support. Resolve access before the show and rehearse the alternative with the language team. The manual allows assignment during a session; check that the role can be selected in your actual session.

See assigning and starting interpretation and enabling the feature.

Check interpretation arrangements before sending the audience to breakout sessions

If a Zoom plenary uses interpretation, review the path before moving the audience into workshops. Language Interpretation is available in the main session and does not work inside breakout rooms. Naming a room after a language can help people find it; it does not create an interpretation channel there.

With the language team, list what will be spoken in each workshop and what its audience needs to hear. If several sessions need simultaneous human interpretation, evaluate separate meetings and confirm accounts, hosts and operation before finalizing the agenda. That alternative needs its own setup and rehearsal.

The current Zoom interpretation guide limits the feature to the main session. Check this restriction before assigning listeners and interpreters to breakout rooms.

1. Test an attendee's route

   Rehearse entering the workshop and returning to the plenary on the planned device. Listen to a recognizable phrase in each location and check who helps if someone enters the wrong room.

2. Separate announcements from the discussion

   If you use Broadcast voice, check how the host's microphone reaches the rooms. Agree on announcements for activity changes and prepare the listening arrangement each workshop needs.

If invitations have already gone out, check the meeting ID before adding interpretation

If interpretation was added after invitations went out, open the scheduled meeting and check its ID. Zoom Language Interpretation requires an automatically generated ID and does not work with a Personal Meeting ID, or PMI. Enabling the account setting does not make that personal link compatible.

For a new meeting, the Zoom guide specifies Meeting ID > Generate Automatically and Enable language interpretation. Set up the planned languages there and save the meeting before copying its invitation. Also review permissions for the hosting account.

Compare the new link with what people already received: calendar entries, registration confirmations, buttons and QR codes. Agree with production on what must be updated and who makes each change. An announcement that the link has changed will not help if attendees still open the old button.

Rehearse from the invitation you will actually distribute, with a host, interpreter and listener. Test a phrase in each language and confirm it from the listener's device. Keep the verified link with the program so the whole team uses the same meeting.

If the workstation receives floor audio over RF, test the interpreter's bodypack too

If the agreed design uses a wireless link to carry floor or a return feed to the interpreter's workstation, include it in the event's RF inventory. Identify its signal and who coordinates the frequency alongside microphones and monitors. This describes that return feed; the audience language channels need their own system.

As an example of a status to check, an SR IEM G4 in RF Mute can still display its frequency while not transmitting RF. Reading that number at the rack leaves the signal reaching the workstation receiver untested.

Rehearse with the person who will interpret. Test a stage voice, an audience question and video audio, one source at a time. Also listen from the colleague's workstation for the handover. Record what each feed carries so you can recognize a wrong channel even if it is loud and clear.

If a bodypack is changed during the day, check its frequency and assigned feed before handing it over. Label the receiver by function and agree on who handles the incident. Power being on or frequencies matching does not confirm that all required content reaches the booth.

Test the floor microphone along the speaker's actual route

What matters at the booth is the speaker feed throughout their route. Ask the speaker to use the microphone at the lectern, beside the screen and wherever they will answer questions. Listen from the interpreting workstation: monitoring beside the receiver leaves part of the job unchecked.

If the speaker's original audio, or floor, arrives through an SLXD4, retain both A and B antenna paths. To share antennas between two receivers, the UA221 diagram uses two splitters and specifies compatible half-wave or directional antennas in the operating band. Decide on the rack location before closing the booth so there is time to test.

During the walk-through, record what the booth heard and where the person was speaking. If sound drops out, compare the receiver output with the signal reaching the interpreting workstation. This narrows the section to investigate without attributing every dropout to RF.

Agree on who removes a faulty microphone and how the replacement reaches the speaker. Rehearse that handoff too, so the booth can recognize the new source and the conversation can continue smoothly.

Identify the technical monitor's listening mode

If a G4 IEM is used for an operator or support person's monitor feed, label the signal at each input. Do not assume two connections provide two selectable languages: first agree on what that person needs to hear.

With the SR IEM G4 in Stereo, the EK offers Stereo or Focus. Focus mixes both signals to mono; Balance adjusts their relative levels. SR Mono uses only BAL AF IN L. These are technical monitoring modes, not audience language selection.

Test each source separately and then together, naming them while listening. Ask the operator to confirm what they need rather than approving the feed because two meters move. Record the selected mode with the patch so the next person can check the same feed without guessing what was mixed.

Check the original voice feed before sending it to the booths

For a day with several speakers, agree on a voice check before going live. Listen to floor at the point feeding interpretation and save that reference for the next shift. The booth operator needs a way to report noise or distortion immediately.

On the Sennheiser EM 300-500 G4 receiver, AF Out controls the audio output level. Sensitivity on the SK 300 G4-RC controls a different point: its input. Distinguish these controls when checking a wireless microphone that supplies floor.

Record those settings with the path to the booths. If the voice sounds harsh, compare it at the receiver and at the interpretation input at a similar listening level. Tracing the path narrows the search before several controls are changed at once.

Prepare a replacement for the floor monitor receiver

If an interpreter or technical support person receives floor through an EK IEM G4, agree on when they can change the bodypack without missing an intervention. Distribution of audience language receivers is a separate procedure.

The EK IEM G4 accepts 1.5 V AA batteries or a BA2015 pack. The pack can be charged in an L2015 separately or inside the receiver. Turn the volume down before putting on headphones.

Hand over the replacement only after checking it with a room voice and a program video. Listen from the handover workstation; a powered-on unit does not yet confirm that it receives the required floor feed.

Language planning worksheet for each session

For each session, record the time, room, languages to be spoken and languages the audience needs to hear. Include expected listeners per language and whether they will attend in person or remotely.

Identify who books the interpreters and who requests the system. Include a contact for the agenda, presentations and event vocabulary, with the agreed deadline for collecting them.

Mark separately the sessions to be streamed or recorded and the languages required in those deliverables. If a speaker or language changes, update the worksheet and notify both providers.

Download the language brief (TXT) — a blank planning worksheet; completing it does not send an inquiry.

INTEGRUS LBB4540/32: understand the reception reading

When checking reception, distinguish the selected language channel from the FOM reading. In the V03 manual, page 55, test mode reports quality by carrier: 00–39 means good reception, 40–49 weak reception, and 50–90 poor or no reception.

With the technician, walk the listening positions with the receiver in test mode; record location, orientation and carrier. Use transmitter tones during pre-event testing. Switching the receiver off exits test mode.

Multilingual SRT: prepare tracks and check the language menu

Separating encoder tracks is only part of the path: check that the destination identifies them and lets listeners select the expected language.

In vMix 29, Split Stereo Pairs into Separate Tracks encodes each stereo pair as a separate track. AAC supports up to eight audio channels, not eight stereo languages. With separate tracks, Audio Bitrate applies to each pair.

Prepare a sample with floor and one interpreted language. At the destination, select each track and listen to a phrase that identifies its content. Record label, pair, PID and bus in the worksheet. Check the player's actual menu before offering language selection to the audience.

Agree on the paths with technical production and review vMix reception.

HLS menus: check that the selected language matches the audio

If you build HLS with Nimble, its 2016 ABR guide distinguishes Audio only, Name for the displayed name and Language for the code. It also describes Default and Autoselect. Confirm those settings in your version; the player must support selection between audio tracks.

Review the manifest and open the planned player. Select each option, listen to a recognizable phrase and record startup and changes in the worksheet. A correct label does not verify the content.

If audio is missing, check the output. Plan monitoring with technical production.

Different audio tracks need clear identifiers

Compare each track's name, language and purpose before changing the manifest or player preferences.

The RFC 8216 specification requires distinct NAME values within the same group, defined by GROUP-ID and TYPE. In hls.js, setAudioOption searches for a match, updates audioPreference and returns null if it cannot find a track.

Identify the language and purpose: floor, interpretation or audio description, where present. Compare labels and phrases in the worksheet. Switch, switch back and listen after reconnecting; record whether the selection is retained.

Coordinate with technical production and check startup behavior.

Safari changes the label but you still hear the same language

Apple recommends mediastreamvalidator and hlsreport for stream validation but notes that they do not check everything. hlsreport summarizes the validator's JSON; retain that report with the playback test.

Use different phrases for each language: select A, switch to B and return to A. Record the label, phrase and any silence in the worksheet. Repeat on another device with the same URL; record the iOS build and whether playback uses a native or JavaScript path.

Review track identity with technical production.

Two languages share a GROUP-ID: is the manifest wrong?

The RFC 8216 specification defines a group by shared GROUP-ID and TYPE. Its alternatives must have distinct NAME values. Sharing a group is part of that structure; it does not by itself indicate an error.

Save the manifest and compare its fields with the browser's list in the worksheet before changing groups. Also review lookup by ID with technical production.