Start with input detection before diagnosing recordings.
This guide is for a microphone that does not appear, shows no usable input, or freezes the game while you select or change an input device. It is different from a recording that saves silently or a recording that cannot be heard on playback.
Use the official investigation as context, not diagnosis.
The developer's Aug 3, 2026 Q&A says the unresolved recording issue may often involve surround or multichannel setups and describes unsuccessful engine-level experiments. It does not prove that a selected microphone, a freeze, or a crash on this machine has one confirmed cause.
Keep one direct device path
Document the game version and device action, restart after a selector freeze, then reproduce the result with one direct microphone in the Demo before adding routing changes.
Read the official Q&A
Use the developer's dated wording when you report the symptom; do not promise that a surround, driver, or virtual-device change will fix every setup.
- 01
Record the game version and the exact device action
Before changing settings, write down the game version, operating system, selected microphone, and whether the freeze happens while opening, selecting, or changing the input list. This keeps a later report reproducible.
- 02
Confirm the microphone works in the operating system
Check that the intended device is connected, enabled, and responds outside the game before changing any Pack folder or game file.
- 03
Choose the same input inside the game
Select the intended microphone in the game options. If the selector freezes, stop switching devices, close the game, and restart before treating the next result as a clean test.
- 04
Run the No Gameplay Demo with one direct device path
Use the Demo to check whether the game detects the same input without Pack changes, calls, streaming capture, or extra audio routing.
- 05
Remove added routing variables
Temporarily avoid virtual devices, surround processing, Discord/OBS capture, USB adapters, and multiple microphones. Record what you disconnect so it can be restored later.
- 06
Classify the next symptom accurately
If the mic becomes visible but a saved take is empty, use the recording-silence guide. If a take exists but cannot be heard, use the playback-silence guide.
Ready for a first round
- The game version, device, and action that caused any freeze were recorded.
- The intended microphone works outside Choicer Voicer.
- The same device is selected in game after a restart.
- The No Gameplay Demo was tested without Pack changes.
- Virtual routing, extra adapters, and additional microphones were removed for the baseline.
- The next guide was chosen from the observed symptom.
Quick answers
Input-detection answers
Use this page only while the game cannot detect an intended microphone.
Next step
Once input is visible, test what happens to the saved take.
A microphone appearing in the game is only the first checkpoint. Use the symptom that matches the saved recording rather than stacking new changes on top of the input test.