One Microphone or Two Is a System Decision

Microphone count changes acoustics, PCB, enclosure, DSP assumptions and factory test.

The first engineering constraint behind One Microphone or Two Is a System Decision was concrete: LOUP asked the manufacturer to recommend one versus two microphones with BOM, PCB, enclosure and test impact rather than choosing by component count alone.

A second microphone can enable spatial processing or redundancy, but it also adds routing, matching, openings, calibration and validation. If the firmware only needs one clean speech channel, extra hardware may create more integration work than value.

I kept the experiment narrow by changing one variable, capturing the observable result, and comparing it with a preserved working build before moving on. Evidence marker: one-vs-two-mics.

Component count should follow a verified signal-processing requirement and a manufacturable acoustic design. In practice that keeps the next LOUP change measurable because the baseline remains available for comparison.

Project evidence

LOUP engineering marker: one-vs-two-mics. This note records the design or debugging lesson without publishing device credentials, private keys, customer data or manufacturing secrets.