Mic Room Diagnostics — 3-Step Recording Quality Check
Mic & Practice Recording Check is a browser-based vocal practice setup checker built for home singers and podcasters. It runs three quick diagnostic checks — background noise, space ring, and a voice setup check covering input level, plosive pop noise, and clipping — then shows a report with a readiness score and a prioritised list of improvements. All analysis runs locally in your browser; no audio is sent to any server.
Why your recordings sound bad even with a decent mic
Most practice recording problems — muddy tone, distant vocals, breath pops, or ugly distortion — come from setup and room behavior more than the mic itself. Bare walls create ring, HVAC adds hiss, and poor gain staging makes your voice either weak or clipped. This tool helps you catch those problems quickly so you can move the mic, change gain, or soften the room before you start singing.
What the three diagnostic checks measure
Step 1 captures a 5-second averaged noise floor and looks for likely low-frequency hum or broadband room noise. Step 2 listens to a single handclap and gives a quick estimate of how ringy the space feels for practice vocals. Step 3 checks whether your voice is coming in too quietly, whether consonants create strong low-end bursts, and whether loud lines clip. When all three finish, the report combines those results into a practical readiness score and a short fix list — it does not run a separate measurement.
How to use the results to improve your vocal recordings
A poor noise result points to a quieter room, less fan noise, or better cable routing. A ringy space check means you should add blankets, curtains, or move farther from bare walls. A low input result means you should move closer or raise gain slightly. Plosive warnings tell you to add a pop filter or angle the mic slightly off-axis. Clipping means your preamp gain is too high — pull it back and try again.
What this page is good at — and what it is not
This page is strong when you want a fast practical answer using the gear you already have: phone, laptop, USB mic, or interface mic. Its advantage is convenience and speed. Its limitation is that browser audio is not a calibrated measurement environment, so results should be treated as guidance for your current setup, not as lab-grade room acoustics data.
Tracking your recording environment over time
Every completed run is saved to the browser's local storage and shown in the history table on the start screen and in the report. Use it to compare scores before and after you move the mic, change rooms, add soft materials, or switch devices.
Mic & Practice Recording Check
A quick browser-based self-check for vocal practice recording. It helps you spot noise, space ring, gain issues, plosives, and clipping in under a minute.
All analysis runs locally in your browser. No audio is sent to any server.
Fast and convenient, but not a calibrated acoustic measurement. Use the results as practical guidance for your current device and room.
How to run the diagnostics
Allow microphone access when the browser asks, then run the three diagnostic checks in order and review the report at the end. The page is designed to give a quick practical answer using your current device, not a professional acoustic report.
Step 1 — Background noise (5 seconds)
- Stay completely silent. Don't speak, move, or touch the desk.
- The tool averages RMS energy and looks for likely hum or broadband room noise patterns.
- Pass threshold is −45 dBFS. Quieter is better for vocal recording.
- If you fail, try turning off AC units, moving away from the PC, or tidying up your cable/power routing.
Step 2 — Space ring check
- Press Start, then clap once loudly near the microphone.
- The result is a quick browser estimate of how ringy the room feels for practice vocals.
- Use it as a practical guide to compare rooms or mic positions, not as a calibrated acoustic reading.
- If the space feels too live, try blankets, curtains, carpets, or a smaller softer area.
Step 3 — Voice setup check
- Say "Pa Pi Pu Pe Po" loudly into the mic during the 5-second window.
- The tool checks whether your voice is too quiet, whether low-frequency bursts suggest plosives, and whether loud syllables clip.
- Clipping is flagged when any sample exceeds 0.98 full scale (−0.2 dBFS).
- Fix low input by moving closer or raising gain slightly. Fix plosives with a pop filter. Fix clipping by reducing gain.
Reading the report
- The overall score (0–100) estimates how ready your current setup is for practice recording.
- The report highlights the next things to fix instead of pretending to be a lab-grade acoustic analysis.
- Use-case bars show how usable the setup is for different recording goals.
- The frequency snapshot is relative only and is not a calibrated frequency response graph.
- Export the radar as PNG or the full report as a text file if you want to compare before and after changes.
Input device selection
- Use the device picker in the Pitch Controls strip (mixer icon) to select a specific input device before starting the diagnostic.
- The chosen device is stored in browser local storage and automatically used when you press Start.
- If you have multiple interfaces connected, always confirm the correct one is selected to avoid measuring the wrong signal chain.
History and repeated measurements
- Up to 10 previous runs are saved automatically and shown on the start screen and in the report.
- Delete individual entries with the × button or clear everything with Clear All.
- History is stored in browser local storage and is not shared across devices or browsers.
Home-recording setup tips
- Run the check in the room and at the time of day you actually plan to record — HVAC, traffic, and nearby appliances change the noise floor more than most people expect.
- If Step 2 flags a ringy room, try facing a different wall or adding a blanket or thick curtain behind the mic before buying acoustic panels.
- Re-run the check after any change — new mic position, pop filter, or furniture — so you can tell whether it actually helped or just felt different.
How the score and the use-case bars are built
The overall score starts at 100 and loses points for specific, independent problems: a noise floor worse than −45 dBFS, 60 Hz hum or fan noise above threshold, a ring that measured reliably but decays slowly, input that is too quiet, a plosive blast, or clipping. Each problem is checked and penalized on its own, which is why a quiet room with the gain set too low still scores badly — a good Step 1 does not buy back a bad Step 3.
Step 2's ring time is estimated the way acousticians estimate RT60: find how long the clap's level takes to fall from −5 dB to −25 dB after its peak, then multiply that span by three to project the time to a full 60 dB of decay. If the handclap trails off too gradually to find both of those points, the page falls back to a straight-line estimate from the clap's peak to its last measured point instead.
The four use-case bars (video call, streaming, podcast, singing) run that same three-step data through four different penalty tables, not just the single overall score split four ways. Singing is the strictest: it starts losing points at a shorter ring time, weighs a quiet noise floor and clipping more heavily, and has no tolerance built in for the casual noise a video call shrugs off.
Questions
What do the three checks measure?
Step 1 is about five seconds of the room with you quiet. That average is the noise floor. Step 2 is the tail after a handclap. Step 3 is your speaking or singing level: too low, clipping, or a plosive blast.
Why a clap, not a scale?
A clap is short and then gone, so the sound that continues is the room. A sung note keeps producing sound, and the page cannot split that from the reflection.
Does a higher score mean a better voice?
No. The score is noise, ring, and gain on the signal the browser is receiving. It says nothing about tone or technique. One bad step is not cancelled by two good ones. A quiet room with the gain too low still records badly.
Is this a calibrated room measurement?
No. Browser audio has no lab calibration. Use the number to compare this room, this mic, and this gain against your own earlier runs. History keeps up to 10 of those runs in local storage on this browser.
What should I change first?
If Step 1 is the problem, move away from the noise or wait until it stops. If Step 2 rings, face a different wall or put a thick curtain or blanket behind the mic before buying panels. If Step 3 clips, lower the preamp. If it is too quiet, move closer before you add much gain. Run the check again after the change. The history row is how you tell the number moved, not just that the room feels different.
Why do the four use-case bars show different numbers from the same run?
They are not the same score relabeled — each use case runs your three-step results through its own penalty table. Singing is scored strictest, so the same room and gain that reads fine for a video call can still show a lower singing bar.
Start is stuck and shows a denied-microphone message — now what?
The browser is remembering an earlier denial for this site. Open the permission icon in the address bar, switch microphone to allow, and reload before pressing Start again.