MicTester

Contact

One address, no form: rlaejrtn16@gmail.com. There is no contact form on this site, which means there is no field anywhere on it that collects anything about you.

Especially welcome

  • A menu path that has moved. Every app page names the article its instructions came from and the date it was read. If Discord, Zoom, Teams or OBS has renamed something, telling us which control and what it is called now is a five-minute fix at this end.
  • A number that does not reproduce. The conversion, gain and latency tables are pure arithmetic and the test suite checks every cell — so if one of them is wrong, it is wrong in an interesting way and we want to know.
  • A browser where the tool misbehaves. The browser name and version, what you expected, and what happened. If it rejected the microphone, the rejection name shown on screen is the single most useful line you can include.
  • A device the group-matching gets wrong. The headset page relies on the identifiers your browser publishes, so it can only report what it is given: if the panel finds no output paired with a headset that plainly has one, or reports no group identifier at all where another browser manages one, that is worth a report — and worth naming the browser in.

Please do not send

  • Audio recordings. We cannot debug them, and this site is built specifically so that your audio never reaches anyone.
  • Requests to add tracking, pop-ups or an account system.
  • Guest-post or link-insertion pitches. They are deleted unread.

Before you write about a microphone problem

Most mail about a broken microphone can be answered by the sender in about two minutes, and it is worth trying because you get the answer immediately instead of waiting for a reply. The three checks below split almost every case.

  1. Does the meter move at all? If it reads −∞ your device is delivering exact digital silence, which is a mute switch, a wrong device or a permission — not a level problem. If it moves but sits low, the quiet-microphone page turns the shortfall into a number in decibels.
  2. Did the browser reject the request, and with what name? The tool prints the exact rejection on screen. That single word is the most diagnostic thing about the whole situation, and the Windows 11 page lists all seven of them with what each one means.
  3. Does it work here but not in one app? Then the hardware, the operating system and the browser are all fine, and the fault is a setting inside that app. The Discord, Zoom, Teams and OBS pages each list the controls that produce silence or bad audio with working hardware.

If you have done those three and are still stuck, that is a genuinely interesting case and worth writing about — include what each of the three produced.

What happens to your email

It arrives in an ordinary mailbox and is read by a person. It is not connected to this website, not added to a list, and not passed on. Replies come when there is something useful to say, which for a sourced correction is usually quickly.

For what the site does and does not collect while you use it, see the privacy page. For where each figure comes from, the about page lists every source.