Reviewed and corrected September 21, 2026.
A small theater needs repeatable cues and an operator who can recover calmly when something changes. Start with the production's requirements rather than the size of a console.
Write down the cue requirements
Identify manual scene changes, fades, moving-head positions, music-reactive passages and any timecode requirements. These are distinct functions. Verify them in the selected application and release; do not infer a full theatrical cue stack from a scene-recall feature.
Choose fixtures for their role
Evaluate face lighting, coverage, noise, dimming and camera behavior. Consumer smart lights can provide practical or scenic accents when tested, but their response and failure behavior may differ from theatrical fixtures.
Build and test the patch
Use the correct fixture mode and channel footprint. Document interfaces and network destinations. If DMXSmartLink accepts another console's Art-Net or sACN input, verify the entire path. Its supported network output is Art-Net; do not assume sACN output.
Give operators predictable controls
Use clear scene names and rehearse the actual sequence. A labelled Stream Deck or deliberately mapped MIDI controller can reduce mouse use. Check the behavior after scene reordering, reconnects and a controller restart.
Plan recovery before opening night
Back up the show and controller configuration. Keep a tested steady scene and a documented fallback appropriate to the venue. Neither a spare cable nor a Dual I/O kit automatically provides seamless redundancy. Keep required emergency lighting independent of show software.
Compare systems in rehearsal with the busiest cues. A large fixture library is useful, but it does not certify every mode, fixture or consumer-light integration.
Check your version and your lights
DMXSmartLink runs on supported macOS, Windows 11, Ubuntu and Raspberry Pi 5 systems, or on a preconfigured HUB. It accepts Art-Net and sACN input and provides Art-Net output; physical DMX requires a supported interface. Smart-light functions depend on the model and integration, including Homebridge or Home Assistant. The bundled Home Assistant companion on Pi/Ubuntu is experimental. Cloud integrations require internet; local paths have their own compatibility requirements.
See current capabilities and beta limitations and compare setups. Use the free 14-day trial, with no credit card required, to test your actual lights. Current prices and included items are on the product pages.
