Fix Connect audio, driver and latency issues.

Most Connect problems come from audio routing, the virtual audio driver, or local performance. Start with the quick checklist, then use the section that matches what you see. If you changed several audio settings and want a clean start, use the reset steps below.

Quick recovery checklist

Follow these steps in order for the fastest recovery:

1. Disconnect from the call and turn CONNECT-ON off.
2. Confirm Connect can see your real microphone and real speakers at the bottom of the app.
3. On Windows, confirm the call app uses Microphone: CABLE-A Output and Speaker: CABLE-B Input.
4. If the driver or routing still looks wrong, open your profile menu and click the large red Reset Audio Devices button.
5. Restart Connect, reopen your call app, then press CONNECT-ON again.

Virtual audio driver problem

If the virtual audio driver is missing, not detected or behaving strangely, reset the audio devices from your Connect profile. This is the fastest way to put the routing back to a clean state.

1. Open Connect.
2. Click your profile button in the top-right corner.
3. Find the large red Reset Audio Devices button.
4. Click it and wait for the reset to finish.
5. Close and reopen Connect.
6. Open your meeting app again and select the correct devices.

Auto Route UI refresh issue

Auto Route forces apps to use CABLE-A (microphone) and CABLE-B (speaker) automatically without manual selection. However, sometimes after using Auto Route, the app UI still shows the real device names and doesn't visually refresh. In reality, Connect is using the cables internally — it's just a display issue.

Solution: Restart the app so the UI refreshes and shows the correct CABLE-A/CABLE-B devices.

No sound output in the call

If the other person cannot hear your translated voice, the meeting app is usually listening to the wrong device. On Windows, open the audio settings inside Zoom, Google Meet, Teams, Discord or your call app and set the devices exactly like this:

Windows call app setting	Select this device	What it does
Microphone	CABLE-A Output	Sends the translated Connect voice into the call.
Speaker	CABLE-B Input	Routes call audio through Connect when needed.

After setting those devices, press CONNECT-ON and speak normally. If there is still no output, go to your profile and run Reset Audio Devices, then reopen the call app so it reloads the available devices.

No microphone input in Connect

If Connect is not hearing you, check the app itself before changing the meeting platform. At the bottom of Connect, the Available Microphones selector should be your real physical microphone, headset or webcam microphone. It should not be a virtual cable unless you intentionally configured a custom routing setup.

• Choose your real microphone in Connect.
• Make sure the microphone is not muted in your operating system.
• Close other apps that may be locking exclusive microphone access.
• Use How I Sound? to test before joining the call.

Distorted voice or robotic audio

If the translated voice sounds robotic, clipped or unstable, first check the same things that affect latency: internet connection, available RAM and microphone quality. Distortion can happen when the audio stream is unstable or when the input contains too much background noise.

• Move closer to the microphone and reduce fan, keyboard or room noise.
• Close heavy apps so Connect has enough memory and CPU headroom.
• Use a stronger internet connection before important calls.
• Run How I Sound? after changing the microphone or noise suppression setting.

High latency or slow translation

High latency usually comes from network quality or local machine load. Connect needs a stable internet connection and enough available RAM to process speech smoothly while your call app is also running.

• Use a stable internet connection. Wired or strong Wi-Fi is better than weak mobile data.
• Close heavy apps, unused browser tabs, games, video editors and background downloads.
• Free up RAM before important calls, especially on machines with limited memory.
• Switch to Instant Mode if you prefer cleaner chunks instead of continuous streaming.
• Keep your microphone close and reduce background noise so speech recognition has less work to do.

If latency suddenly becomes much worse during a call, disconnect, wait a few seconds and reconnect. If the whole computer feels slow, restart Connect after closing the apps that are using the most memory.

Wrong language or incorrect terms

If Connect translates into the wrong language or misses domain-specific vocabulary, the issue is usually configuration rather than audio. Set the source and target languages manually, add language hints, activate the right conversation context and use a pronunciation dictionary for names or special words.

App crashes or freezes

If Connect freezes during a call, restart the app first, then close other audio or video tools that may be competing for the same devices. If the crash happens after audio routing changes, reset audio devices from the profile menu and start again from a clean state.

1. Turn CONNECT-ON off.
2. Close Connect and reopen it.
3. Close unused meeting apps, browser tabs and audio tools.
4. Free up RAM before reopening the call.
5. If audio devices still look wrong, use Reset Audio Devices.

Reset everything back to zero

Use this when multiple audio settings were changed and you are not sure which one caused the problem. Open your profile, click the large red Reset Audio Devices button, then restart Connect. After that, set your call app devices again and run a short How I Sound? test.

1. Reset audio devices from the profile menu.
2. Restart Connect.
3. Restart the meeting app.
4. On Windows, choose CABLE-A Output as the microphone and CABLE-B Input as the speaker.
5. Select your real microphone and real speakers inside Connect.
6. Press CONNECT-ON.

Related Connect resources

• Basic setup guide
• Tutorial for voiceprint, context and dictionaries
• Download or reinstall Connect
• Contact support