---
title: "Music and calls versus the CueSpec AI workflow"
description: "The hardware sheet lists dual speakers and music/call capability."
slug: "speaker-and-call-scope"
category: "hardware"
language: en
editorial_status: published
capability_status: validation
reviewed_at: 2026-10-13
keywords: ["smart glasses calls","SPECS 01 speakers","Bluetooth music"]
---

# Music and calls versus the CueSpec AI workflow

The hardware sheet lists dual speakers and music/call capability. Those supplier-described audio functions are separate from verified CueSpec transcription, wearable controls and Codex conversation delivery.

## Check each route
Audio playback tests the speaker path. A phone call tests a calling path and its processing. Recording a draft on Mac tests another host and recognition route. Success in one route should not be used as evidence that all three are ready.

For a sample, check connection, input selection and understandable audio with a non-sensitive test. Confirm the actual route used before documenting the result. Sound audible to the wearer may also be audible nearby; the reviewed materials do not establish a leakage measurement.

## AI answers are not a lens display
SPECS 01’s current facts do not establish a camera, lens display or eye-projected interface. The available task overview is on the Mac desktop. Audio hardware alone also does not establish automatic reading of every AI answer through the glasses.

A finished combination guide should specify which outputs and controls are supported and how they interact with playback or calls. Until then, keep everyday audio claims at the supplier-description level and the AI integration marked as development work.

## Related reading

- [Bluetooth connection is not the whole AI input path](/bluetooth-input-path/)
- [Microphone noise rejection versus quieter listening](/noise-rejection-vs-listening/)
- [SPECS 01 hardware specification reference](/specs-01-specification/)