Technology & Innovation

Auracast broadcast audio is beginning to appear in cinemas and other public venues. For hearing-aid brands, that is an important market signal: future users may expect to receive venue audio directly through compatible hearing devices, earbuds or headphones.

But a roadmap decision involves more than choosing a Bluetooth version or adding “Auracast ready” to a concept sheet. Compatibility depends on the transmitter, receiver, broadcast profile, assistant device, user interface, firmware and venue implementation working together.

Why public-venue deployment matters

Bluetooth SIG identifies cinemas, airports, lecture halls, conference centers and houses of worship as potential public-location uses for Auracast broadcast audio. The technology can transmit venue or public-address audio to multiple compatible receivers within range.

A recent industry report described an Auracast assistive listening rollout at Vue cinemas across the UK and Ireland. One rollout does not establish universal availability, but it illustrates the shift from product demonstrations toward real public use.

For brands, the opportunity is not limited to cinema audio. The same broadcast concept may support announcements, silent screens, tours and multiple language streams. Each use case creates different requirements for discovery, selection, latency, privacy, battery life and support.

Start with the complete connection chain

An Auracast experience includes at least three functional roles. A transmitter broadcasts audio. A receiver—such as a compatible hearing aid—plays it. An Auracast assistant helps the user find and select the desired broadcast, often through a phone, remote or App.

OEM buyers should map every step. Which device scans for broadcasts? How does the user identify the correct screen or language? Is a phone required? What happens if the phone model or operating system is not supported? How does the hearing aid return to its normal listening program after the broadcast ends?

A chip capability alone does not answer these questions. The production firmware and user journey must implement and expose the required functions.

Ask whether the hardware can support the required profiles

Bluetooth SIG explains that Auracast relies on features introduced with Bluetooth Core Specification 5.2 as well as the Public Broadcast Profile within the LE Audio specifications. A product carrying a newer Bluetooth number is not automatically an Auracast receiver.

Brands should request written confirmation of the chipset, radio, audio architecture, profiles, codec implementation and firmware plan for the exact configuration. If a supplier describes a field upgrade, ask what hardware foundation is already present, who will release the update and how it will be validated.

Power consumption also belongs in the review. Broadcast discovery and streaming should be tested against the intended battery, receiver and normal daily-use scenario rather than evaluated only on a development board.

Define how users discover and join a broadcast

The connection flow must be understandable to the intended user. A venue may offer several broadcasts, including multiple screens, auditoriums or languages. The assistant interface should distinguish them without relying on confusing technical identifiers.

For an older adult, large touch targets, clear names, confirmation feedback and an easy exit can matter as much as radio performance. Brands should also decide whether joining requires an account, network connection or location permission and explain those requirements before purchase.

Test the entire flow with representative users. A successful engineering connection is not sufficient if users cannot find the correct broadcast or recover when the connection fails.

Plan for venues that use different systems

Auracast will coexist with hearing loops, FM and infrared systems. NIDCD notes that these established assistive listening technologies remain available in theaters, classrooms, places of worship and other facilities.

A product roadmap should therefore be based on the markets and venues the target customer actually visits. Consider whether telecoil support, a venue receiver, a neckloop accessory or another bridge remains relevant. Do not imply that one connectivity feature guarantees access in every public location.

Test accessibility, not only connectivity

Interoperability testing should cover more than initial pairing. Evaluate broadcast discovery, join time, audio stability, latency, left-right synchronization, reconnection, movement within the venue, competing broadcasts, battery consumption and return to the default hearing program.

Use realistic environments and representative transmitter configurations. Include users who have limited experience with smartphone settings. Record the hardware, firmware, assistant device, operating system and venue setup for every test so results remain traceable.

Control claims, trademarks and compatibility language

“Bluetooth,” “LE Audio” and “Auracast” are not interchangeable marketing terms. The product team should confirm qualification and trademark requirements with Bluetooth SIG and qualified compliance specialists before using names or logos.

Compatibility claims should identify the tested product version and any required assistant or App. Avoid broad statements such as “works in all theaters” or “connects to every Auracast system.” Venue availability and receiver compatibility will vary.

Build support and lifecycle plans

Public broadcast audio creates support questions that may involve the hearing aid, phone, App and venue. Define which team handles each problem and give customer-service staff a short diagnostic path. Users should know whether to contact the brand or the venue.

Firmware and App updates need controlled release notes, compatibility regression tests and a recovery plan. If the feature is added after launch, packaging, instructions, website claims and customer communication should all move to the correct revision together.

OEM roadmap checklist

• Identify target venues, markets and customer use cases.
• Confirm the exact chipset, profiles and production firmware capability.
• Define the Auracast assistant, App and phone requirements.
• Map broadcast discovery, joining, adjustment and exit.
• Measure streaming stability, latency and battery impact.
• Test with multiple transmitters, broadcasts and representative users.
• Plan coexistence with loops, FM, infrared and venue receivers.
• Verify qualification, trademark and compatibility language.
• Control firmware, App, packaging and instructions by revision.
• Train customer support before making public claims.

Tomore is monitoring LE Audio and public assistive-listening developments as part of its technology roadmap. This article does not state that current Tomore models support Auracast. Qualified OEM and ODM partners should review the exact model, chipset and released feature set before making connectivity claims.