Quickly test smart glasses microphone quality in 15 minutes

Time needed about 15 minutes in one session

The steps

1. Confirm firmware and appAsk to see the companion app or device settings, record the screen or have the rep state the firmware and app version aloud while you record.You should see: You have a screen recording or an audio recording where the firmware and app version are visible or spoken.
2. Enable and verify microphone permissionsOpen system and app settings on the paired phone or glasses app and confirm Microphone permissions are allowed, showing the permission toggle on camera if remote.You should see: The settings screen shows Microphone allowed or the system permissions dialog confirming mic access.
3. Position the glasses correctlyWear the glasses as you normally would, adjust for fit, and take a short video showing the fit and mic placement.You should see: A video shows the glasses sitting on your nose and temples in your usual fit with visible mic placement.
4. Select mic mode and label itIn the app select the mic mode to test (single, multi‑mic, noise suppression) and say the mode name aloud while recording so the file is labeled.You should see: The app shows the selected mic mode and the audio file contains your spoken mode label.
5. Run a live call testCall your remote listener, speak the scripted phrases in quiet and noisy setups, and ask the listener to repeat what they heard and save their recording.You should see: The remote listener supplies a verbatim repeat and a saved audio file of the call.
6. Make a local recording and playbackUse the glasses’ native recorder or your phone recorder to record the same scripts locally for 30–60 seconds, then play back the raw file through headphones.You should see: A recorded audio file appears in the recorder and plays back the sounds you just made.
7. Run the transcription / caption checkEnable live captions or the vendor transcription feature, speak the scripted phrases in quiet and noisy staging, and take screenshots or export the resulting captions.You should see: Captions or a transcript appear and match the scripted phrases closely, and you have screenshots or an exported transcript saved.
8. Perform AI and multi‑mic checksDo beamforming and source separation tests by recording target-on-axis and off-axis takes with a second noise source, and label each take.You should see: Recorded files show reduced off-axis noise when the target is centered if beamforming works, or distinct voices if source separation is present.
9. Save, label and upload evidenceRename each recording with device, mode and environment, upload them to a cloud folder you control, and note links for follow-up with support.You should see: A clearly named set of raw audio and transcript files exists in your storage with timestamps and mode labels.

How to test smart glasses microphone quality

Run three focused checks in one session: a live call to a remote listener, a local recording and playback, and a transcription/caption check. Do each check in quiet and in noisy staging, save the raw files and a short video showing mic placement, and label the mic mode and fit for every take.

A 10–15 minute pre-demo checklist you must run first

Verify five items before any audio test so results are meaningful: firmware and app version, microphone permissions, correct device positioning, battery or charger, and the mic mode you will test. Check them in that order and record the screens or have the rep state versions aloud so you can prove the demo configuration later.

• Firmware and app: show the app’s About or Settings screen with the version.
• Microphone permissions: confirm system and app mic access is allowed.
• Positioning: wear the glasses the way you normally would and show fit on video.
• Battery: plug in or confirm adequate charge to avoid power‑save noise.
• Mic mode: select single, multi‑mic or noise suppression and label which you test.

Run the three quick tests: live call, local recording, transcription

Do the tests in this order: live call to reveal routing and perceived clarity; local recording to capture raw mic input; and transcription to evaluate captions and AI features. Run each test in quiet first for a baseline, then repeat with staged noise. Save every audio file and note mic mode and placement for each take.

Store-friendly live call test (step-by-step)

Make a call using the demo device and a cooperative remote listener, run scripted lines in quiet and noisy setups, and have the listener record the call and repeat what they heard verbatim. Confirm on camera that the call is using the glasses’ mic; if it isn’t, stop and fix routing before you continue.

• Script, clarity: “Testing voice clarity. This is Sam, one, two, three. The red fox jumps over the lazy dog.”
• Script, sibilance: “Sally sells seashells by the seashore.”
• Script, distance: “I am standing two metres behind you and speaking softly.”
• Noisy staging: one person murmurs nearby while another speaks loudly from a different angle.

Remote-trial live call and recording when you don’t have the device

Ask the vendor to join a video call using the demo device, show mic selection on camera, toggle modes while recording, and then send the raw audio files plus a short timestamped video of the person wearing the glasses. If they will not supply native audio exports, treat the trial as inconclusive and insist on a different arrangement.

• If they only send a meeting app recording, request the native export from the glasses app or the phone that proves the glasses’ mic was used.
• If the vendor provides a demo link for captions, have them run the transcription test live while you watch.

Test scripts and environments that reveal weaknesses

Use four simple environments—quiet room, café-style chatter, wind/outdoor, and two-speaker overlap—and three scripted phrase types: clarity, sibilance and distance. These setups expose routing errors, harsh high-frequency processing, aggressive suppression and failure to separate simultaneous speakers.

• Clarity: “This is Sam testing voice clarity; please repeat.” — expect exact repetition from the listener.
• Sibilance: “Sally sells seashells by the seashore.” — listen for harsh S sounds or hiss.
• Distance: “I am two metres away and speaking softly.” — expect intelligible words, not a muffled blob.
• Two-speaker: two people 1.5 metres apart speak different short phrases at once; check if sources separate.

How to test AI and multi‑mic features specifically

For beamforming and voice isolation, record the target speaker centered and again off-axis while a background source runs. For wake-word and transcription, time the device’s response and save captions. Compare recorded files to see whether on-axis speech is prioritized and whether background chatter is reduced without erasing consonants.

• Beamforming: record 0° target then 90° target while a noise source sits at 45°.
• Voice isolation: play consistent café noise and speak scripted lines; compare subjective SNR and listen for missing consonants.
• Wake-word: say the wake word and note the device’s visual or audible acknowledgement and any caption response.
• Source separation: have two people overlap short sentences and check whether the system outputs distinct sources or a single mixed transcript.

How to record, save and present your evidence

Use the glasses’ native recorder when available plus a secondary recorder (your phone or the remote listener). Rename each file with device, mic mode, environment and timestamp, store them in a folder you control, and keep the raw exports. Waveform views in a simple audio editor help spot sudden dips or compression that indicate aggressive suppression.

• Tools: phone voice recorder, vendor app export, and a quick meeting app record as backup.
• Label example: rayban-demo_mode-noiseisol_quiet_2026-10-13-14-05.wav
• Keep raw files — transcoded files from the salesperson’s system are not reliable evidence.

Why demos fail in practice and the sequence you should expect

Demo failures usually follow a pattern: the call routes to the phone or headset, the device is in power‑save or low battery, an app setting reroutes audio, or AI suppression misclassifies speech as noise. Catch these by following the pre-demo checklist and by comparing remote listener recordings with your local raw files.

• If the remote listener reports a different tone than your recording, the call likely used the phone mic.
• If consonants or sibilance are missing across recordings, the device is applying aggressive suppression.
• If the device drops audio, check battery, interference and power‑save settings before ruling the hardware out.

What to ask the salesperson and what to do if the device fails

Ask to see firmware and app versions, the export path for raw audio, mic mode controls and the vendor’s trial and return terms. If a unit fails a single test, request a different demo device, a loaner period, or a firmware verification from the vendor; do not accept only verbal assurances.

• Read aloud: “Can I see the firmware and app version?” and “Can you export the raw audio file from the glasses?”
• If the vendor refuses raw exports, insist on a materially different demo device or walk away.

Next step you should take right now

Run the three-test checklist on the demo unit, record each take, label files and compare them to the pass/fail notes in this guide. If any test fails, insist on a different demo device or a loaner period and use your recordings to show the issue. After the demo, check app compatibility on /apps and caption behaviour on /uses/live-captions.

Where this usually goes wrong

• Remote listener reports a different tone than your local recordingThe call routed to the phone’s mic or a paired headset instead of the glasses’ mic.Stop testing, show the app's active audio source on camera, and force the call to use the glasses’ mic in the app or phone call settings.
• Playback files sound overly smooth with missing consonantsOver‑aggressive noise suppression or an AI filter misclassifying consonants as noise.Switch to a less aggressive mic mode, retest and document the difference; ask the vendor whether suppression settings are adjustable.
• Sibilance is extremely harsh or clipped across samplesMic capsule design or a high‑frequency boost in the processing chain.Request a different demo unit or model to compare; if the issue persists, rule the device out for voice‑heavy use.
• Audio drops out intermittently during a callLow battery, wireless interference, or power‑saving throttling on the demo unit.Plug the device in, move to a different location to check interference, and retest; if dropouts continue, ask for a replacement unit.

The checklist

• Confirm firmware and app
• Enable and verify microphone permissions
• Position the glasses correctly
• Select mic mode and label it
• Run a live call test
• Make a local recording and playback
• Run the transcription / caption check
• Perform AI and multi‑mic checks
• Save, label and upload evidence

Frequently asked questions