Bring an Existing xLights Show into EZPlayer
Start with one song and the xLights layout that already matches your display. EZPlayer can read that show folder, play a rendered sequence and send its channel data to your network controllers. Keep editing effects and models in xLights; use EZPlayer to organize and run the resulting show.
This route works without an EZRGB cloud account. If you want EZRGB to supply and manage the layout, follow cloud setup instead. Installation and the initial choice are covered in first start.
Official reference: Local getting-started guide; EZPlayer overview.
1. Identify the working show folder
Open your established show in xLights and check its show-folder location. Use the folder for this display and season, then make a dated backup before experimenting. A familiar song is a better first test than a new sequence: you already know which prop should light and where the music begins.
Scroll sideways to see all columns.
| File or location | Job | Mattos check |
|---|---|---|
xlights_rgbeffects.xml |
Models and layout | The props match the display you are testing. |
xlights_networks.xml |
Controller and network configuration | Addresses and controller assignments belong to this show. |
Rendered .fseq
|
Frames the player sends to the lights | Render after relevant layout or sequence changes. |
| Matching audio | The recording paired with the sequence | Use the intended recording, with the expected duration and start. |
Keep associated files together where practical. EZPlayer stores its own song, playlist and schedule data in a .ezplayer directory inside the show folder. Back up the whole working folder, including that data; copying a few FSEQ files does not preserve your operating plan.
Official reference: Show files and player data.
2. Select the folder on the show computer
In the desktop application, open Settings → Show Folder and choose the existing folder. Folder selection happens on the player computer. Changing it loads that folder’s show data, so check the displayed path before continuing.
If audio lives elsewhere, set the optional Media Folder. The path must exist on the show computer, even when you later operate EZPlayer from a phone. A folder on the phone or another computer is not automatically available to the player.
Official reference: Show Folder settings.
3. Register one complete song
Use Add Song, select the rendered FSEQ, and review any companion audio EZPlayer finds. Fill in the required title and artist, then save. An FSEQ is required; audio is optional for an intentionally silent animation. Automatic matching is a convenience, so verify the actual file before a show-night test.
Bulk Import is useful after that first success. Its audio-matching requirements differ from a deliberate silent-song import: matching companion audio must be discoverable beside the sequence or in the configured media location. Use the same base filename for the intended pair. A browser-based bulk import registers files already available to the player; it does not upload a folder from your phone.
Official reference: Songs and bulk import.
4. Test the same layout through EZPlayer
Mattos recommends a small, supervised test before enabling the full schedule. Stop any other show player and xLights output testing that could also send data to these controllers. Keep the established controller configuration for this first comparison.
- Check that the intended controller is enabled and reachable. Use controller and network setup if its identity or status is unclear.
- Play the single registered song through the player’s jukebox. Start with a familiar section and observe the expected prop.
- Compare physical order, colors and model boundaries against the xLights preview. Record a specific mismatch, such as “window two responds when window one should.”
- Listen for the expected recording and timing. A wrong audio edit needs a file correction before sync adjustment is useful.
- Stop the test, correct one cause at a time, and repeat the same section.
A correct preview verifies the visual plan. The physical test verifies the path from that plan through network configuration and controller ports. Keep those checks separate when diagnosing a result.
Official reference: Jukebox controls; xLights Controller Visualizer.
5. Keep a clear owner for layout changes
If you later connect the cloud, check the layout mode before editing. xLights master keeps the local layout authoritative; Cloud master allows the cloud layout to replace local changes on sync. Choose the workflow intentionally and use the appropriate push or sync action after a change.
Official reference: Cloud status and layout ownership.
Once the first song passes, continue to media import, playlists and scheduling. Save the successful configuration before expanding the show; the backup guide explains what to preserve.
