The short answer
Discord describes 1003 as a substantial microphone input-rate mismatch. Rejoin first. If it persists, record input A/output B, compare input C with B, restore A+B, then compare A with output D. If no alternative devices exist, record that limit and compare a local recording and browser call without assuming these prove hardware compatibility.
Different symptom or still not fixed? Find the next check →Key facts
- Verify the actual error
- Record which participant’s device shows 1003
- One variable at a time
- A+B → C+B → A+B → A+D
- No spare hardware
- Check built-in devices, then record what remains untested
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| 1003 not confirmed; someone reports distorted speech | Check the screen and who hears the distortion. | Step 1 |
| Baseline input A/output B shows 1003 | Rejoin with that unchanged combination first. | Step 2 |
| Input C/output B improves | Investigate the original input or combination; do not declare it broken. | Step 2 |
| Input A/output D comparison | Restore A+B before changing output only. | Step 2 |
| No alternative mic/output device | Inspect built-in options, then recording/browser comparisons. | Step 3 |
| 1003 persists or clears while distortion remains | Record code and audio separately and choose the next check. | Step 4 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1｜Confirm 1003 and who hears the distorted audio
The official input-rate description does not mean every robotic voice has this cause.
Time: Compare one change at a time
- Record the code, full message and time. Distinguish a code on your screen from one reported by another participant.
- Determine whether they hear your voice distorted or you hear theirs distorted. If possible, ask another willing listener for comparison.
- For 1003 on your device, continue to Step 2. For an error concerning the other person’s input, let them use these checks on their own setup.
- Without a confirmed 1003, follow the voice-cutting-out guide for clipped/intermittent speech, or Bluetooth audio checks for muffling that starts when a call begins.
Results that did not fix the problem help the next reader too.
Step 2｜Change input and output separately, returning to the baseline
This orders Discord’s device/rejoin suggestions so you can identify what changed.
Time: Compare one change at a time
- In User Settings → Voice & Video, record the exact input A and output B. Select their names during the comparison rather than relying on Default.
- First leave/rejoin using A+B and repeat the same phrase. If that clears both the code and distortion, keep the devices and check for recurrence.
- If it persists and an alternative exists, change input only to C while keeping output B. For example, use a built-in mic with the original headphones. Rejoin and record code plus speech quality.
- Restore input A and confirm output B, then change only output to D and repeat. Moving directly to C+D would obscure which change helped.
- If only C+B helps, prioritize the original input/combination. If only A+D helps, inspect the output-including combination. Even if both help, do not conclude that the original headset is faulty from this alone.
- Rejoin once more with the working combination and ask the same listener to confirm. If 1003 clears but distortion remains, continue to Step 4 instead of calling it resolved.
Lower volume before changing output. Speakers can feed back into the mic; stop if echo occurs. The A/B/C/D examples describe a comparison, not measured results.
Results that did not fix the problem help the next reader too.
Step 3｜Without spares, compare available built-in devices, recording and browser
These observations can help support; they do not replace a test with an alternative device.
Time: Compare one change at a time
- Inspect Settings → System → Sound for a usable built-in mic, monitor output or built-in speakers. Use an available option as C or D in Step 2, keeping volume modest.
- If no alternatives exist, mark that comparison unperformed. Fully quit/reopen Discord, select the original devices by name and recheck the call.
- Make a brief private recording with the same mic in Windows Sound Recorder, or Voice Recorder on Windows 10. Distortion there broadens the check to input/connection/Windows; a clean recording prioritizes Discord or call conditions without proving the hardware fault-free.
- Close the recorder and desktop Discord, then compare the same call at https://discord.com/app. Align site microphone permission and the named input/output devices.
- If only the browser works, prioritize app settings/conditions. If both distort, record the shared device/connection/call conditions without declaring hardware failure.
Results that did not fix the problem help the next reader too.
Step 4｜Choose settings checks or support from the results
The phrase input rate is not a reason to impose one Windows sample-rate value on every device.
Time: Compare one change at a time
- If an alternative combination works, use it temporarily and inspect the original device’s connection, manufacturer-supported drivers and known issues.
- For browser-only success, check Discord updates and a full restart. Before trying a Voice & Video debugging-area reset, record device choices/input mode, then compare under the same conditions and restore unhelpful changes.
- If the code clears but distorted or interrupted speech remains, record that separately. Check one listener versus all listeners and continue with the voice-cutting-out guide.
- For persistent failure, give official support the device showing 1003, OS/app versions, input/output names, A+B/C+B/A+D results and recording/browser results. Mark unavailable comparisons unconfirmed.
Results that did not fix the problem help the next reader too.
Avoid
- Do not impose 48 kHz or another sample rate solely because the code mentions input rate.
- Do not buy replacement hardware or conclude it is broken from one comparison.
Important cautions
- Keep the baseline and each changed combination identifiable. Record code presence and audible distortion separately, with the rejoin time.
- Use only a harmless private test recording; redact usernames/server names from support screenshots.
FAQ
Does robot voice always mean 1003?
No. Confirm the code before applying its interpretation. Intermittent speech, Bluetooth quality changes and one-listener issues can require different checks.
Can I replace both mic and headphones at once?
It might avoid the symptom but obscures which change helped. To isolate it, change input only, restore the baseline, then change output only.
Do I need to buy a spare microphone?
No. Use built-in alternatives if available. Otherwise record rejoin/restart, local recording and browser results, and mark the device comparison untested.
Should every Windows device be set to 48 kHz?
This guide does not prescribe that. Discord’s 1003 advice concerns separate/alternative input and output devices and rejoining. Change device-specific format settings only with appropriate manufacturer guidance.
Sources
English adaptation of the Japanese guide with the same cause IDs, action sequence, cautions and source scope. Official Discord, Microsoft and relevant browser documentation support the checks. Comparison examples are editorial guidance, not measured results. Test with a willing participant, keep recordings private and restore unhelpful changes.
Discord: audio and video error codesDiscord: voice and video troubleshootingMicrosoft: set up and test a microphoneDiscord: contact supportDiscordJapanese version of this page