Real-time voice conversion
For a recording or a cover, file conversion lets you render and compare several takes. In a live setup, the converter has to finish each audio block quickly enough to keep the microphone stream moving. Configure a reliable local signal first, then connect it to a call, recording or streaming application.
Choose a tool for the job
See the RVC tools directory for downloads and hardware notes, including Vonovox for NVIDIA GPUs.
The AI Hub real-time guide is a useful map of the w-okada ecosystem. Consult the actual project's release for current compatibility.
Hear one clean signal first
- Connect a microphone and headphones. In the converter, select your physical microphone as the input and your headphones as the output.
- Load a known compatible inference model and its matching index if you use retrieval. A successful short file conversion is a useful reference before you test the live path.
- Start the stream and speak at a normal level. Check the input meter or make a dry recording. Reduce input gain if peaks clip before conversion.
- Verify that the headphone signal changes when conversion is toggled. If you hear the original at the same time, check for direct hardware monitoring or a second route through the operating system.
- Test for longer than a single word. Include quiet speech, a loud phrase and a short pause. Listen for cutoffs, drift or glitches under the same workload you plan to use live.
Avoid listening through speakers near an active microphone. Headphones help you identify a routing issue without feeding the output back into the input.
Send converted audio to another app
A virtual audio device provides a playback endpoint for the converter and a corresponding recording endpoint for the receiving app. Endpoint names depend on the driver. For example, a virtual cable may call its playback endpoint “Input” and its recording endpoint “Output” because the instructions use the cable's perspective.
Physical microphone → RVC converter → virtual playback endpoint
↓
matching recording endpoint → call or stream
Select the matching recording endpoint as the microphone in the receiving app and make a short test recording there. If your local monitor sounds correct but the recording does not, verify the destination input and remove any duplicate microphone source. If you monitor the converted audio, use a separate headphone output. Avoid routing your entire desktop mix or the receiving app's audio back into the converter. Applio's routing guide
Tune latency without losing stability
End-to-end delay includes device buffers, conversion, virtual routing and any processing in the destination. A processing-time figure in the converter measures only part of that path. Capture a local test of both the dry mic and the converted route if you need to measure the delay between them.
Start with the app defaults and change one setting at a time. If a game or another GPU-heavy program shares the machine, repeat the test while it is running. Keep a working preset so you can restore it before going live. Mainline real-time GUI · Applio latency controls
Troubleshoot by where the fault appears
RVC fundamentals · Troubleshooting