c3lingo

Live interpretation of talks at Chaos events

User Tools

Site Tools


for-event-organizers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
for-event-organizers [2020/02/05 17:16] tealfor-event-organizers [2023/12/30 18:05] (current) – [At a location-based event] oskar
Line 23: Line 23:
  
 ===== What you should provide ===== ===== What you should provide =====
 +
 +==== At a location-based event ====
  
 Ideally, you can provide us with the following setup: Ideally, you can provide us with the following setup:
  
-  * A soundproofed booth for each stage+  * A soundproofed booth per language for each stage
     * Positioned so the stage can be seen from the booth     * Positioned so the stage can be seen from the booth
-    * Ideally elevated so that the audience does not block the view +      * Ideally the booth is elevated above viewers 
-    * With a desk, desk lamp, and office chairs +      * Alternatively a screen in the booth with the current slides can suffice 
-  Two consoles for each booth/stage, with the following features: +    * With a desk, desk lamp, and 3 padded chairs 
-    Headphone connector (ideally 3.5mm audio jack) to listen to stage/speaker audio, where the volume can be controlled from the console/by the interpreter +    At least 2 free power sockets near the desk 
-    Microphone (ideally) or microphone connector (please let us know whether XLR or audio jack and which voltages) to get the interpreted signal to the mixer/FOH; each microphone should be switchable (on/off); a cough button to temporarily interrupt the signal is optional but appreciated+    * Water and ideally cough drops (sage) or similar for the interpreters 
 +    * Points of contact or numbers for tech issues and stage managers 
 +    * [C3] Ideally a phone to communicate with stage managers 
 +    * 2 interpretation consoles for each booth, with the following features: 
 +      Headphones (or worst-case a 3.5mm Headphone connector) to listen to stage/speaker audio 
 +        * Floor volume can be controlled from the console/by the interpreter 
 +        Ideally the microphone audio can also be directly fed back into the headphones, with controllable volume 
 +        * Ideally an additional headphone output for a 3rd interpreter 
 +      * Microphone to get the interpreted signal to the mixer/FOH 
 +        * Each microphone should be switchable (on/off) 
 +        * A cough button to temporarily interrupt the signal is optional but appreciated 
 +        * Ideally, both microphones can be active simultaneously
   * A way to manage, mix, and route audio, usually a mixer/FOH - **provided and managed by you or people you hire**   * A way to manage, mix, and route audio, usually a mixer/FOH - **provided and managed by you or people you hire**
   * A way to distribute the interpreted signal - **provided and managed by you or people you hire**   * A way to distribute the interpreted signal - **provided and managed by you or people you hire**
 +    * If there is a public stream, it should have a ducked version of the floor audio mixed in
 +    * Distribution to the live audience is possible via our website, if the audio can be fed into our mumble server. Contact our techs for this.
 +==== At a virtual event ====
 +
 +If your event is (partially) virtual, and translators will be working remotely, you will need to provide these things:
 +
 +  * A low-latency audio and video stream of the presentations.
 +    * This can be the same signal that eventually is streamed to viewers, but it must be taken from the video direction system as early in the processing pipeline as possible.
 +    * It should be in a format that can be viewed with common software, for example an RTMP or HTTP stream with codecs supported by VLC, or a WebRTC-based solution viewable through a common web browser like Chromium or Firefox.
 +    * The video quality should be good enough to be able to make out reasonably sized slides and demos.
 +    * The signal could be the program output, or it could be a multi-view of the program and preview signals, plus additional ones.
 +    * The sound must include all speakers, and may contain talkback from the director or similar. If the talkback audio is part of the translators stream, the interference must be limited to the most urgent communications only.
 +  * A Mumble bot that can take the translation audio from the c3lingo Mumble server, and insert it into the program stream. The translators will be speaking into a mumble channel specific to the event (if you have multiple rooms, one per room). It is your responsibility to obtain the audio from there.
 +    * We will coordinate to set up the channels, and allow your bots access to the appropriate rooms.
 +  * A dedicated person as point-of-contact who:
 +    * can monitor and fix issues with both the special stream and the Mumble integration,
 +    * be the communication bridge between the translators team as well as the event organizers and the video director.
 +
 +Typically, we can do two languages at once; usually DE/EN, and a second language like FR, ES, etc. This means that you should plan to take two mono audio sources for the two translations.
  
 ===== Helpful links ===== ===== Helpful links =====
for-event-organizers.1580922967.txt.gz · Last modified: 2020/02/05 17:16 by teal