The Choicer Voicer 0.5.2-dev2 Mic Test Build
Compare stable Choicer Voicer 0.5.1 with experimental 0.5.2-dev2, protect packs, repeat the same microphone test, and record useful results.
The Choicer Voicer 0.5.2-dev2 is an experimental build published to test a possible microphone bug fix. It is numerically newer than 0.5.1, but the official labels serve different purposes: 0.5.1 is the stable release, while 0.5.2-dev2 is for controlled comparison.
Which version should you use?
Use stable 0.5.1 for a normal first installation, custom-pack library, or party session. Try 0.5.2-dev2 when the official demo or stable build shows the reported recording problem and you are prepared to preserve the old folder.
| Version | Intended use | Main caution |
|---|---|---|
| 0.5.1 | Normal play and stable baseline | May still show the known mic issue on affected setups |
| 0.5.2-dev2 | Testing the possible mic change | Development build can include unfinished behavior |
Do not call the development file a stable “latest release” merely because its number is higher. The developer’s own post asks players to test a possible fix, which means results across devices are part of the purpose.
Protect the stable folder and custom content
Keep each version in a separate directory. Back up voice, dub, contestant, judge, studio, and chatter packs before testing. Do not point both builds at a modified content folder until the basic recording comparison is complete.
- Launch 0.5.1 with default content and note the exact result.
- Write down the operating system, microphone, output device, and channel layout.
- Close the stable build.
- Extract 0.5.2-dev2 into a separate folder from the official itch.io download.
- Select the same input and output and repeat the same short phrase.
- Compare actual recorded playback, not only a live meter.
- Return to 0.5.1 for normal play unless a newer stable version is published.
This side-by-side setup is reversible. Replacing files inside the stable folder makes it difficult to reproduce either state and risks mixing configuration or content changes with the microphone change.
Make the comparison useful
A result such as “the new version works” is encouraging but incomplete. Record whether the input meter moved, whether the saved take contained audio, whether playback used the expected device, and whether a stereo or multi-channel output was active.
If 0.5.2-dev2 succeeds while 0.5.1 fails, repeat once after a clean restart. If both fail, simplify the route: one microphone, stereo output, no virtual mixer, no voice changer, and no broadcast software. If both succeed but a party setup fails, reintroduce its extra software one layer at a time.
Avoid mixing pack problems with version tests
Use default content for the first comparison. A custom pack can have missing media or incompatible metadata that produces silence unrelated to microphone capture. After the default test succeeds, add one known-good voice pack to each version and repeat.
The same principle applies to Dub Mode. Smooth video playback, microphone capture, and timing are separate checks. Do not use a complex dub pack as the only evidence for a core microphone change.
Where to get the test build
Use the file linked from YeahMaybe’s official itch.io page and read the accompanying devlog. Do not download a repack that removes the “dev” label or promises a universal fix. A future stable release may supersede this page, so check the live listing before choosing a build.