Virtual microphone

A virtual microphone routes synthesized translated speech from CrossMeet into a meeting app. This Pro / Team feature requires a working TTS engine and correctly configured audio devices.

1. Understand the route

Reply text → translation and review → TTS
                                      ↓
                         Virtual device playback end
                                      ↓
                      Meeting app selects recording end
                                      ↓
                          Remote party hears translation

Virtual audio devices have two endpoints with easily confused names. For VB-Cable:

Location	Typical selection
CrossMeet virtual-microphone output	CABLE Input: playback endpoint
Meeting app microphone input	CABLE Output: recording endpoint

Confirm the actual device names listed by your system and avoid selecting a similarly named endpoint by mistake.

2. Prepare the driver

CrossMeet provides a guided VB-Cable installation flow. Follow its download and installer prompts, then complete installation inside the driver installer. Closing the installer alone does not install the driver.

Administrator permission or a Windows restart may be required. The driver is third-party software; it is not described as a CrossMeet-built driver or as having a particular certificate type.

If installation fails, review the app's message or use its official vendor link. Do not bypass the problem by disabling system protection.

3. Configure CrossMeet

1. Select the virtual-microphone output device in audio settings.
2. Bind a working TTS engine and a voice compatible with the target language.
3. In the meeting or interpretation workflow, confirm that the outgoing content is your reply.
4. Test a short, non-sensitive sentence through translation and speech output.

If multiple virtual devices are detected, select the correct endpoint manually. Do not use the virtual recording endpoint as the physical microphone for recognition.

4. Configure the meeting app

In the meeting app's audio settings, choose the virtual device's recording endpoint as its microphone. Use the app's test or playback function before a real call.

Menus and audio processing in Zoom, Teams, Discord and other apps change across versions. Adjust noise suppression or automatic gain only after testing your setup; there is no universal switch combination.

5. Review before sending

Interpretation replies can be inspected and edited before sending. Quick phrases also enter the reply field first rather than immediately broadcasting.

Automatic speech is constrained by the active sources and output routes. System-audio capture can create loops, and sending the other person's words back to them is usually inappropriate. Follow the app's disabled-state explanations rather than bypassing route protection.

6. Common problems

The meeting app receives no sound

Check TTS success, CrossMeet output, meeting-app input, microphone permission and mute state. Test one stage at a time.

The remote party hears echoes or repeats

Check whether synthesized output is being captured again. Avoid loops between physical microphones, system audio and virtual endpoints. Headphones do not prevent internal system-audio recapture.

I cannot hear it locally

Virtual microphone output and local playback are different routes. Check the selected mode and device before concluding that TTS failed.

The device is missing after installation

Restart Windows if the installer requests it, then refresh the device list. If it is still missing, note the system version and error and contact support@crossmeet.com.

See engine setup and troubleshooting for further checks.