Connect EZPlayer to Your Controllers
A working EZPlayer connection needs a reachable controller, a supported network output and a port map that matches the display. Check those layers in that order. Finding a controller on the network is useful evidence; it does not prove that the next song will reach the correct pixels.
Start with the network output
EZPlayer documents DDP and E1.31/sACN playback over IPv4. Use the protocol and address specified by the controller’s configuration and your xLights network setup. Network protocol is different from the pixel protocol selected for a physical output: DDP does not tell you the voltage, connector wiring or pixel type.
For a Mattos system that already works from xLights, retain that known configuration while moving playback to EZPlayer. Note each controller’s name, address, protocol, enabled state and intended models. Changing all five at once makes a fault harder to locate.
Official reference: EZPlayer capabilities; xLights Ethernet controller configuration.
Playback and controller management are different
The official support matrix describes detailed status, configuration and actions. A configured DDP/E1.31 controller can still be usable for playback without every management feature. Check the exact model and firmware before depending on configuration upload or statistics.
Scroll sideways to see all columns.
| Controller example | Published management evidence | What to check |
|---|---|---|
| Baldrick B8 / B17, under ILightThat | Firmware 3.5 and 3.7; lab-tested CV entry, marked as of EZPlayer 0.6.9 | C means configuration; V means verification. Confirm your actual firmware and offered actions. |
| Other configured DDP/E1.31 controllers | Playback support is broader than the management-driver table | Verify network output first, then consult the current matrix for model-specific tools. |
The table above is a dated documentation snapshot, reviewed October 29, 2026. It is not a promise that every revision of a controller has identical features.
Official reference: Controller support matrix.
Discover devices on the intended show network
Open Controllers and review the interfaces selected for scanning. Sweep looks for responding addresses; Identify attempts supported controller identification; Full retrieves more detailed information. Use the network connected to the show equipment.
A scan result does not automatically assign models or physical ports. Also review any Proxy Allowed setting separately: proxy access is a remote-access choice, not a requirement for every scan. Keep that access limited to the devices your operators need.
Official reference: Networks and scanning.
Read status as a specific test result
The controller list combines configured devices and discoveries. A green response indicates a successful ping; it cannot confirm channel order or pixel wiring. A configured, enabled device that responds is Present. A configured device that does not respond is Absent. An Unregistered discovery still needs the correct show configuration.
If a device is absent, check its power, physical network path and address before changing model mapping. If it responds but the wrong prop lights, move to channel and port checks. If it is disabled, establish why before enabling it for live output.
Official reference: Controller List.
Compare the expected and physical port map
The Port Map connects models to controller outputs. It can represent one model spanning several ports or several models sharing a port. Compare the planned ports, model order and pixel counts with the installed wiring; supported device details can help expose a difference.
In xLights, Controller Visualizer allocation also depends on the model’s physical string configuration. Resolve reported connection errors before uploading. A visually plausible layout can still describe the wrong number of physical outputs.
Official reference: Port Map; xLights Controller Visualizer.
Upload config changes the controller. Available actions depend on its driver. Save the working configuration and review the expected map before an upload. Perform detailed refreshes and configuration changes during setup time; the manual notes that fetching controller details can be disruptive.
Official reference: Controller actions.
Mattos example: an existing Baldrick first-100-pixel setup
Use the Mattos first-100-pixels plan as the physical and xLights reference. For an already verified Baldrick output, keep its known model, output port and controller address. Render the test sequence from that layout, select the same show folder in EZPlayer, and confirm the intended controller is enabled.
Run the same short section with only EZPlayer transmitting show data. Check the first pixel, last pixel and colors before adding other props. This is a playback handoff test; EZPlayer’s scan is not evidence that the enclosure, power system or connectors have been configured for you.
For the broader hardware workflow, use the Baldrick Learning Center. For a specific fault, continue to EZPlayer troubleshooting with the controller name, address, firmware and exact observed behavior.
