Audio & Microphone Troubleshooting

The Choicer Voicer’s Microphone Bug: Where It Comes From and What Actually Helps

If you’ve searched for help with a silent recording in The Choicer Voicer, you’ve probably landed on the same complaint over and over: live monitoring works fine, you can hear yourself while performing, and then the actual recording comes back empty. This isn’t an obscure edge case — it’s the most common issue reported against the game, and the developer has been unusually transparent about why it keeps happening.

It’s Not the Game’s Code — It’s the Engine Underneath It

The Choicer Voicer is built in Godot, an open-source game engine, and the developer has pointed to Godot’s audio handling as the actual source of the problem rather than anything specific to this game. The most consistent trigger reported is a surround-sound audio configuration — Godot has trouble reliably identifying which channel to record from once more than two channels are in play. According to the developer, this isn’t a new discovery either; it’s been a known limitation for years without dedicated attention from Godot’s own maintainers.

This Hasn’t Been Ignored — Here’s What’s Actually Been Tried

Rather than sitting on the issue, the developer has gone looking for fixes in the engine itself, with mixed results:

  • Two separate community pull requests submitted to Godot’s own GitHub repository were tested — one targeting the audio recording feature directly, another aimed at overriding how the engine detects speaker configuration.
  • The first attempt caused the Godot editor to crash outright whenever a recording effect already existed in a project, across multiple custom engine builds. Only a build for a much newer, still-unstable version of Godot avoided that specific crash — while introducing new crashes of its own when loading content packs.
  • The second attempt, tested in a simulated surround-sound environment, simply didn’t fix the underlying problem.

Where Things Stand Right Now

The most recent development is an unofficial test build, version 0.5.2-dev2, built with help from a collaborator using yet another community pull request. It’s explicitly not a full release — it’s a “please test this and tell me if it works” build, distributed alongside the regular game files.

Player feedback on it has been genuinely mixed, but leaning positive:

  • Several players with microphones that had never once recorded properly — specific USB mics and gaming headsets among them — have confirmed the test build fixed it for them.
  • Others have tried it and still see no change.
  • One consistent quirk: leaving the audio input on its default setting seems to work better than manually selecting a specific device. At least one player found that switching to a named microphone and back to default caused the fix to stop working.
  • The Linux version of the test build had its own separate hiccup early on — an incorrect export template — which has since been corrected. If your only attempt was on Linux before that fix went out, it’s worth trying the current file again.

A Troubleshooting Order That Actually Makes Sense

  1. Test before you’re relying on it. The free “No Gameplay Demo” exists specifically so you can confirm a working mic before buying, streaming, or starting a group session — use it that way rather than discovering a problem mid-round.
  2. Try the 0.5.2-dev2 test build if your standard install is affected. It’s unofficial, but the reported success rate makes it worth the download.
  3. Leave your input device on default rather than manually picking a specific microphone, based on what’s actually worked for other players with the test build.
  4. If recordings exist but play back silent — a separate symptom from the mic not recording at all — a corrupted save configuration has been the cause in at least one confirmed case. Deleting the game’s save.json file resets your settings (not your installed packs) and has resolved this specific issue for at least one player.
  5. On Linux, confirm the game file actually has execute permissions before assuming something’s broken — one player needed to run a permissions command in a terminal just to get the game launching in the first place.

If You’ve Tried Everything and It Still Won’t Work

The developer hasn’t hidden the fact that this may not be something they can fully solve alone — it’s an engine-level issue, and Godot’s own team isn’t currently treating it as a priority. Their actual ask to affected players is somewhat unusual: contact the Godot Foundation directly and let them know this bug is blocking you from playing Godot-made games. The reasoning is that pressure from a wider group of affected players is more likely to move the needle than anything achievable from inside a single indie game’s codebase.

Set Expectations Before You Buy, Not After

Because this bug can make the game effectively unplayable for anyone it affects, the store page carries an explicit warning about it, and testing the free demo first is the recommended way to avoid an unpleasant surprise. If you already own the game and are running into this, working through the test build and the steps above is a far better first move than assuming it simply won’t work on your setup.