Apps still hear my raw mic
Set Zondel Output to CABLE Input. Then set the voice app's Microphone to CABLE Output.
Do not select your real microphone inside Discord, Zoom, OBS, Teams, or Slack if you want them to hear Zondel.
Fix issues
Most Zondel problems are either routing mistakes or an over-aggressive processing stage. Work through the matching card below before changing a lot of settings.
Each card starts with the fastest check first.
Set Zondel Output to CABLE Input. Then set the voice app's Microphone to CABLE Output.
Do not select your real microphone inside Discord, Zoom, OBS, Teams, or Slack if you want them to hear Zondel.
Restart Zondel once, reselect Input and Output, then check Windows Settings > Privacy & security > Microphone. Make sure microphone access and desktop app access are both enabled.
If you use speakers, enable Echo Cancel in Pro mode and set its speaker source to the device playing call audio. If you use headphones, look for a routing loop instead: the call app may be monitoring CABLE Output back into itself.
If you are using Monitor, lower its buffer first. Then disable Voice Persona and Dereverb to compare. The Latency readout shows Zondel processing only; audio drivers and the voice app can add more delay.
Use a gentler preset or reduce Noise Suppression. If Dereverb is on, try Light or Off. Run Test Mic after each change so you can hear the before-and-after clearly.
Run Calibrate again. Watch the IN meter while speaking; if it is peaking near the top, lower microphone gain or Pre-Amplifier gain before tuning anything else.
The DeepFilterNet model files may be missing. Reinstall Zondel from the same source you used originally; the models ship with the app package.
Open Settings and confirm Start with Windows is on. If Windows disabled it, open Windows Settings > Apps > Startup and turn Zondel back on there.
Turn on Settings > Start hidden, then fully quit and launch Zondel again. The next auto-start should go directly to the tray.
Go back to Simple mode and choose Voice Call, Stream, or Podcast. That reloads a known-good chain while keeping your Custom state available if you want to return to it.
Zondel writes logs under %LOCALAPPDATA%\Packages\<Zondel package>\LocalState\logs\.