Troubleshooting
Troubleshooting
Plugin missing in the DAW, the vocal sounds late, correction jumps to the wrong note, crackles or high CPU.
CX TUNE does not show up in my DAW
- Check that the whole
CX TUNE.vst3folder is inC:\Program Files\Common Files\VST3\. - Check that your DAW scans that folder, then rescan. In FL Studio: Options → Manage plugins → Find plugins.
- CX TUNE is 64-bit only. A 32-bit DAW or bridge cannot load it.
The vocal sounds late
In Standard mode CX TUNE needs 35.8 ms at 48 kHz to analyse the voice. It reports this to the DAW, which delays everything else to match. If the vocal is late, make sure plugin delay compensation is switched on in your DAW.
When you sing through the plugin while recording, switch Latency to Low Latency. CX TUNE then adds only 20 samples (0.45 ms at 44.1 kHz); a corrected note can arrive up to one pitch period later, a few milliseconds. Your audio interface’s buffer adds its own delay on top, so keep the buffer small while recording. Switch back to Standard for mixing: it keeps the voice’s formants exactly.
It corrects to the wrong note
- Set Key and Scale to match the song. With the wrong scale, CX TUNE pulls notes to the nearest allowed note, which may not be the one you sang towards.
- CX TUNE follows one voice at a time. Doubled vocals, harmonies, heavy reverb or a lot of background music in the same track confuse any monophonic tuner. Tune the dry lead vocal before effects.
- It tracks voices between about 65 Hz and 1050 Hz and corrects by up to about three semitones. Lower notes pass through unchanged.
Crackles or high CPU
- Raise your audio buffer size in the DAW’s audio settings.
- Use a proper audio interface driver (ASIO in FL Studio).
- Freeze or render the tuned vocal once you are happy with it.
Still stuck?
Contact support with your Windows version, DAW and its version, and the CX TUNE version. A short audio clip of the problem helps a lot.
Updated 10 November 2026