The IMMERSE™ Node Ecosystem: Distributed by Design

The IMMERSE™ platform is, structurally, three layers: the Designer where authoring happens, the Runtime where execution happens, and the node ecosystem where the work actually meets the world.

This article is about that third layer.

The case for distributed nodes

Conventional show control architectures centralize processing in a rack. Hundreds of cables run from the rack to every speaker, projector, fixture, and relay in the show. Every signal has to travel the full distance from the rack to the endpoint. Every cable run is a potential point of failure. Adding a room means re-cabling the rack.

The IMMERSE approach is the opposite. Intelligence sits at the edge of the show — at the speaker, at the projector, at the relay. Small, purpose-built nodes live where the work happens and speak the IMMERSE protocols natively over standard Ethernet. Cable runs collapse. Latency disappears. Failure is contained to a single node, not propagated through a centralized DSP.

The four nodes

The IMMERSE node ecosystem ships in four core form factors today:

• GPIO Node — Distributed digital and analog I/O. Sensors, contact closures, relays, motorized hardware, environmental triggers. Ruggedized industrial connectors. Per-channel isolation. Designed to live at the device it controls.
• Audio Node — Multi-channel networked audio with onboard DSP, time-aligned playback, and synchronized routing. Built for ambient audio zones as much as for theater-scale show audio.
• Video Node — Networked playback for projection, displays, and LED systems. Frame-accurate sync with the broader show clock. Edge-blending support for multi-projector environments.
• DMX Node — Lighting control endpoint speaking DMX, sACN, and Art-Net. Time-synchronized to the broader show timeline so lighting cues land at the same moment as the audio that prompted them.

IMMERSE Node OS

All four nodes share the same underlying firmware: IMMERSE Node OS. The operating system handles network bring-up, time sync, protocol parsing, watchdog recovery, fault reporting, and over-the-air updates from the Runtime layer. Operators see one platform. Engineers maintain one codebase.

That commonality is what allows the platform to extend cleanly. New node form factors plug into the same OS and the same protocol — they show up in Designer as native endpoints without bespoke driver work.

Industrial design language

The aesthetic of the hardware matters. Show racks are inspected. AV equipment lives in client-facing spaces. Hardware that feels like a hobbyist project undermines the operator.

Every IMMERSE node ships in extruded aluminum chassis with passive cooling — no fans, silent operation, indistinguishable from the professional AV gear it lives next to. Rack-friendly form factors. Front-panel status indication. Designed to slot into the racks an integrator already builds today.

The look isn’t decoration. It’s part of the product.