Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Choose the device before recording
Connect the intended microphone, then check the operating-system sound input and the browser’s default microphone. A site permission saying “allowed” answers whether capture is permitted; it does not establish which physical input is selected. PitchChanger’s recorder does not provide a device picker, so change selection in the browser or operating system.
Stop, select and start a fresh test
Stop the current capture before switching the default input. Return to the recorder and begin a new short take. Speak a device label and make a quiet, distinguishable sound close to the intended microphone, then repeat away from it. Do not strike the capsule or create a loud test sound. Preview the saved test with headphones.
An original two-position identification worksheet
Proposed test: say “USB desk microphone, take A” at a comfortable distance from that microphone. Then move toward the laptop microphone and say “laptop position, take B” at comparable speaking effort. These are instructions for your own check, not evidence that any particular device was tested here.
A stronger nearby sound is supporting evidence, not unique proof: room reflections and automatic gain can change levels. Combine the recording with the actual selected-device name. If the result remains ambiguous, disable or disconnect an unused external input when practical, then repeat. Do not disconnect hardware during an unsaved full take.
Swipe or scroll sideways to read all columns.
| Record | What to write down | Reason |
|---|---|---|
| System input | Exact device name | Avoid a generic default label |
| Browser input | Selected microphone | Browser can differ from system |
| Test A/B | Which position is clearer | Independent audible cross-check |
| Final check | Reopen saved test | Preview alone is not file verification |
Recheck after changing headsets
Bluetooth connections, USB reconnection and docking changes can alter the default device. A successful test yesterday is not proof of today’s input. Repeat the short identification test after a hardware change and before a long interview or rehearsal.
If there is silence, first confirm mute and input activity at the system level. If the browser cannot access any microphone, use the separate permission workflow. Device identity, permission and signal level are three different checks.
Common questions
Does hearing my voice prove the USB microphone was used?
No. A built-in microphone can also hear you. Check the selected device name and use a short position-based test. If you cannot identify the source confidently, resolve that ambiguity before recording the full take.