🎤 SEM Mic Array Setup Sheet

For event organizers running electronic judging on tuninglabs.net · v1.1 · 2026-05-19
← Back to Mic Array

1Before the event — desk prep

Do this before you leave for the venue. 15–20 min the day prior.

The sparkline next to each curve previews its shape. Verify the curve you picked looks right before you save.

2At the event — hardware setup

Bring: laptop, USB mic array (or interface + matched mics), tape measure, contestant roster.

Detect requires microphone permission in the browser. If you previously denied it, click the lock icon in the URL bar → Site settings → allow Microphone → reload.

3Build the array template

One array template per rig. You can clone it later if your rig changes.

4Per-contestant — place each mic + measure

When a contestant's car is in the judging bay, do this for each entry.

How many mics? 4–8 mics is the sweet spot for SEM judging. The Geddes-style 6-point ear-ellipsoid is the academy-cited baseline. 1–3 mics is acceptable for quick checks but reduces spatial confidence. Above 8 mics gives diminishing returns inside a typical cabin.
Position labels live on the measurement, not the array template. They're editable per use because car geometry changes contestant-to-contestant.

4.5🌬️ Ambient noise capture (5 seconds, optional)

Captures the room's sonic signature so it can be subtracted from the actual test. Skip in a quiet room; use when there's crowd noise, HVAC, or other systems playing nearby.

How the math works: power-domain spectral subtraction. If the room has a –40 dB hum at 100 Hz and the contestant plays at –10 dB at 100 Hz, the score uses ~–10.04 dB (the hum is mathematically removed without distorting the contestant's signal). Loud bands stay loud; only the noise floor moves.

5Live capture + score

90 seconds. Platform handles the averaging.

Scoring formula: 100 − (MAD × 5), clamped 0–100. 0 dB MAD = 100. 10 dB MAD = 50. Target precedence: per-contestant override → event default → IASCA flat fallback.

ℹ️Why the platform uses RMS / power averaging

We use power averaging because equal-weight dB averaging underweights peaks and overweights nulls (logarithmic bias) — a 6 dB null between two mics would look like a real cabin null when it's just placement spread. Power averaging is what REW, Dirac Live, Audyssey, and Trinnov all use under the hood. It's the AES TC-AA standard for multi-position spatial averaging and what Floyd Toole and Sean Olive endorse in the Harman research.

For 8 or more mics, the platform automatically upgrades to coherence-weighted RMS averaging — the per-band, confidence-weighted version Smaart uses. Below 8 mics we stay on plain RMS / power averaging because the statistics get thin and the weights become unreliable. Either way, a single-mic capture degenerates cleanly to just that mic's response — no special case.

6Re-measure / dispute resolution

📚Quick reference — library presets

PresetUse caseNotes
Harman in-carSQ tonality judgingOlive/Welti research target. Bass shelf, gentle treble roll-off.
B&K 1974Classic room referenceStrong bass tilt, gentle treble roll-off.
IASCA RTA flatIASCA RTA/SPL ChallengeFlat across 31 bands. Variance from flat = penalty.
MECA RTA flatMECA RTA Freq OutFlat across 31 bands. Same scoring pattern as IASCA.
Audiofrog / WehmeyerPro install / tuning judgingHarman variant with slight midbass emphasis.
Dolby X-CurveCinema-styleSMPTE/ISO 2969. Flat to 2 kHz, –3 dB/octave roll-off above.

⚠️Troubleshooting

SymptomFix
Detect button does nothingBrowser blocked mic permission. Click the URL-bar lock icon → allow Microphone → reload.
Mic shows up with no namePermission granted, but browser didn't expose the label. Safari does this — switch to Chrome or Edge.
Same mic appears twiceIt won't — upsert is keyed on device ID. If two rows exist, they're truly two different USB devices.
Auto-fill from connected drops micsMax 16 slots per array. Excess detected mics are skipped.
Score shows "no measurement"You saved the placement but haven't pasted the band data yet. Click Save Measurement & Score on the placement editor.
Target source says "fallback flat"No event-level "all" curve set and no per-contestant override. Go back to Step 1 and set an event curve.
Score lower than expectedClick "Show per-band detail" — large red Δ values point to the bands hurting the score. Often a level offset between measurement and target (system is louder/quieter than the target curve expects).
Score shows a yellow ⚠ outlier warning — one of my mics flaggedOne mic's response deviates >6 dB from the median in >20% of bands. Check that mic for: (1) covered/blocked port, (2) loose connection, (3) sitting near a panel rattle. Re-position and re-capture, or accept the flag — the platform does not auto-drop outliers (auto-drop is indefensible at a judged event).
Score got worse when I added more micsProbably picking up crowd / HVAC noise via the additional positions. Run the Ambient Capture (Step 4.5) before the next attempt so the room signature is subtracted out. Also check the outlier-flag warning — one of the new mics may be sitting on a panel rattle.
Cross-position variance is very high (>4 dB avg)System sounds very different at different mic positions. For tuning: this points to imaging / staging weakness — work on time alignment, level matching, and seat-to-seat balance. For judging: it's a real characteristic of the install — don't "fix" it by removing mic positions. The spread is the truth.