A failed recording usually comes from browser permission, the selected input, operating-system privacy controls, or another app holding the microphone. Work through these checks in order so each test rules out one layer.
Open Settings, choose Mic Test & Crust, and press Test Microphone. The game requests access only at that moment. A Microphone ready message confirms that the browser produced a live audio stream; it does not upload or save the test. If the request never appears, check the address-bar permission icon before changing game settings.
Open the site controls beside the address bar and change Microphone to Allow, then reload the page. If the browser remembers an earlier denial, pressing Record cannot override it. Use the exact choicer-voicer.games origin because microphone permission is stored per site. Private windows and embedded browsers can apply stricter policies, so retry in a normal Chrome, Edge, Firefox, or Safari window.
Connect the headset or USB microphone before opening the setup screen, then use Refresh microphone list. For multiplayer, check the microphone selector beside every contestant because each player can carry a separate device choice. If a saved device was unplugged, the game attempts the browser default, but explicitly selecting the active input avoids operating-system routing surprises.
Confirm that the browser is allowed to use the microphone in macOS, Windows, iOS, or Android privacy settings. Then watch the system input meter while speaking. No movement at the operating-system level means the game cannot receive a signal. Raise input gain, unmute hardware controls, and disconnect unused Bluetooth devices that may have become the default input.
Use headphones so the reference clip does not feed back into the recording. Keep the microphone about a hand span from your mouth and avoid maxing out input gain; clipped audio loses the pitch and waveform detail used during judging. Speak after the countdown and keep the tab active until the take ends or you press Stop Take.
Close meeting, streaming, voice-chat, and recording tools that may hold exclusive access to the device. Then reload the game and run Mic Test & Crust again. On mobile, disconnecting and reconnecting a Bluetooth headset can refresh the audio route. If the input works in system settings but not the browser, restart the browser rather than repeatedly granting permission.
After the mic test succeeds, start a one-round Standard show with the built-in tutorial pack. Press Begin Turn, speak, and confirm that Stop Take is enabled. A completed take should advance to the five-judge reveal. This short test separates microphone problems from issues in a downloaded scene or community pack.
No. Microphone analysis and normal takes remain in the browser. A file leaves the session only when you explicitly save a completed Dub.
Browsers often hide device labels until microphone permission has been granted. Run the microphone test, return to setup, and refresh the list.
The device identifier can change after reconnecting hardware or switching hubs. Refresh the microphone list and select the active device again.
You can browse the site and packs, but recording-based Standard and Dub play require a microphone stream.