GamingMap the signal path
Write the path from voice to Discord: microphone, cable or wireless link, interface if present, computer, operating-system input, then Discord. A USB microphone is usually its own input. An XLR microphone needs an interface or mixer, and Discord selects that device rather than the microphone model.
Disconnect unused inputs during the first test. Use headphones so speaker playback cannot feed the microphone.
- Connect directly to a known-good port.
- For XLR, set interface gain and any required phantom power according to the hardware manuals.
- Clear hardware mute switches.
Prove the operating-system input
On Windows, open Settings, System, Sound, Input, select the microphone, run Start test, then play the sample. On macOS, open System Settings, Sound, Input, select the device, and watch its input meter. Allow Discord microphone access in privacy settings.
If the device is absent or the meter is flat, Discord settings cannot repair it. Check the cable, port, interface, power, mute, and permission first.
Select and test inside Discord
Open User Settings, Voice & Video, choose the proven device under Input Device, set Input Volume, and use Mic Test. Selecting the device by name is clearer than relying on Default during diagnosis.
If the system test works and Discord does not, recheck the Discord selection and permission, then restart Discord after changing permission or reconnecting hardware.
- Speak from your normal gaming position.
- Test a normal sentence and a quiet sentence.
- Join a private call after Mic Test succeeds.
Choose an input mode
Voice Activity opens when speech crosses its sensitivity threshold. Start with automatic sensitivity. If words disappear, try a slightly more permissive manual threshold. If keys or room noise open the mic, raise it or use Push to Talk.
Push to Talk gives explicit control but can clip the first word when pressed late. Test the key while the game has focus and avoid a bind that conflicts with gameplay.
Tune processing last
Suppression, echo cancellation, and automatic gain can help, but they can also make a weak signal pulse or sound thin. Establish stable level and placement first, then change one control at a time and repeat the same phrase.
If distortion appears in both the system recording and Discord, reduce gain earlier in the path. If only Discord sounds altered, compare its processing settings.
Read the result
If neither layer sees the device, follow the Windows or Mac detection guide. If the system works and Discord fails, focus on Discord selection, permission, mode, and processing. If both work but one channel fails, inspect channel permissions and mute state.
Discord documents a specific macOS voice-service limitation for some USB audio interfaces accepting XLR microphone input. Keep that boundary exact: it does not establish a general macOS, USB-microphone, or interface incompatibility.
Save the working device name, input mode, sensitivity choice, and hardware gain position. Defaults can change after reconnecting a headset, docking a laptop, or installing routing software. A short baseline note makes later troubleshooting a comparison instead of a fresh setup.
For the final check, speak softly, normally, and loudly; pause in silence; type briefly; and play game audio through your normal headphones. Success means the whole sentence survives, silence does not hold the channel open unexpectedly, and loud speech remains intelligible. Failure in only one part identifies the next setting to adjust.
Do not optimize from Discord's moving meter alone. Listen to the Mic Test playback, because a meter can move for keyboard noise, electrical hum, or the wrong microphone. Then have one person confirm the live call. Those three observations answer different questions: detection, local Discord processing, and actual call delivery.