Fix no audio, low audio, or missing translation
Find the broken part of the signal path before changing settings. These checks cover what you hear, what the other participant hears, and whether Connect receives your real microphone.
Start with the symptom
“No audio” can describe several different failures. Identify who cannot hear which signal before changing devices, because the outgoing and incoming routes are independent. Record the working device names and settings so the same result can be reproduced on the next call. A clean baseline makes every later quality decision more reliable.
| Symptom | Check first | Why |
|---|---|---|
| The other participant hears nothing | Calling-app microphone | The outgoing path may not use Connect Mic |
| The other participant hears your untranslated voice | CONNECT-ON and translation mode | The call may bypass Connect or translation may be inactive |
| You cannot hear the other participant | Calling-app speaker for the selected mode | Connect Speaker is not required in every unidirectional mode |
| How I Sound? receives no voice | Available Microphones in Connect | The physical input is muted, unavailable, or incorrectly selected |
| Audio is present but too quiet | Physical microphone level and position | The input reaches Connect below a useful level |
Test the physical devices inside Connect
This first test removes the calling platform from the path. If Connect cannot hear the physical microphone here, changing Zoom or Teams will not solve the underlying input problem. Compare the result in Connect and in the calling application before adjusting another part of the signal path.
- At the bottom of Connect, set Available Microphones to the real headset or microphone you speak into.
- Set Available Speakers to the real headset or speakers you listen through.
- Confirm the microphone is not muted on the headset, in Windows/macOS, or with Connect's bottom microphone control.
- Select How I Sound?, speak a complete sentence, then listen to the preview.
- If there is no input, try another physical microphone or USB port before changing the calling app.
Match routing to the translation direction
The virtual microphone and speaker are not required in every mode. Use only the route needed for the side being translated. A clean baseline makes every later quality decision more reliable. Start with one controlled change so the responsible microphone, playback device, or processing stage stays identifiable.
| Mode in Connect | Microphone in the calling app | Speaker in the calling app | Expected result |
|---|---|---|---|
| Bidirectional | Connect Mic | Connect Speaker | Both sides can pass through translation |
| Unidirectional | Connect Mic | Normal/default speaker | Your voice is translated; you hear the other person normally |
| Unidirectional reverse | Normal/default microphone | Connect Speaker | You hear translated incoming speech; your voice stays direct |
Change these devices inside Zoom, Teams, Meet, Discord, your browser softphone, or the call application itself. System-wide defaults do not always replace an app's saved choice.
Confirm the session is actually active
Correct device selection is only preparation. Translation begins after the session starts and Connect receives enough speech to produce a transcription. Start with one controlled change so the responsible microphone, playback device, or processing stage stays identifiable. Compare the result in Connect and in the calling application before adjusting another part of the signal path.
- Choose different From and To languages.
- Verify the correct translation type is selected.
- Start or join the call, then return to Connect.
- Press CONNECT-ON. Confirm the session timer starts and live transcription reacts when you speak.
- Speak normally for one full sentence; very short sounds may not produce a useful translation test.
Fix low or inconsistent volume
A quiet signal is usually created before translation. Improve the physical input first, then decide whether Connect enhancement is still necessary. Compare the result in Connect and in the calling application before adjusting another part of the signal path. Record the working device names and settings so the same result can be reproduced on the next call.
- Place a boom microphone one to two finger widths from the corner of your mouth.
- Raise the physical microphone input level gradually; avoid large boost settings that introduce hiss.
- Connect the headset directly instead of through an unstable USB hub.
- Turn off overlapping microphone effects, automatic gain, voice isolation, and third-party noise processing one at a time.
- Keep headset speaker volume moderate so playback does not leak into the microphone.
Run How I Sound? after each change. Changing one variable at a time makes the cause visible.
Refresh stale device lists
Calling applications often keep the devices that were present when they opened. Refresh the applications in a controlled order after connecting or reinstalling hardware. Compare the result in Connect and in the calling application before adjusting another part of the signal path. Record the working device names and settings so the same result can be reproduced on the next call.
- Turn CONNECT-ON off and leave the call.
- Close the calling app completely, including browser tabs using the microphone.
- Reconnect the headset, then reopen Connect and select the physical devices again.
- Reopen the calling app and reselect the appropriate Connect virtual device.
- If Connect Mic or Connect Speaker is absent everywhere, follow the installation and audio-driver recovery guide.
Escalate with the right details
Contact support if the physical microphone works in other apps but not in How I Sound?, or if correct routing still produces no transcription. Include the call app, translation mode, From/To languages, selected devices in both applications, whether the timer starts, and which participant cannot hear which signal.
Frequently asked questions
Use these answers after the symptom table has identified the affected side of the call. Begin with the answer that most closely matches the symptom or decision in front of you. Verify that recommendation in a short test before changing another setting or workflow. If the result remains unclear, record the exact behavior and the conditions under which it occurs.
Why can the other participant hear my natural voice instead of the translation?
The calling app is probably using your physical microphone directly, or CONNECT-ON is not active. When your outgoing voice must be translated, select Connect Mic as the calling-app microphone and confirm the Connect session timer is running.
Why can I no longer hear the other participant in Unidirectional mode?
Standard Unidirectional mode translates your outgoing voice only. Keep the calling-app speaker on your normal device. Selecting Connect Speaker in this mode can route incoming audio somewhere you are not monitoring.
What should I do when How I Sound? does not detect my microphone?
Select the real headset under Available Microphones, unmute it everywhere, grant operating-system microphone access, and test another USB port. If another microphone works, the issue is with the original device or its connection rather than the virtual route.
Support
Need help? Get in touch with our Support Team for assistance. Include the calling application, operating system, selected microphone and speaker, translation direction, and the exact step that failed. A short description of the expected result and what happened instead helps the team respond more quickly.