Start with one project you can finish, test, and enjoy. That might be arches along the driveway, a coro feature, a roof section, or a planned MegaTree. Once you know what you are building, we can help you choose the parts that make it work.
The easy trap is buying a little of everything and discovering that the connectors, power, or mounting do not line up. Use this worksheet before filling the cart. If you are still choosing a direction, our Start Here page walks through the main options.
Give the project a finish line
Write one sentence: “Four matching arches beside the driveway, running color sweeps with my show.” Then decide where people will watch, how much space you have, and whether you want music synchronization or a repeating animation.
Measure the installation area and the actual cable routes. Include doors, walkways, landscaping, mounting space, and access to the connections. Take a photo from the audience's viewpoint. Also decide where the finished prop will live when the season ends.
Make one list for the whole project
| Part of the plan | What we need to know |
|---|---|
| Props | Exact names, sizes, quantities, and viewing direction. |
| Pixels | Model, voltage, protocol, count, spacing, and connector. |
| Mounting | Frames, strips, supports, brackets, and installation requirements. |
| Control | Controller model, physical outputs, and any supported receivers. |
| Power | Expected load, supply, distribution, cable ratings, and protection. |
| Cables | Measured routes, extension lengths, directions, and approved adapters. |
| Software | Sequencer, model files, required licenses, and nightly playback method. |
| Time | Bench test, assembly, installation, and full-show rehearsal dates. |
Beside each item, write “have,” “included,” “need,” or “ask Mattos.” Check the selected product variant before marking something included. A board-only controller and a completed controller build are different purchases, even if the board name is the same.
Count the nodes before choosing outputs
For coro, use the exact prop's documented node count and matching model. For an outline, account for spacing, corners, starting positions, and sections needing separate inputs. Count addressable nodes; multiple visible LEDs can share one address in some products.
As a planning example, four props with 100 RGB nodes each use 400 nodes and 1,200 color channels in ordinary ungrouped models. That still does not tell you how many controller ports or power feeds to use. The physical wiring and electrical requirements determine those.
The xLights model settings distinguish nodes, strings, and controller assignments. Our model and wiring guide helps you match the software to the real prop before pushing pixels.
Choose parts that work together
For a 12V WS2811-compatible project, you might compare standard EVO pixels with a suitable MD1500 Baldrick8 xConnect build. That is the start of a compatibility check. Match the selected EVO connector, required pixel count, load, cables, and mounting to the finished plan.
Check both data links: sequencer or player to controller, then controller to pixels. A connector adapter does not automatically convert voltage or pixel protocol. Our addressing guide explains the data side; the hardware instructions set electrical limits.
Budget for what makes the project usable
Include lights, props, controller, power equipment, enclosure, mounting, extensions, adapters, shipping, taxes, and any paid software or sequences. Add useful spares and the tools you need. Keep reusable equipment separate from parts specific to this project.
If the total is too high, reduce the project and price the complete setup again. Half as many props does not necessarily mean half the cost when the controller or support structure stays the same. Keep future additions on a separate list so they do not hold up the first build.
Leave room to test before installation day
Check shipments, identify the parts, and bench-test one complete compatible setup. Verify colors, node order, and playback. Label the working cable and keep the settings with the prop. Our first-prop xLights guide is a useful next step.
Want help checking the cart? Send us your list, a location photo, and the model numbers of equipment you already own. That gives us something concrete to check before you discover a missing connection out in the yard.
Work through a complete example
Use From xLights Layout to Shopping Cart to turn exported models, measured routes and controller assignments into a filled parts list. Then compare three Mattos project budgets so included equipment, additional materials and reusable parts stay visible.
For the physical build, follow the window-frame project or compare DIY and supplied arch options. Each project needs its own mounting and power plan even when the software treats the models similarly.
Keep learning
- Pixel Power Planning: Voltage Drop, Injection and Brightness
- xConnect vs M-Connect: Match Pixel Cables and Adapters
- Light Show Preflight Checklist: Test, Label and Back Up
Browse all Mattos education and support guides.
Reviewed October 29, 2026. Use the instructions for your exact hardware and installed software version.
