Lighting And Audio Converge In The Specification

Signify and Bose Professional signed a memorandum of understanding in Singapore on 9 October to develop and sell integrated lighting and audio across Southeast Asia. Signify brings its connected lighting portfolio, including Interact, Dynalite and Color Kinetics; Bose Professional brings loudspeakers, amplifiers and the ControlSpace audio ecosystem. The initial targets are stadiums, arenas and entertainment venues, then hospitality, immersive retail and experience centres, and flexible workplaces. The mechanics are a joint 180-day action plan covering priority markets, reference architectures, demos and proof-of-concept work with integrators and consultants, with Signify's chief executive putting roughly twelve months on the regional test before a wider rollout, against a regional ICT spend IDC puts at 647 billion US dollars for 2026.

Strip away the marketing and the technical claim is modest but consequential: light and sound are already both IP endpoints, so they can be designed and commissioned as one system rather than two that happen to share a ceiling. Connected lighting runs on Power over Ethernet or on DMX-based control protocols such as Art-Net and sACN; professional audio runs on Dante or AES67. Lighting control is small, bursty and tolerant of tens of milliseconds. Audio is a continuous stream that cannot tolerate a late packet, which is why audio networks want QoS, IGMP snooping, a disciplined PTP grandmaster and their own VLAN. Put them on one switch without thinking and the failure will not be dramatic; it will be a click in the audio every time the lighting scene changes.

What actually improves for an integrator is the cue. In a stadium or an experience centre, the moment the lights go to a warm wash is the moment the sound should lift, and today that synchronisation is usually stitched together in a show-control layer that calls two systems and hopes neither is slow. A joint reference architecture that treats both as scheduled events on one timeline is genuinely useful, and gets copied for a decade once it is specified. The risk is demarcation. When one throat is choked, who owns the switch, the VLAN plan, the PoE budget and the grandmaster? Lighting people and audio people have different default answers, and the project needs one before the first cable is pulled. The other risk is lock-in: an architecture that only works with two brands is one a consultant will avoid on any competitively tendered job.

So the checklist looks like a network design, not a product list. What is the PoE budget per port and per switch, given PoE++ luminaires and audio endpoints draw real power with non-linear inrush? Is there a documented multicast group plan, and does the switch do IGMP snooping and querier properly? Which device is the PTP grandmaster, and what happens to audio if it disappears? Does the lighting controller hold a fallback scene when the network is down, because a dark venue is worse than a quiet one? Is there an open API, or only a cloud portal? And does the technical file also serve the Cyber Resilience Act timeline? Amtune works at the audio networking layer these projects depend on: Dante and AES67 interfaces, Dante audio modules and AES67 audio modules for OEM products, DAC and preamp platforms for monitoring, and seamless hybrid matrices for the video side. Technical enquiries at sales@amtune.com.