Contingencies during RSI events and how to resolve them

[Cyril Flerov]

There are several standard “issues” that come up often during remote simultaneous interpretation events. Below are the most common ones and how they can be resolved quickly in InterStar ICP.

We provide separate solutions if you are troubleshooting as an interpreter or a technician.

Problem:2 interpreters in the same booth speaking at the same time interpreting into the main language of the booth. This is usually heard only by the delegate who’s listening to your interpretation or by the technician.

Resolution:
-by the client-the client can report the issue to the technician or to the interpretation team in chat from the client console
-by the technician-the technician can send a message “to booth” that is called “2 interpreters same time”. The message advises interpreters that there speaking at the same time.

Problem:Interpreter continue speaking into the relay channel. After an interpreter is done with the relay interpretation, the interpreter does not switch output back into the primary language of the booth. For example, if I’m a Spanish booth and I finished interpreting from Spanish into English into the relay channel, I did not switch my output into Spanish, and I continue to interpret into Spanish into the relay [English in our example] channel. however it overlaps with the voice of the interpreter who is correctly interpreting into the relay channel.

Resolution:
-by the client-the client can report the issue to the technician or to the interpretation team in chat from the client console
-by the technician-the technician can send a message “to booth” or to the entire interpretation team code “wrong channel”. The message instruct interpreters that somebody stopping into an incorrect channel. It is better to send it to the booth of the interpreter who is talking into the wrong channel, however, sometimes is difficult to determine very quickly what booth it is. That is why that message can be sent quickly to the entire interpretation team.
-by the interpreter-if an interpreter can hear overlapping was a the relay channel the interpreter concerned “wrong channel” message to the entire interpretation team

Problem:The interpreter did not unmute the microphone.

Resolution:
-the client can report the issue to the technician or to the interpretation team in chat through a quick message
-the the technician can send a quick message to the entire interpretation team or to the booth of the interpreter who did not unmute.
-If interpreter cannot hear the boothmate or the relay interpretation they can send a quick message “warn: unmute MIC” to the boothmate or to the entire interpretation team.

Problem:The interpreter microphone is unmuted when it’s supposed to be muted.

Resolution:
-by a fellow interpreters-send a message to your boothmate to mute the microphone or the message to the entire interpretation team to check of their microphone is muted if they are not interpreting.

Problem:interpretation is not possible because of bad audio quality.

Resolution: the technician or any interpreter can send a message to the client advising that interpretation is not possible and will continue when audio quality improves.

Problem:The speaker is too far away from the microphone.

Resolution: a technician or an interpreter can send a quick message to the client in the chat to speak closer to the microphone.

Problem:There are open/hot microphones on the floor in the RSI event that create interference.

Resolution:
-by technician or interpreter: they can send a message to the client to mute hot microphones
-interpreter can send quick message to the technician to ask to mute the hot microphones.

[Author]

Posts