Halloween ends, Christmas setup starts, and the same yard suddenly needs a different cast of characters. Keep the parts that already work, but give the changeover its own plan. A new prop can change pixel counts, wiring order, power requirements and what your sequences should do.
Our recommendation is to change one area at a time, keep the Halloween setup recoverable and test each Christmas section before moving on. That gives you a clear answer when something does not behave as expected.
Save Halloween before taking it apart
Save your final sequences and layout, back up the show folder and copy the required media and assets. Keep a separate dated copy away from the working computer. Review xLights backup settings; a backup checkbox does not automatically mean every file you need is included.
Photograph the installed cable paths and label anything that will be reused. Write down controller addresses, physical ports and brightness settings. Those notes are useful when next October arrives.
Choose a clear Christmas workspace
For a straightforward seasonal workflow, make a separate Christmas working copy of your show folder, with the required media copied or deliberately linked. Use xLights' Select Show Folder control to open it and confirm the folder before editing.
Leave the Halloween archive alone. In the Christmas copy, make a short list of what stays, what moves and what leaves the yard. For example, roofline models might stay while a character group changes. The physical controller can stay in place even when the models assigned to it change.
Compare the replacement props before reusing cables
A CoroWorks Frankie and a CoroWorks Santa are different models. The current listings identify 600 nodes for Frankie and 450 for Santa. Swapping the cable without updating the model does not describe that change to the software.
| For each changed location | Record before reconnecting |
|---|---|
| Physical prop | Exact product, version, size and orientation. |
| Pixels | Node count, voltage, protocol and connector variant. |
| Data path | Controller, output, input direction and position in a chain. |
| Power path | Supply, protected branch, extension and any injection points. |
| Software | Model name, groups, assignments and affected sequences. |
That count comparison is a planning example, not a statement that either prop can use any output or cable. Review the new load using our pixel power-planning guide. Disconnect power before changing connections.
Bring in the actual Christmas models
Use the CoroWorks model hub to get the matching files. Import them into the Christmas layout, then check the front/back view, starting node and wiring path. The official model-import guide explains local files and vendor downloads.
Keep the model names recognizable. Santa Left is easier to trace than “new prop 3.” Check orientation-specific notes on the product page before assuming a mirrored picture uses the same physical path.
Only remove unneeded Halloween models from the Christmas working copy after checking which sequences and groups use them. Preserve the archived Halloween setup so you can return to it.
Review groups and physical assignments
Open each affected group and check its membership and order. A Christmas character that is missing from your whole-house group can sit dark during effects assigned only to that group. A group containing an old model can also leave your sequence aimed at something no longer installed. The Model Groups guide describes membership and rendering behavior.
Use Controller Visualizer where supported to compare models with the real ports and chain order. If the replacement count changes, review everything downstream on that data path.
Save the corrected controller and layout settings. Upload supported input or output changes to the intended hardware, then inspect the result. The controller-settings documentation explains those separate uploads.
Re-render the Christmas show
Open the sequences you intend to use, check for missing models and assets, and review the effects on the changed props. A familiar effect can look different on a new shape, even when the wiring is correct.
Run Check Sequence, resolve errors and review warnings. Use Batch Render for the affected sequences after layout or addressing changes. Confirm the updated playback files were produced. The Tools documentation covers both checks.
Change the player as well as the yard
Transfer the new sequences and required media to the actual player. Follow our xLights-to-FPP checklist if you use Falcon Player. Review the playlist entries and disable or replace the old seasonal schedule deliberately; new files on the player do not choose the new show for you.
FPP users can check the playlist and scheduler references for start, repeat and stop behavior.
Finally, test each changed prop with colors, movement and off. Rehearse a full Christmas playlist from the real player, then prove a scheduled start and stop. Save a fresh backup of that working result. You now have two seasonal setups you can understand and reuse.
Keep learning in the Mattos Designs Learning Center, with guides for your next project and troubleshooting help when you need it.
Reviewed October 29, 2026.
Example changeover record for one controller output
Your label can identify a location even when the seasonal character changes. Keep the controller and cable names stable, then document the model and count that now occupy that location.
Scroll sideways to see all columns.
| Item | Halloween record | Christmas record |
|---|---|---|
| Location label | Front Yard Character Left | Front Yard Character Left |
| Installed model | Exact Halloween model and size | Exact Christmas model and size |
| Addressable nodes | 600 in this illustrative layout | 450 in this illustrative layout |
| Next 100-node section on the same data path | Node positions 601–700 | Node positions 451–550 if the chain remains consecutive |
| Files and schedule | Archived Halloween render/media and notes | New Christmas render/media and verified playlist |
The example shows why changing the first model can also change a later model's local data positions. It does not establish a safe power arrangement or approve chaining two particular products. Recheck the actual connector, pixel protocol, voltage, total branch load and controller configuration.
Make the handoff deliberate: update the model, inspect the downstream assignments, review the power record, test the entire affected output, render the affected sequences and transfer the new files. Then walk the yard while playing the Christmas test from the actual player.
Photograph the completed Christmas connection before storing the Halloween prop. Put the archived configuration name on the Halloween storage label so you can find the right setup next year. Your parts worksheet can hold both seasonal configurations.
