Light of Y harnesses Art-Net protocol features to bring responsive, architectural lighting under unified control. By translating sACN and Art-Net data into tidy DMX universes, it bridges modern network lighting with legacy dimmer racks.
Designers value clean signal separation, timing stability, and per-universe monitoring, which makes Light of Y a practical centerpiece for touring, broadcast, and fixed installation.
| Primary Signal | Route Capacity | Sync Mode | Diagnostics |
|---|---|---|---|
| Art-Net sACN input | Up to 6 DMX universes | Multicast and unicast | Live packet error rate |
| DMX 512 output | Per universe rate control | Rate-based to avoid drift | Frame loss and blackout alerts |
| Net priority mapping | Universe lock to slot | Clock master or follower | Log of warnings and fixes |
Art-Net Integration Workflow
Packet reception and parsing
ArtNet controller LightofY listens on designated UDP ports, validates HTP merge rules, and extracts raw DMX values with minimal latency. Subnet and universe mapping is editable per project.
Rate shaping and buffering
To protect downstream fixtures, Light of Y applies timing adjustments and jitter buffers. This reduces timing errors when network load spikes or when multicast storms appear on congested venues.
Physical Outputs and Redundancy
DMX hardwired delivery
Each selected universe exits via robust XLR ports, with configurable idle mode and polarity sense. The relay-based outputs support legacy dimmer packs and modern LED movers without protocol translation issues.
Failover and monitoring
Internal heartbeat monitoring triggers automatic switchover to backup Art-Net streams. Status LEDs and SNMP traps report port and frame health so shows can react before visible faults appear.
Deployment in Architectural Installations
Symmetrical load balancing
ArtNet controller LightofY can split a single show file across two wired paths, balancing universe groups to reduce single-point failures. The switchover is transparent to fixtures when gateways are correctly tuned.
Cabling and grounding strategy
Star grounding and shielded CAT6 runs keep induced noise low, especially under stage lighting truss and near RF-heavy broadcast gear. Best practices recommend one common reference point to avoid ground loops.
Operational Tuning and Scenes
Scene recall and cue rates
Fixture fade times, wait queues, and burst modes can be stored as named scenes. Light of Y applies rate curves per universe so moving heads and matrix pixels react in time with music or narration cues.
Macro and schedule chains
Simple if–then macros chain multiple universes into sequenced responses, such as blackout-to-burst or hail-Mary patterns. Operators trigger these from consoles or external OSC clients without extra programming on downstream gear.
Best Practices and Takeaways
- Validate universe-to-port mapping with a test fixture before house lights dim.
- Use dedicated VLANs for Art-Net traffic to limit broadcast load on front of house Ethernet.
- Enable frame logging on startup to simplify troubleshooting timecode or MIDI sync issues.
- Set conservative rate limits on high-channel-count universes to protect older dimmer packs.
- Schedule periodic cold reboots during extended runs to purge memory fragmentation on long tours.
FAQ
Reader questions
How does Light of Y avoid DMX timing drift when receiving Art-Net?
It measures packet arrival intervals and applies rate-based adjustment, aligning output edges to a stable clock while preserving HTP merge semantics across redundant feeds.
Can I map different subnet layouts to one DMX output line?
Yes, per-universe offset and length settings let you fold non-sequential Art-Net universes into a single contiguous DMX profile without repatching downstream fixtures.
What happens during an Art-Net multicast storm on a busy show?
Queue depth and jitter control limit buffer overruns, while packet-error logging highlights problem ports so you can replace cables or segment the network before visible fade artifacts occur.
Is it possible to use Light of Y as a clock master for sACN on a mixed vendor network?
When elected as clock master, it distributes timing to compliant nodes and compensates for path asymmetry. Selective disable of multicast on slave ports prevents feedback loops on large installations.