Knowledge Base

Getting Started

  • Set up KUDO translation for an onsite event

    Connect venue audio to KUDO so attendees can receive translated speech and captions on their devices.

    Audience: AV/IT.


    Before you begin

    • A dedicated computer for each translated room. This computer sends the room’s audio, and video if available, to KUDO. Don’t use it for anything else during the event. 
    • A wired Ethernet connection for each dedicated computer.
    • A USB audio interface or capture device that can receive the room’s audio feed from the onsite AV team.
    • A USB video capture device, if a video feed is available.
    • Room feeds from the AV team: a direct audio feed in the stage language, and the program video. Video is recommended for AI translation and required for professional interpreters.
    • Your KUDO links: the Participant Link for each dedicated computer, and the Mobile Link and QR code that attendees will use.

    Before the event, turn off notifications, sleep mode and automatic updates on each dedicated computer.


    Step 1: Join from the dedicated computer

    1. On the dedicated computer, open the Participant Link and join the meeting.
    2. Keep the computer connected to KUDO throughout the event.

    Step 2: Connect the venue feed

    1. Connect the room’s audio feed to the USB audio interface or capture device.
    2. If a video feed is available, connect it to the USB video capture device.
    3. In KUDO, select the USB audio interface as your microphone device and turn it on. Then speak into the room microphone, or play audio from the mixing console, to check that KUDO receives it.

    Step 3: Test before attendees arrive

    Before you open the doors, test the following in each room:

    • The Mobile Link and QR code
    • Translated audio
    • Captions

    Step 4: Verify Attendee Wi-Fi

    Reliable wireless connectivity is essential because attendees receive translated audio and captions directly on their devices. For large events, see Plan Wi-Fi requirements for a large event

    Minimum network requirements

    Component Requirement
    Wireless standard Wi-Fi 5 (802.11ac) or Wi-Fi 6 (802.11ax)
    Wireless network Dedicated or isolated 5 GHz
    Access points 3×3 MU-MIMO antennas or better
    Bandwidth Minimum 48 kbps per attendee
    Firewall Allow required UDP traffic
    Communication Support unicast traffic

    The venue IT team should confirm that wireless coverage and capacity are sufficient for the expected number of simultaneous listeners. Test connectivity throughout the venue, including seating areas, breakout rooms, hallways, and overflow spaces.


    Step 5: Share the QR code and Mobile Link

    1. Display the meeting’s QR code and Mobile Link on presentation screens, signage or printed materials, wherever attendees can see them.
    2. Encourage attendees to use headphones and to keep their devices charged throughout the event.

    Running several rooms or a multi-day event? Create a static QR code for each room.


    Onsite computer requirements

    Component Requirement
    Operating system Windows 10 or later, or macOS 13 Ventura or later
    Processor Intel Core i7, AMD Ryzen 7 or Apple M1, or better
    Memory 8 GB RAM minimum
    Browser The current version of Chrome (preferred), Firefox or Edge. Safari isn’t supported.
    Internet connection 20 Mbps download and 10 Mbps upload, minimum
    Network ports TCP 443 and UDP 3478

    Firewall and network requirements

    Each dedicated computer and the attendee network must meet KUDO’s firewall and network requirements. These include allowing TCP 443 and UDP, plus specific rules for attendee networks. See Firewall and network requirements


    Need assistance planning your setup?

    Contact KUDO Support before your event if you'd like help validating your workflow, reviewing audio routing, or confirming network readiness for your deployment.


    Related content

  • Advanced Settings for KUDO Meetings

    When scheduling a session, you have the option to configure advanced settings. All these settings have been pre-configured with the optimal defaults suitable for the vast majority of meetings. Therefore, in most cases, you do not need to modify them. However, to enhance the experience for specific needs, you may need to customize them. Below is a list of settings you can configure when creating a new session.


    Mobile Link and Integrations

    This option enables the automatic creation of a link for accessing KUDO AI on any mobile device through a dedicated URL or a QR code. The QR code will open a page in the browser. Additionally, this option provides an embed code to integrate KUDO AI into third-party platforms. This option is enabled by default.

    This option includes the following two settings:

    • Enable Autofloor: When activated, this setting allows participants to hear the original (speaker's) audio within the translation channel if the speaker is speaking the same language as that particular channel. Autofloor can be disabled to implement the autofloor API, or to stop the floor audio from passing thru.
    • Enable Horizontal Screen Projection: When activated, this setting adjusts the appearance of the Mobile Link, allowing it to be fully resizable. This feature is especially useful for projecting captions on large screens during in-person events, where space is limited due to other visuals being projected on the screen.

    Uploading Your Logo

    This option allows you to upload your company logo to a meeting, replacing the default KUDO logo on the Mobile Link. It's ideal for organizations that want to deliver a branded experience when using translation services.

    The logo can be uploaded in Advanced Settings during meeting creation. For best results, use an image that is 96x96 pixels or smaller, in landscape orientation.


    Speaking Modes

    This option applies to sessions held via KUDO Meeting. The default setting is Open Mic, but you can customize this based on your needs. The available modes are:

    • Open Mic: Participants can independently turn their microphones on and off. You can also limit the maximum number of microphones that can be active simultaneously by adjusting the "Number of Active Mics" setting.
    • Request to Speak: In this mode, participants must request permission to speak by clicking a dedicated icon within the KUDO Web Conferencing application. The session host will then enable their microphone. We recommend using Request to Speak modes for meetings expecting 20 or more participants.

    Recordings

    This option allows you to record the audio and video of your meeting. Recordings will be available for 30 days. By default, this option is set to OFF, ensuring that no recording of your meeting will occur without your explicit consent.


    Audio Manager

    Allow the Audio Manager role in order to ingest and route audio for hybrid or in-person meeting.


    Preparation time

    Allow the meeting to start before the scheduled time. This is useful for technical setup, such as checking if connections are established and ensuring that audio is properly captured by the device.


    Grant consent for the KUDO team to access your meeting

    Allow members of the KUDO team to join your meeting when necessary, for example, for debugging purposes.


    Need Help?

  • Understanding Post-Meeting Reports

    How KUDO Counts Viewers

    KUDO identifies and reports unique attendees (called Viewers) based on how participants access and interact with interpretation channels during a meeting. These statistics appear in the Viewer Language Statistics section of the Post-Meeting Report.

    Screenshot 2026-05-29 142318.png


    What Makes a Unique Viewer

    A viewer is counted when someone clicks Join on a Floor or language channel through the KUDO Meeting, Mobile Link, or KUDO Widget. KUDO identifies each viewer by the combination of their device, browser, and session environment.


    When Someone Is Counted Once

    If a viewer refreshes the page, clicks Leave and rejoins, or reconnects using the same browser and device, they are counted only once. This prevents duplicate counts during normal reconnects or page refreshes.


    When Someone Is Counted Again

    A viewer is counted as a new unique attendee if they join from a different device, switch to a different browser on the same device, or access the meeting from a separate environment. For example, opening the KUDO Viewer Link in another browser while already connected on their phone.


    How Language Counts Work

    Viewer statistics are tracked per language channel accessed during the session. If a participant joins the Floor channel, switches to Spanish, then English, then back to Spanish, the report will show one count for each language: Floor, Spanish, and English. Switching back to a channel already visited in the same session does not add another count.


    Need Help?

  • Scheduling a Meeting in Request to Speak Mode

    This guide walks Hosts through the process of scheduling a KUDO AI Meeting in Request to Speak mode. In this mode, participants request microphone access, while the Host/Operator controls speaking permissions and manages the speaker queue.

    Audience: Hosts, Operators, Presenters, Meeting Organizers, and Technical Support Staff.


    Before You Start

    KUDO AI Meetings are designed for real-time multilingual communication. Before scheduling your meeting:

    • Use a reliable headset or headphones whenever possible.
    • Verify your microphone and internet connection.
    • Assign a Host or Operator to manage speaking requests during the meeting.
    • Determine the Speaker Languages and Translation Languages required for the session.

    Schedule a Meeting

    1. Create a New AI Meeting

    1. Sign in to KUDO.
    2. Click New Meeting.
    3. Select AI Translation.

    2. Select a Meeting Type

    Choose the experience that best fits your use case:

    • AI Speech & Captions is the full experience. Best for broadcasts like keynotes and town halls.
    • AI Captions Only reduces latency. Best for multilingual discussions where response time matters.

    4. Configure Languages

    • Speaker languages are the languages participants will speak during the meeting. 
    • Translation languages are the languages participants can select to hear or read during the meeting.

    5. Assign a Meeting Host

    The Meeting Host is responsible for:

    • Managing speaking requests
    • Approving participants to speak
    • Controlling recordings
    • Accessing meeting moderation tools

    Screenshot 2026-06-10 221429.png

    6. Enable Request to Speak

    1. Click Advanced Settings.
    2. Scroll to Speaking Mode.
    3. Select Request to Speak.
    4. Configure the Maximum Number of Active (on-screen) Microphones allowed simultaneously, including the Host.

    7. Create the Meeting

    Click Save to finish creating the meeting.


Recording

  • Download KUDO Recordings and Transcripts

    Audience: Organizers with access to the scheduling Client account.

    Retrieve available meeting assets after a recorded session finishes.

    Before you start

    Confirm recording was enabled during the meeting and sign in to the KUDO Client account that scheduled it. Allow time for processing after the session.


    Steps

    1. Open Previous Meetings and select the session.
    2. Open Content.
    3. Choose Recordings to view and download available recordings.
    4. Choose Transcripts to retrieve available multilingual transcription files.

    What to expect

    Recordings and transcripts are available only for meetings that were recorded. Download important assets promptly after processing.


    Availability checks

    CheckEstablished guidanceConfirm for your session
    PermissionAccess through the scheduling Client accountAny additional delegated download permissions
    LanguagesMultilingual transcripts are describedThe actual files and languages offered
    FormatThe source does not specify extensionsThe download format before planning downstream processing

    Missing assets?

    Check recording status, the account used, and processing completion. If expected files remain absent, contact KUDO Support.


     

IT, Security & Privacy

  • Plan Wi-Fi requirements for a large event

    At an onsite event, attendees follow KUDO translation on their own phones over the venue's Wi-Fi. Use this guide to check that the attendee network can carry translated audio to every listener, and to agree on the requirements with the venue IT team before the event.

    This guide is for event organizers, production and venue IT teams.

    Before you begin

    • Know how many attendees you expect to listen at the same time, and where they'll sit.
    • Identify the venue IT contact who manages the attendee Wi-Fi.
    • Set up KUDO for the event. See Set up KUDO translation for an onsite event.

    Why airtime matters more than internet speed

    Attendees receive translated audio as a steady stream of small, real-time audio packets, about 50 a second for each listener. Every packet uses a fixed share of an access point's (AP's) airtime, whatever its size. That's why the limit at a large event is the number of listeners each AP can serve, not the internet speed.

    On Wi-Fi 5, each listener uses roughly 1% of an AP's airtime, so 35 listeners on one AP use over 40% of it for KUDO alone. Wi-Fi 6 and later with OFDMA can serve several listeners in a single transmission, which is why large audiences require it.


    Requirements for all events

    • A dedicated or isolated 5 GHz network, using Wi-Fi 5 (802.11ac) or later
    • Coverage in every area where attendees will listen, including overflow areas
    • UDP traffic allowed through the firewall, and unicast supported
    • At least 128 kbps of bandwidth per listener
    • An attendee network that meets the rules in Firewall and network requirements, including no captive portal, no per-device bandwidth limits and no UDP filtering

    Requirements for large audiences

    If any AP will serve more than about 11 listeners, the attendee network also needs the following.

    Area Requirement
    Wi-Fi generation Wi-Fi 6, 6E or 7 access points with OFDMA (orthogonal frequency-division multiple access) enabled for downlink. MU-MIMO alone doesn't provide the capacity KUDO needs.
    Listeners per AP 35 or fewer with Wi-Fi 6 or 7 and OFDMA, or about 11 or fewer without OFDMA. Never plan more than 80 seats per AP in any zone.
    Signal quality At the farthest seat in each zone: RSSI (received signal strength) of −70 dBm or better, and MCS (modulation and coding scheme) 5 or higher.
    Channel plan A written plan that covers channel widths, channel reuse and the number of APs per zone. Use 5 GHz as the main band, and 6 GHz where permitted.
    Central control One controller with fixed channel and power profiles for each zone, rather than adjusting APs one at a time.
    Full-room tuning Check power and channels with the hall at least 80% full before the first session. A test in an empty room gives optimistic results, because people absorb the 5 GHz signal.
    Even load Devices spread evenly across the APs in each zone, with about 10% spare APs on site.
    Internet capacity At least 128 kbps per listener plus 50% headroom, on top of other attendee traffic. Use two independent internet connections with automatic failover.
    DHCP and NAT Sized for the peak number of devices.

    Size the network

    These examples assume 35 listeners per AP with OFDMA, about 11 without OFDMA, about 10% spare APs, and 128 kbps per listener plus 50% headroom.

    Concurrent listeners Minimum APs with Wi-Fi 6 or 7 and OFDMA Minimum APs without OFDMA Internet for KUDO (Mbps, including 50% headroom)
    500 17 51 96
    1,000 32 101 192
    2,000 64 201 384
    3,000 95 301 576
    5,000 158 501 960

    To estimate for a different audience size:

    1. Divide the number of concurrent listeners by 35 (with OFDMA) or 11 (without OFDMA), then round up.
    2. Add 10% for spare APs, then round up.
    3. For internet capacity, multiply the number of listeners by 128 kbps, then add 50%.

    These figures cover KUDO traffic only. They don’t include anything else attendees do on the network, such as streaming video, checking email or joining video calls. Plan extra capacity for that traffic.


    Confirm the network with the venue

    1. Send these requirements to the venue IT team in writing. Ask them to confirm the AP model, Wi-Fi generation, OFDMA status, number of APs per zone and number of internet connections.
    2. Agree in writing who is responsible for the attendee network.
    3. Run a loaded test with the hall as full as possible.
    4. If the venue can't meet these requirements, plan a fallback, such as FM receivers where permitted or backup sessions.

    Firewall and network rules

    The attendee network must also meet KUDO's firewall and network requirements, including allowing TCP 443 and UDP. See Firewall and network requirements


    Get help planning your network

    Contact KUDO Support before your event if you'd like help validating your workflow, reviewing audio routing or confirming that your network is ready.


    Related content

  • KUDO Single Sign-On (SSO) Implementation

    KUDO supports Single Sign-On (SSO) through SAML 2.0, allowing users to sign in to KUDO after authenticating through your organization's Identity Provider (IdP). KUDO acts as the Service Provider, and your organization acts as the IdP. If a user doesn't already have a KUDO account, one can be created automatically upon their first successful sign-in.

    By default, new users are provisioned with the Meeting Participant role unless a different role is specified in the SAML response. If a user is later invited to a session with a different role, that role can be associated with their account, and they may be able to select it at login.

    Supported roles: Meeting Participant, Interpreter, Viewer, and Operator.


    Step 1 — Request SSO Setup from KUDO

    To begin, email the following information to support@kudo.ai:

    • Your KUDO account email address
    • Your organization name
    • Your Identity Provider (Okta, OneLogin, or Microsoft Entra ID)

    Once KUDO creates your organization in the system, the support team will provide the SAML configuration details you'll need, including the ACS URL, Login URL, Single Logout URL, and Entity ID.


    Step 2 — Configure Your Identity Provider

    Your IT administrator will need to log in to the Identity Provider with administrator permissions and create a SAML connector for KUDO using the details provided. Map the following custom fields in the IdP configuration:

    Name Value
    First Name first_name
    Last Name last_name
    Email email
    Role participant, interpreter, operator, viewer

    If no role is assigned in the IdP, KUDO will default to the Meeting Participant role.

    Once configuration is complete, download the SAML metadata file and send it to support@kudo.ai.


    Step 3 — Submit Your User List

    Provide a list of users who will be accessing KUDO through SSO. KUDO will use this to ensure each user is associated with the correct organization in the system.


    Step 4 — Confirmation

    Once setup is complete, KUDO will confirm that SSO is active. Users can then sign in to KUDO using your organization's SSO provider.


    Need Help? 

  • Firewall & Network Requirements

    Configure firewalls, proxies and corporate networks so users can reach KUDO meetings, audio, video, captions, AI translation and interpretation.

    This guide is for IT administrators and network and security teams.

    KUDO uses secure web technologies and real-time communication services to deliver multilingual meetings, AI translation, captions, audio and video. If users connect from a corporate, government, educational or other restricted network, firewall or proxy settings may block parts of the KUDO platform. This guide lists the domains, ports and IP ranges to allow.


    Signs of a firewall or network restriction

    Users affected by firewall or proxy restrictions may see:

    • Meetings that won’t join
    • Loading screens that never finish
    • Missing audio or video
    • Interpretation channels that don’t load
    • The KUDO panel not appearing in Microsoft Teams
    • Frequent disconnects or reconnects
    • Captions or AI translation failing to start
    • Webcam or microphone connection failures
    • The KUDO Widget or Mobile Link not loading properly

    If the page and captions load but there’s no audio, first check whether UDP traffic is being blocked or filtered.


    Domains

    Depending on your firewall or endpoint security settings, you may need to allow these domains:

    • *.kudoway.com for accounts in the USA or Asia-Pacific region
    • *.kudoway.eu for accounts in the Europe region
    • *.kudoway.ca for accounts in the Canada region
    • *.tokbox.com
    • *.opentok.com

    If your firewall or policy doesn’t allow wildcard domains, allow these subdomains for your account’s region instead.

    Region Subdomains
    USA https://live.kudoway.com, https://api.kudoway.com, https://session-console.kudoway.com
    Europe https://live.kudoway.eu, https://api.kudoway.eu, https://session-console.kudoway.eu
    Canada https://live.kudoway.ca, https://api.kudoway.ca, https://session-console.kudoway.ca
    Asia-Pacific https://asia.kudoway.com

    Ports

    All media traffic (audio and video) goes through STUN servers. All traffic is bidirectional.

    Port Status Notes
    TCP 443 Required Used for all KUDO traffic, and for media if UDP is blocked
    UDP 3478 Recommended UDP’s low overhead gives better audio and video quality in most cases

    Also allow outbound UDP for media traffic. Don’t block or throttle UDP. If UDP is blocked, KUDO sends media over TCP 443 (SSL) instead, at lower quality.


    Proxies

    If your network can reach the internet only through a proxy, the proxy must either be transparent or be configured in the browser for HTTPS connections. KUDO doesn’t support proxies that require authentication.


    Firewall behavior

    Some firewalls and endpoint security tools use stateful packet inspection or flood control. These features can deprioritize or throttle media streams, which lowers quality or, in some cases, blocks the stream. Users may notice audio or video problems after a short period of use. If this happens, contact your organization’s IT security team.

    At large events, stateful inspection or flood control can degrade streams for many attendees at once. Check firewall and NAT session capacity against the expected number of devices.


    Attendee networks at onsite events

    On the network attendees use to follow KUDO at an onsite event:

    • Don’t use a captive portal.
    • Don’t set per-device bandwidth limits.
    • Don’t filter UDP traffic.

    For Wi-Fi capacity and sizing, see Set up KUDO translation for an onsite event.


    Microsoft Teams

    If you use KUDO with Microsoft Teams, all the requirements above apply. Also allow these subdomains and ports:

    • https://teams-bot.kudoway.com
    • https://teams-web.kudoway.com
    • TCP port 8445
    • TCP port 9444

    IP ranges

    KUDO uses dynamic IP addresses and elastic load balancing, so we can’t guarantee the exact IP addresses your meetings will use. We can provide ranges instead. We change these ranges periodically for technical and security reasons.

    If your organization allows these ranges, ask KUDO Support to add you to the mailing list for range updates. We notify customers three weeks before a change.


    IP version support

    KUDO supports IPv4.


    Ranges to allow

    Depending on your firewall settings and policies, you may need to allow two sets of addresses: the server for your account’s region, and KUDO Media Services.

    These ranges were updated on March 2022.

    Region server IP addresses Required when
    USA 44.194.123.245, 54.183.2.235 Your account is in the USA region
    Europe 3.125.64.235, 34.247.171.240 Your account is in the Europe region
    Canada 3.97.146.187 Your account is in the Canada region
    Asia-Pacific 47.52.44.158, 47.52.109.58 Your account is in the Asia-Pacific region

    KUDO Media Services (required for all accounts):

    3.123.12.128/28
    3.127.48.224/28
    3.214.145.96/27
    3.234.232.160/27
    3.234.248.80/28
    3.235.255.176/28
    3.248.234.48/28
    3.248.243.144/28
    3.248.244.96/27
    3.25.48.192/28
    3.38.113.0/24
    3.38.114.0/24
    3.38.91.128/25
    3.7.161.0/26
    3.7.161.48/28
    13.251.158.0/28
    15.228.1.16/28
    18.139.118.176/28
    18.141.165.128/27
    18.156.18.0/27
    18.157.71.112/28
    18.179.48.208/28
    18.180.159.224/27
    18.202.216.0/28
    34.218.216.144/28
    34.222.66.96/28
    34.223.51.192/27
    34.223.51.224/27
    35.158.127.224/28
    44.232.236.96/27
    44.234.90.64/28
    52.200.60.16/28
    52.213.63.176/28
    52.41.63.240/28
    52.51.63.16/28
    52.65.127.192/27
    52.66.255.192/27
    54.233.127.224/29
    54.250.250.208/28
    54.69.125.241/32
    54.89.253.64/28
    99.79.160.16/28
    99.80.88.240/28
    168.100.64.0/18

    Related content

  • Network Access & Regional Restrictions

    Access & Restrictions

    KUDO meetings can be joined from any location with a stable internet connection. If you're connecting through a corporate, government-managed, or heavily restricted network, your IT team may need to adjust firewall or security settings to allow access to KUDO services. See the KUDO Firewall & Network Requirements guide for recommended configurations.


    Regions with Known Access Limitations

    Some countries restrict cross-border data traffic or apply internet routing policies that can affect access to cloud-based services like KUDO. In these locations, you may experience service disruptions, degraded audio or video quality, or difficulty connecting at all. KUDO is aware that access may be unreliable or unavailable in the following countries: 

    • China
    • Belarus
    • Crimea
    • Cuba
    • Iran
    • Jordan
    • Kuwait
    • North Korea
    • Oman
    • Russia
    • Sudan
    • Syria
    • United Arab Emirates (UAE)
    • Donetsk People's Republic of Ukraine
    • Luhansk People's Republic of Ukraine
    • Zaporizhzhia Oblast
    • Kherson Oblast

    This list is not exhaustive and may change without notice as regional regulations and internet policies evolve.


    Using a VPN

    Participants connecting from restricted regions may be able to access KUDO through a VPN. Keep in mind that VPN connections can introduce additional latency or affect audio and video quality depending on your provider and network conditions.


    Need Help? 

     

Captioning

  • Displaying Captions for KUDO Live Events

     

    Displaying the multilingual closed captions from the KUDO Mobile Link on a large display can be achieved using basic AV skills and hardware devices. We highly recommend seeking professional AV support, especially during large-scale conferences or meetings where successful interpretation is critical.

     

    Requirements:

    - Large display or comfort monitor.

    - Dedicated computer with HDMI output, or a USB adapter with an SDI output.

    - Video scaler hardware (Brands such as Blackmagic, AJA, AVPro, Decimator)

    - Stable wired internet connection.

    - Appropriate power and display cabling (HDMI, SDI).

    - Professional AV technician.

     

    1. Open The KUDO Mobile Link in Your Web Browser 

    Use a dedicated laptop or PC with a wired internet connection to open the KUDO Mobile Link in a supported browser (Google Chrome, Mozilla Firefox, or Microsoft Edge).

    The meeting organiser of the KUDO meeting must share this mobile link ahead of time.

    Once the meeting is live and "presenter" audio is correctly being published, you can select the language you'd like to display by using the dropdown list.

     

    Screenshot 2025-06-13 at 17.27.28.png

    You can select between coloured backgrounds by clicking the "Aa" symbol at the top right. Here you have the choice between light and dark mode.

     

     

    Screenshot 2025-06-13 at 17.30.04.png
    Display Cc wide Monitor.png

    Tips:

    Double check that you do not have any + or - "accessibility zoom"  function taking place within your browser for consistent text scaling.

    Also check to mute the audio from your device or directly from the KUDO mobile link. (It's best to avoid having the audio of the translation leak out of a loud speaker when within close proximity to your microphone system in the same room).

     

    2. Connect the Hardware and Cabling

    Connect your laptop or PC to the video scaler’s input using an HDMI cable.

    On your computer (Windows or Mac OS), go to the display settings and select “Extend Display” instead of mirroring. This keeps the main screen private while sending captions to the external display.

     

    Next, connect the video scaler’s output to your main display using HDMI or SDI, depending on cable length and the video scaler hardware you’re using.

     

    Tip: Avoid using HDMI for long cable runs—SDI is more reliable over distance.

     

    3.  Scale the Image on the Video Scaler

    Once your system is connected and you've double checked that audio is still being passed through to the KUDO meeting, use the video scaler controls to adjust the image size and aspect ratio. 

    Most video scalers have buttons and a small screen for making adjustments. You can zoom in or crop the image so that only the captions are visible, hiding the rest of the interface for a clean look.

     

    Tip: Many clients prefer scaling the image so the KUDO interface (icons, buttons, etc.) is hidden, leaving just the captions visible on screen.

     

  • Adding a Caption Overlay with NDI

    This guide walks through how to capture live programme audio, generate multilingual AI captions through KUDO, overlay them onto a video feed in OBS Studio, and stream the final output to Vimeo through an Epiphan Pearl encoder.

    Audience: Hosts, Producers, Operators, and AV technicians configuring AI caption overlay workflows for live productions.


    How the Workflow Fits Together

    The workflow runs across four stages. First, a dedicated ingest computer joins the KUDO meeting as a Participant and routes NDI programme audio into KUDO AI for caption generation. KUDO processes that audio and delivers real-time captions through the KUDO Mobile Link. OBS Studio then composites those captions over the programme video feed. Finally, an Epiphan Pearl encoder takes the OBS output and streams the captioned programme to Vimeo via RTMP.


    Before You Start

    Confirm that the KUDO meeting has been created with AI Captions enabled and the Mobile Link is available for the desired caption language. Vimeo streaming credentials should be on hand, the TriCaster programme output should be accessible via NDI, and the following software should be installed before beginning: NDI Tools, VB-Audio Virtual Cable, OBS Studio, the DistroAV OBS plugin, and Google Chrome or Microsoft Edge. The Epiphan Pearl encoder should also be accessible on the local network.

    For the best production stability, use wired Ethernet connections on all systems, separate the ingest and overlay workflows across different machines when possible, and test NDI routing and caption latency before the live event. Validate the Vimeo ingest before going live.

    Important: Audio quality, network stability, and source platform performance directly affect AI caption quality and synchronization.


    Equipment

    You'll need a TriCaster as the programme video and audio source, an Epiphan Pearl as the RTMP encoder for Vimeo delivery, a dedicated Ingest PC to route programme audio into KUDO, and an Overlay/Production PC running OBS Studio. The Ingest PC and Overlay PC can be combined into a single machine if CPU resources allow. Always test under production load conditions before going live.


    Phase 1 — Configure the Ingest PC

    The goal here is to capture programme audio from the TriCaster NDI output and send it into KUDO as the microphone source. KUDO AI then generates live captions from that incoming audio.

    1. Install NDI Tools and VB-Audio Virtual Cable, then restart the computer.

    2. Open NDI Virtual Input and select the TriCaster programme NDI source. Confirm the NewTek NDI Audio device appears in Windows audio settings and that audio signal activity is visible. For additional browser compatibility, optionally route the signal through VB-Cable as the browser microphone input.

    3. On the Ingest PC, open Chrome or Edge and join the KUDO Participant/Speaker link as a Participant. Inside KUDO, select the NDI audio device or VB-Cable output as the microphone source, confirm microphone activity is visible, and mute local speakers to avoid feedback.


    Phase 2 — Retrieve KUDO Captions

    4. Open the KUDO Mobile Link for the desired caption language in a browser. This caption feed will be embedded into OBS Studio as a Browser Source in the next phase.


    Phase 3 — Configure the Caption Overlay in OBS

    The goal here is to composite the KUDO caption feed over the programme video, creating a single captioned output for Vimeo delivery.

    5. Inside OBS, add a new NDI Source and select the TriCaster programme feed. Set the output resolution to match your production format. The programme feed should appear in the OBS canvas.

    6. Add a new Browser Source and paste the KUDO Mobile Link URL. Set the resolution to match the production output — 1920x1080 is recommended.

    7. Move the caption layer above the programme video source and position captions in the lower third of the canvas. Resize or crop the Browser Source as needed. Adding a semi-transparent black background behind the captions can improve readability. Preview the scene and confirm captions appear correctly over the programme feed.


    Phase 4 — Configure OBS Output to Epiphan Pearl

    8. Choose one of the following methods to deliver the OBS output to the Epiphan Pearl:

     Method A: NDI Output (Recommended)Method B: HDMI Loop-back
    How it worksOBS sends its output as an NDI stream over the network; Pearl ingests it as an NDI sourceOBS Virtual Camera output is captured through a video capture card or direct HDMI connection into the Pearl
    RequirementsPearl-2 or Pearl Nexus with NDI input support; DistroAV OBS plugin installedOverlay PC with HDMI output connected directly to the Pearl HDMI input
    OBS settingGo to Tools > NDI Output Settings and enable Main OutputGo to Tools > Start Virtual Camera, then connect HDMI to the Pearl
    Pearl settingAdd an NDI source and select the OBS NDI output as the channel inputSet the Pearl channel input to HDMI IN connected to the Overlay PC

    Phase 5 — Stream to Vimeo

    9. Inside Vimeo, open the live event and locate the RTMP URL and Stream Key. Keep these available for the next step.

    10. Inside the Epiphan Pearl web interface, select the correct input source and add a new RTMP destination. Paste the Vimeo RTMP URL and Stream Key, then configure encoding settings. Recommended output: H.264 video, AAC audio, 1080p, 25 or 30 fps. Click Apply, then Start Streaming.


    Troubleshooting

    IssuePossible CauseRecommended Action
    No captions appear in OBSIncorrect Mobile Link URLVerify the correct Mobile Link was added as a Browser Source
    Captions are delayed or inconsistentPoor source audio qualityCheck programme audio quality and microphone routing
    OBS Browser Source appears blankBrowser rendering issueRefresh the Browser Source or reopen OBS
    Audio feedback loop occursLocal monitoring enabledMute local speakers or use headphones
    Epiphan Pearl doesn't receive OBS outputNDI or HDMI routing issueVerify OBS output settings and Pearl input configuration
    Vimeo stream fails to startInvalid RTMP credentialsVerify the Vimeo RTMP URL and Stream Key
    NDI audio not detected in KUDOIncorrect audio routingVerify NDI Virtual Input and VB-Cable device routing
    Caption overlay blocks video contentOverlay positioning issueReposition or resize the Browser Source in OBS

    Known Limitations

    AI caption quality depends heavily on source audio quality. Network instability may affect NDI routing and caption synchronization. OBS Browser Sources may need to be refreshed during extended productions, and combined ingest and overlay workflows on a single machine may require additional CPU resources. Caption timing may vary slightly depending on AI processing latency, and Vimeo synchronization behavior can vary by network conditions.


  • Adding a Caption Overlay with OBS

    Requirements

    • Dedicated computer with a wired internet connection to open the KUDO Mobile Link in a supported browser (Google Chrome, Mozilla Firefox, or Microsoft Edge).
    • The latest version of OBS Studio installed.
    • An active KUDO session with audio ingestion of the source language.
    • An active KUDO Mobile Link (URL).

     

    Step-by-Step Setup in OBS

    Step 1: Open OBS and Add a Browser Source

    1. Open OBS Studio.
    2. In the Sources panel, click + and select Browser.
    3. Name the source (e.g., KUDO Captions) and click OK.
    4. Paste the KUDO Mobile Link URL into the “URL” field.
    5. Set the dimensions:
      • Width: 1280
      • Height: 100 (adjust as needed)
    6. Click OK to save.

    Step 3: Position and Style Your Captions

    • Drag and position the browser source at the bottom of your video frame.
    • Resize it to fit your stream layout cleanly.
    • Optional: Add a background strip for visibility:
      • Add a Color Source underneath the caption layer.
      • Use a dark or semi-transparent color (e.g., black with 50% opacity).

    Step 4: Start Virtual Camera/Go Live

    1. Set up your additional sources (camera, slides, screen share).
    2. Confirm that captions appear in your OBS preview.
    3. Start streaming to your OBS Virtual Camera output or desired RTMP string.

    Optional: Add Translated Audio

    To stream audio interpretation alongside captions:

    1. Capture the language audio feed from the KUDO Mobile Link.
    2. Add the audio in OBS using either:
      • Audio Input Capture (if using a virtual audio cable), or
      • Browser Source
    3. Match the caption overlay with the corresponding audio.

     

Streaming

  • Configuring RTMP Streaming to YouTube

    This guide walks through how to configure a KUDO Meeting to broadcast multilingual audio channels to YouTube using RTMP broadcasting. By the end of this process, each configured KUDO language channel will stream independently to its own YouTube Live destination.

    Audience: Hosts, Operators, AV Technicians, and meeting organizers.


    Before You Start

    Before configuring YouTube streaming, confirm that the KUDO meeting has already been created and translation languages are configured. You'll also need a separate YouTube Live stream created for each language, with its own unique stream key, and a Host with permission to manage broadcast settings in both KUDO and YouTube Studio.

    Important: Each language must be broadcast independently to its own YouTube Live destination. Reusing the same stream key across multiple languages will interrupt or overwrite active broadcasts.


    Configuring YouTube Streaming

    1. In YouTube Studio, create one YouTube Live stream for each language you plan to broadcast. Each stream must have its own unique stream key.

    1. From the KUDO meeting dashboard, go to Settings > Broadcast.
    2. Enable RTMP Stream, then click + Add RTMP Stream.
    3. Enter the YouTube stream URL in the Server URL field and the corresponding stream key in the Stream Key field. Then select the KUDO language channel you want to broadcast to that destination.
    4. Click Start Broadcast to begin streaming the selected language channel to YouTube.
    5. Repeat steps 3 through 5 for each additional language.

    Troubleshooting

    Task Action Expected Result
    Verify YouTube Stream Configuration If the YouTube stream does not start successfully, confirm that the Stream URL and Stream Key are correct, the YouTube stream is active, the selected KUDO language channel is available, and the broadcast was started inside KUDO. The RTMP broadcast connects successfully and the translated language stream becomes available on YouTube.
    Verify Internet Stability Confirm that the broadcasting computer has stable upload bandwidth and network connectivity. The RTMP broadcast remains stable without buffering, interruptions, delayed audio, or disconnects.
    Restart the Broadcast If the YouTube stream becomes unstable, stop the RTMP broadcast from KUDO, verify the Stream URL and Stream Key, then restart the broadcast from KUDO. The RTMP broadcast reconnects and the YouTube stream resumes normally. The live stream may temporarily pause during reconnection.

    Need Help? 

Voting

  • Managing Polls & Voting

    This guide walks participants through how to vote in live polls and view results during a KUDO meeting.

    Audience: Participants, Hosts, Presenters, and meeting attendees participating in live polls during KUDO meetings.


    Polls can be configured by going to Content > Polls before the meeting, or added during the live session. KUDO supports multiple choice, parliamentary voting, and anonymous ballot formats. Both Operators and Hosts can start, stop, and publish results, and monitor voting activity in real time.

    Modifying a poll after it's already live may require participants to refresh their browser, so pre-configuring polls before the meeting begins is strongly recommended. Poll access can also be restricted to specific delegates, and anonymous voting or vote weighting can be configured in advance.

    Screenshot 2026-05-30 142803.png

    Before you start

    Before participating in a poll, confirm that you've already joined the KUDO meeting, the Host or Operator has launched a poll, and the Polls panel is visible inside the meeting interface. Stay connected to a stable internet connection and submit your vote before the Host closes the poll.

    Note: Poll availability and result visibility depend on Host or Operator permissions during the meeting.


    Voting in a Live Poll

    1. When a Host launches a poll, the Polls icon on the right-hand side of the meeting interface becomes highlighted. Click it to open the voting panel.
    2. Read the poll question and review the available answer options before selecting one.
    3. Click your preferred answer, then click Submit to cast your vote. Once submitted, the poll status updates to Voted while you wait for the Host to close the poll and optionally publish the results.

    Viewing Poll Results

    1. After the poll ends, the Host may choose to publish results to participants depending on the meeting's configuration.
    2. When results are published, the Results tab becomes highlighted inside the Polls panel.
    3. Click the Results tab to view the outcome.
    4. Poll results display a visual summary using bar or pie charts, and may include a breakdown of eligible voters, actual voters, and non-voters.

    Troubleshooting

    Issue Possible Cause Recommended Action
    Polls panel is not visible Poll hasn't been launched Wait for the Host or Operator to launch the poll
    Vote cannot be submitted Poll already closed Verify the poll is still active before submitting
    Poll results are unavailable Host hasn't published results Wait for the Host to publish
    Poll interface is unresponsive Browser or network issue Refresh the meeting and reopen the Polls panel
    Vote status doesn't update Submission didn't complete Reopen the Polls panel and verify your vote was submitted

    Need Help?

Hybrid Meetings

  • Route KUDO Translation Audio to a Dante Network

    Audience: AV/IT and Audio Managers.

    Use Audio Manager to route translated channels to Dante destinations. Venue Audio OUT supports AI and human interpretation; Venue Audio IN is for human interpretation only.

    Before you start

    Install Dante Virtual Soundcard and Dante Controller. Use wired Ethernet on the destination devices’ Dante network and verify clock synchronization.


    Steps

    1. Enable Audio Manager in the meeting’s advanced settings. Add the assigned user under Audio Managers and complete invitation setup if needed.
    2. On the dedicated computer, start Dante Virtual Soundcard with WDM and 16 × 16 channels, as in the documented configuration.
    3. Sign in with the assigned Audio Manager role. Open the meeting settings and Venue Audio OUT.
    4. Select Edit Audio Settings. Map each language to a Dante output and save.
    5. In Dante Controller, subscribe those outputs to the required destination channels and test each feed.

    What to expect

    Subscribed destinations receive the mapped language audio.


    Troubleshooting

    Issue / TaskPossible CauseRecommended Action
    Missing channelsClock or network issueCheck synchronization, network visibility, and Virtual Soundcard operation.
    Unstable routingConnection instabilityReopen Audio Manager, restart Virtual Soundcard, and verify subscriptions; audio may briefly disconnect.


     

  • Receiving Interpreter Booth Audio Via Dante

    This guide walks through how to configure a KUDO Meeting with Audio Manager for Dante audio input. By the end of this process, interpreter booth audio from an external source will be captured and routed into the KUDO language selector through a Dante-enabled audio network.

    Audience: Audio Managers, AV technicians, Operators, and meeting organizers configuring KUDO for onsite, hybrid, or broadcast workflows.


    Before You Start

    Before configuring Audio Manager and Dante input, confirm that the KUDO meeting is ready to be scheduled, Dante Virtual Soundcard is installed on the Audio Manager computer, Dante Controller is installed and configured on the Dante network, and the Audio Manager computer is connected to the same Dante network as the source devices.

    For the best audio stability, use a wired Ethernet connection, avoid Wi-Fi for Dante workflows, close unnecessary audio applications, and confirm that Dante network and clock synchronization are stable before the meeting begins.

    Important: Venue Audio IN is only available for Human interpretation workflows.


    Scheduling a Meeting with Audio Manager

    1. While scheduling the KUDO meeting, click Advanced Settings and scroll down to enable the Audio Manager role. This allows interpreter audio channels to be routed through Dante-compatible workflows.
    2. Click the Users tab, select Audio Managers, then click + Add Audio Manager and enter the user's details. If this is their first Audio Manager session, they'll need to complete the account setup from the invitation email before joining the meeting.

    Configuring Audio Manager

    1. On the Audio Manager computer, install and open Dante Virtual Soundcard. Set the Audio Interface to WDM and Channels to 16 x 16.
    2. Log in to KUDO using the assigned Audio Manager credentials.
    3. Select the Audio Manager role to access Dante routing and venue audio configuration tools.
    4. Locate the meeting, go to Settings, and select Venue Audio IN.
      • Venue Audio IN sends external audio — such as onsite interpreter booth feeds — into KUDO. Available for Human interpretation sessions only.
      • Venue Audio OUT sends translated KUDO audio to external devices, Dante systems, or broadcast infrastructure. Available for both AI and Human interpretation sessions.
    5. Click Venue Audio IN.
    6. Click Edit Audio Settings.
    7. Select the appropriate Dante source devices and assign them to the desired interpretation language channels.
    8. Click Publish All to activate the Dante audio routing configuration.
    9. Once routing is active, assigned devices will show a Live status inside Audio Manager. Keep this browser tab open for the duration of the meeting.


    Troubleshooting

    Issue / Task Possible Cause Recommended Action
    Dante input channels are not visible inside Audio Manager Dante devices are not synchronized to the same Dante clock source Verify that all Dante devices are properly synchronized to the same Dante clock source before the meeting begins.
    Dante source devices are not visible or interpreter audio is unavailable Dante network connectivity issue Confirm that:

    • Dante Virtual Soundcard is running
    • the Audio Manager computer is connected to the Dante network
    • source Dante devices are visible inside Dante Controller
    • firewall or network policies are not blocking Dante traffic
    Interpreter audio channels stop updating or audio routing becomes unstable Dante routing or Audio Manager connection instability Restart Dante Virtual Soundcard, reopen Audio Manager, and verify Dante routing subscriptions inside Dante Controller. Audio feeds may temporarily disconnect while the routing reconnects.

    Need Help? 

  • Connect KUDO Mobile Link Audio to RF or IR Systems

    Audience: AV/IT.

    Feed language audio from individual browser sessions into an FM/RF or infrared distribution system.

    Before you start

    Provide one powered laptop per language, wired internet, Chrome, compatible transmitter cabling, and optionally a USB audio interface.


    Steps

    1. Open the meeting’s Mobile Link on each laptop and select one language per device. Label each laptop.
    2. Confirm the language feed with headphones.
    3. Connect the headphone output to the transmitter input, or select a USB audio interface as the system/browser output and cable its output to the transmitter.
    4. Assign each language to the appropriate transmitter or IR system channel. Verify receivers are tuned correctly.
    5. Prevent laptop sleep and notifications, test every receiver path, and monitor the feeds during the event.

    What to expect

    Attendees listen on the venue’s receivers while the laptops continue receiving KUDO audio through the internet.


    Troubleshooting

    Issue / Task Possible Cause Recommended Action
    Hum or interference Analog connection noise Consider a ground-loop isolator or USB interface.
    Wrong language Channel selection mismatch Check the laptop selection and receiver channel.

    For multiple outputs from one computer, see Dante routing.

  • Join a Hybrid KUDO Meeting as an Onsite or Online Participant

    Audience: Participants.

    Choose the participation mode that matches how you will use the venue’s equipment. These steps describe the hybrid web meeting console.

    Steps

    1. Open the meeting link and enter your name and email.
    2. Choose I’m an on-site Participant if using venue microphones, cameras, and interpretation equipment instead of the KUDO platform. Choose the online participant option for participation through the KUDO Meeting platform.
    3. If onsite and the session uses a speaking queue, select Request to Speak. Wait for acceptance, then use the venue microphone.

    What to expect

    Onsite mode does not provide microphone, camera, or interpretation-language controls in the web console. Online mode provides those controls. Both modes can access meeting documents.


    Selected the wrong mode?

    Ask the Host or Operator to change your participation mode from the user list. You receive a notice when it changes.


    Joining on a phone

    Follow the organizer’s instructions for your assigned access method. The KUDO Live joining guide covers general mobile joining; it does not establish identical hybrid controls. For browser translation access, see Mobile Link and QR codes.


     

  • How to enable Hybrid Meetings: Participants and Operators

    Join the meeting as Online and Onsite Participants

    Participants can join the Hybrid Meeting as an “Online” or “On-site” participant from a customized onboarding page.

    • Enter Name & Email Id or Email Id and Password to join the meeting  
      • Select “I’m an on-site Participant” to join as Onsite 
      • Select “I’m an online participant” to join as Online  

    mceclip0.png

    Switching participant from onsite to online and vice-versa 

    An Operator can switch a participant from online to onsite or vice versa from the Meeting console.

    • Go to the Users List → Click on the “…” menu next to the participant's name
      • Click on (On-Site) Change to Online to switch a participant from On-site to Online → Participant receives a modal informing them of the switch
      • Click on (Online) Change to On-site to switch a participant from Online to On-Site → Participant receives a modal informing them of the switch

    mceclip1.png

    mceclip2.png

     

    mceclip3.png

    Request to speak (Onsite – similar to online) 

    • Click on “Request to Speak” --> The Operator sees the Request in the RTS Tab 
    • Operator accepts the request --> the button changes to “Done Speaking” and the onsite participant is listed in the RTS list as accepted 

    mceclip4.png

    Access meeting documents 

    • Click on Documents tab to access all documents available for participants in the hybrid meeting 

    mceclip5.png

    Access Polls 

    To read about KUDO's access polls features, click here