Start with the four layers
| Layer | Job | Typical examples |
|---|---|---|
| 1. Content and programming | Creates video, effects, scenes, cues, timelines, or generative looks. | MADRIX 5, Resolume Arena, ENTTEC ELM, Pharos Designer 2, CueCore programming tools |
| 2. Pixel mapping and patch | Matches virtual pixels or fixtures to physical positions, channels, and universes. | MADRIX 2D/3D mapping, Resolume Advanced Output, ELM stages and strips, Pharos Designer fixture layout |
| 3. Transport and playback | Sends Art-Net or sACN live, or stores and plays a show without the programming computer. | A live computer; Pharos VLC/LPC; Visual Productions CueCore3; supported controller recording/playback features |
| 4. Pixel output | Converts network lighting data into WS281x, SK6812, APA102, or another tape-specific signal. | Advatek PixLite, MADRIX NEBULA, ENTTEC pixel controllers, Visual Productions SpiNode |
The usual signal path is content or show controller → Art-Net/sACN network → pixel controller → SPI tape. Power supplies and injection wiring are a parallel system; Art-Net does not power the LEDs, and a pixel controller does not eliminate voltage-drop planning.
What each ecosystem is best at
MADRIX: effects-driven 2D and 3D pixel mapping
MADRIX 5 combines real-time generative effects, media, cue lists, timelines, audio-responsive looks, and both 2D pixel and true 3D voxel mapping. It can output Art-Net and sACN to first- or third-party network hardware. MADRIX NEBULA is the matching Ethernet/USB-to-SPI pixel-tape interface, but MADRIX software can also feed compatible controllers from other manufacturers. The playback computer and MADRIX KEY license are part of the software system; use MADRIX AURA or another suitable standalone controller when computer-free recorded playback is required.
Advatek: flexible pixel-output hardware
Advatek PixLite controllers receive Art-Net or sACN and produce the selected pixel-chip protocol. Advatek Assistant is the configuration and fleet-management tool; it is not the creative content source. A PixLite can sit downstream of Resolume, ELM, a lighting console, or an architectural controller. Current Mk3 systems also offer SHOWTime recording and standalone playback features, but confirm the exact model, capacity, and triggering needs before treating the output controller as the complete show-control system.
Pharos: permanent playback and integration
Pharos Designer systems are aimed at architectural and themed installations that must start, schedule, trigger, synchronize, and run reliably without an operator’s laptop. The VLC family is optimized for large pixel arrays and video-like effects; LPC-family controllers are strong where timelines, fixture control, logic, and integration matter. Designer 2 is used to build and commission the project, then the controller runs it. Pharos can output network lighting data to downstream pixel controllers when direct tape output is not part of the selected hardware.
Resolume Arena: live visuals and performance
Resolume is a live visual and media-server application. Arena’s DMX fixture output can sample video or effects through a pixel map and send Art-Net to compatible nodes and pixel controllers. It excels when an operator, performer, MIDI/OSC control, live video, projection, and LED pixels need to share one creative canvas. The computer remains part of the live playback system, so permanent unattended installations need an appropriate computer strategy or a separate standalone playback approach.
ENTTEC ELM: purpose-built LED mapping
ENTTEC LED Mapper is focused specifically on mapping images, video, and effects onto LED pixels and DMX fixtures. It outputs Art-Net, sACN, and KiNet over the network to pixel controllers and nodes. Compared with a broad live-video platform, ELM’s workflow is centered on defining LED layouts, assigning strips, testing pixels, and running mapped content. It still needs compatible output hardware between the Ethernet network and SPI tape.
Visual Productions: modular standalone control
The Visual Productions family separates show control, interfaces, and physical output into modular devices. CueCore3 can play scenes and effects, record incoming DMX/eDMX, schedule events, respond to triggers, and run continuously without a computer. SpiNode converts Art-Net or sACN into four SPI outputs and can expand a CueCore3 pixel system. Other family devices provide touch panels, buttons, I/O, DMX ports, timecode, and remote management.
Side-by-side orientation
| Example | Primary role | Runs without programming computer? | Directly drives common SPI tape? | Strong fit |
|---|---|---|---|---|
| MADRIX 5 + NEBULA | 2D/3D mapping, generative effects, cue lists, timelines, and SPI output | No for MADRIX 5 live playback; separate MADRIX standalone hardware is available for recorded network playback | Yes, through NEBULA | Clubs, art installations, façades, 3D LED objects, audio-reactive and effects-heavy systems |
| Resolume Arena | Live content, effects, pixel mapping, Art-Net output | No—the playback computer is the show source | No; use a compatible pixel controller | Concerts, clubs, events, live video and projection |
| ENTTEC ELM | LED-focused media playback and pixel mapping | No—the ELM computer is the show source | No; use ENTTEC or compatible network pixel hardware | Mapped LED art, façades, signs, installations with a dedicated PC |
| Advatek PixLite | Art-Net/sACN-to-pixel conversion and output | Live input normally comes from another source; supported Mk3 playback features can cover some standalone uses | Yes | Flexible, high-density pixel output from many software or console sources |
| Pharos VLC/LPC | Standalone show playback, scheduling, logic, integration | Yes | Model/system dependent; network output commonly feeds downstream nodes or pixel controllers | Architectural, museum, theme, façade, and unattended 24/7 systems |
| CueCore3 + SpiNode | Standalone show control plus modular SPI output | Yes | Yes, through SpiNode | Permanent installations needing triggers, schedules, interfaces, and modular expansion |
Product capabilities change. Treat this table as a system-orientation guide, not a substitute for current datasheets. Verify universe count, pixel protocol, frame rate, synchronization, licensing, storage, input/output, and environmental requirements for the exact model and software version.
Four common system recipes
Effects-driven 2D or 3D installation
MADRIX 5 → Art-Net/sACN → MADRIX NEBULA or another compatible pixel controller → LED tape. This is a strong path when generative effects, sound response, cue lists, or three-dimensional LED layouts are more important than conventional video-layer performance.
Live event or touring installation
Resolume Arena → dedicated wired network → Advatek PixLite or another supported pixel controller → LED tape. This keeps content creation and playback on the media computer while purpose-built hardware handles the electrical pixel output.
Dedicated mapping computer
ENTTEC ELM → Art-Net/sACN network → ENTTEC or third-party compatible pixel controller → LED tape. This is a straightforward choice when the installation has a maintained Windows computer and the main need is LED mapping rather than complex building automation.
Unattended architectural installation
Pharos controller → network output hardware → LED tape, or CueCore3 → SpiNode → LED tape. Both approaches move show playback into solid-state hardware and can add schedules, contact closures, touch interfaces, timecode, and system integration.
Questions to answer before choosing
- Live or unattended? Is an operator and playback computer acceptable every time the system runs?
- Video-like content or lighting cues? A media mapper and an architectural timeline controller solve different creative problems.
- How many actual pixels and channels? Calculate universes from the real pixel format, grouping, and color-channel count.
- Which tape protocol? Confirm the exact chip, voltage, color order, data-only versus data-and-clock wiring, and maximum pixels per output.
- What happens after a failure? Define startup behavior, watchdogs, stored playback, replacement configuration, backups, and remote support.
- What must trigger the show? Consider schedules, buttons, contact closures, OSC, MIDI, timecode, building-control commands, or a lighting console.
- Who commissions and maintains it? A familiar, documented workflow is often more valuable than the largest specification number.
Commissioning checklist
- Draw the complete signal and power path before buying hardware.
- Build the pixel patch from physical output, port, universe, start channel, pixel count, and color order.
- Use controller test patterns before opening the content software.
- Test red, green, blue, white, first pixel, last pixel, and universe boundaries.
- Prefer a dedicated wired lighting network and document every IP address and universe.
- Back up software projects and export controller configurations.
- Power-cycle the complete system and confirm it recovers without manual repair.
- For permanent work, test schedules, triggers, loss of network, loss of source, and restart behavior.
Size the electrical system before selecting outputs
Use the calculator for tape load, power supplies, feeder current, voltage drop, and injection points. Then select control hardware from pixel count, protocol, universes, distance, and playback requirements.
Open LED Tape CalculatorRelated guides
Sources & further reading
- Advatek — Advatek Assistant 3
- Advatek — PixLite Mk3 network input and SHOWTime playback overview
- Pharos Controls — Designer VLC
- Pharos Controls — Designer software and tools
- Resolume — Arena DMX and Art-Net output
- Resolume — Advanced Output
- ENTTEC — ELM pixel-mapping software
- ENTTEC — ELM user manual and signal path
- Visual Productions — CueCore3
- Visual Productions — SpiNode
- MADRIX — MADRIX 5 software
- MADRIX — NEBULA SPI pixel-tape controller
- Environmental Lights — Pixel product formats and controller compatibility overview