If ports, channels and universes have started sounding like the same thing, let's straighten them out. These settings decide where your effects go. Once they make sense, planning a controller or finding a mapping problem gets a lot easier.
Start with the real props and cables you have. Then make xLights describe that setup. Our examples below are data calculations; the electrical limits still come from the exact controller, pixels and wiring.
What each term means
| Term | What you are dealing with |
|---|---|
| Controller | The device that receives or plays lighting data and directs it to outputs. |
| Pixel port | A physical pixel-data output feeding a string or prop. |
| Differential output | A different output type that sends data to a compatible receiver, which provides local pixel outputs. |
| Channel | One control value, such as the red intensity of an RGB pixel. |
| Universe | A numbered block of channels used by protocols such as E1.31/sACN and Art-Net. |
| Model | The prop definition in xLights, including its shape and lighting configuration. |
One universe does not automatically equal one plug. A controller can map several universes across its ports, and one prop can cross a universe boundary.
Do the channel math first
An individually controlled RGB node uses three channels: red, green and blue. Multiply the addressable node count by three. Count addressable nodes rather than every visible LED package on a strip.
| RGB nodes | Channels needed |
|---|---|
| 50 | 150 |
| 100 | 300 |
| 170 | 510 |
| 200 | 600 |
| 300 | 900 |
This is why a 100-node RGB prop filled with EVO pixels needs 300 control channels. It does not tell you how much power that prop needs.
RGBW has an independently controlled white channel and commonly uses four channels per node. Four conductors do not automatically mean RGBW: our EVO+ design uses dual data. Choose the real lighting type in xLights model settings.
Why you see both 510 and 512
An E1.31 universe can contain up to 512 channels. Many RGB layouts use 510 so each universe holds complete groups of three. A supported 512-channel arrangement can work too. The important part is that the sender and receiver agree; the Ethernet-controller documentation covers universe sizing.
Take a 200-node RGB prop. It needs 600 channels. Starting at universe 1, channel 1 with 510-channel universes, the first 170 nodes use universe 1. The remaining 30 use channels 1–90 of universe 2. That channel split alone does not require a second physical output.
If colors go wrong at a repeatable boundary, compare the universe sizes at both ends. A sender using 510 and a receiver expecting 512 can interpret the same stream differently.
DDP uses a different addressing workflow
DDP carries channel data without the E1.31 universe-allocation workflow. Both devices must support it, and the selected range or offset must match. Check whether the receiver expects its first channel at 1 or retains absolute show-channel numbering.
For an FPP player, compare FPP Channel Outputs with the xLights controller entry. Pick a supported protocol and keep the two ends consistent. A protocol change cannot correct the wrong physical port or a mismatched pixel voltage.
Make the software order match the cable order
Name each enclosure and prop, then assign models to outputs using the supported Controller Visualizer workflow. If two 100-node RGB props share one continuous chain, the first uses the first 300 channels of that path and the second uses the next 300.
Move the second prop directly to the port and you have changed the physical data path. Its software assignment may need to change too. This is why we recommend labeling both cable ends before taking a working setup apart.
Upload supported changes, then inspect the controller. Input and output uploads do different jobs; the controller-settings guide explains that distinction.
Follow the first point where the result is wrong
- Local controller test works, xLights does not: check the controller address, protocol, input range and output enablement.
- One prop behaves incorrectly: compare its port, chain position, start node and count.
- The error starts at a boundary: compare channel alignment and universe sizes, then check whether local hardware testing shows the same fault.
- Everything shows unexpected effects: verify the show folder and stop other players or test modes sending to that controller.
Before buying from our controller range, make a list of props, pixel counts, cable routes, outputs and receiver needs. Then check the power plan separately. Addressing capacity never overrides a port, bank, fuse, cable or connector rating.
Keep learning
- xLights for Beginners: Set Up and Test Your First Pixel Prop
- How to Import an xLights Model and Match Your Prop Wiring
- Move Your xLights Show to Falcon Player: A Setup Checklist
Browse all Mattos education and support guides.
Reviewed October 29, 2026.
