An easy-to-use pixel show player for the xLights ecosystem.

We anticipate that EZPlayer will be usable in mid-2026 for 4th of July shows. In addition to the handful of shows that successfully ran the pre-alpha versions of EZPlayer in October-December 2025, there is a lab setup where ongoing work is being tested. We welcome additional early testers!

Currently, EZPlayer supports a subset of what xSchedule supports:

• Setup of a simple schedule of playlists of sequences
• Execution from an xLights show folder
• .mp3 and .fseq playback
• DDP and E1.31 controllers on attached IPv4 networks
• A jukebox view of songs to choose from
• A variety of status screens
• Remote Falcon
• Local Web UI
• Background sequence
• Volume control automation

We are currently enhancing:

• Live view
• Control panel
• Controller status ping
• Background blending and other small issues

It doesn't support (and won't soon support):

• USB controllers
• Master/Remote show designs
• HDMI video playback

You do not need to build from source to use the app.

➡️ Download the latest release:
https://github.com/ezpixelplayer/ezplayer/releases

We currently provide builds for:

• Windows (x64)
• macOS (dmg)
• Linux (AppImage)

Just download the installer or portable build and run it.

When you first run EZPlayer, you will choose your show directory. This should contain your xLights files, which are needed for EZPlayer to find your controllers. You can change the show folder later from the "Playback Settings" screen.

The player opens to the "Player" screen, but there will not be much here yet. So, navigate between screens using the sidebar menu. (If no sidebar is visible, click the 3 bars in the upper right.)

Start on the "Songs" screen. Here you can add songs, which associate the .fseq file with its .mp3 file, the song title, etc. If you have image files (or URLs) handy, you can enter those as well, this way your songs will show with images in the jukebox gallery. It is recommended to add some tags to your songs, as this will help build playlists. You can try playing your songs from the "Jukebox" gallery.

After adding some songs, create playlists on the "Playlists" screen. You can think of a playlist as an ordered list of songs to play, but it can also be used as a "set" of songs that are not taken in order. As we'll see later, you might want to make an "intro" playlist, a few main playlists, and an "outro" playlist.

After you have some playlists, visit the "Schedule" screen. Here, you can assign your playlists to play on the right days. Note that each schedule item is where you can set the "intro" and "outro" that goes with your show playlist, assign priorities, add loop/shuffle, and so forth.

Return to the "Player" screen, which will give you a summary of what is going and what will happen next. But, if you want more detail about exactly how your schedule will run, try the "Schedule Preview" screen, or if you want more details about how the show is running, how the controllers are performing, etc., try "Show Status".

Sometimes you have to restart the player to get it to do what it is supposed to. EZPlayer does not do well with missing files. Don't remove anything.

Please report any bugs or requests here: GitHub Issues

For any general discussion, join us on Discord.

EZPlayer is a show player and scheduler app for animated light shows based on pixel controllers. It reads files and sends the data over the network at show time, and plays the audio in sync. This is very similar to what xLights xSchedule does.

It is also similar in purpose to FPP, though FPP is more of an embedded service with a web UI.

With two established player solutions, why would anyone make a brand new one?

Well, we liked the design of xSchedule but found it to be underdesigned and undermaintained, and getting the sort of simplicity and features we wanted to see in the future would have been difficult on that codebase.

On the other hand, FPP is more of a decentralized design and can be extremely complex to work with.

So, we started a new one, featuring:

• Node.js / Electron stack / React, for a modern UI that supports the same look both on the desktop and on the web
• Simplicity, starting with how songs and playlists are assembled
• Affero GPL licensing, so it is free forever

We have a lot of features planned for the coming years... better previews, better controller health checks, a cloud portal, and so forth. We aim to simplify the way the xLights ecosystem works, while solving long-standing problems. We have a plan for interactive show elements, but without resorting to a complex and brittle plugin architecture or a tangled web of version dependencies.

Despite that broad scope, we want to avoid the complexity that currently plagues the xLights ecosystem, so there are a few things we do not expect we will ever implement:

• USB controllers
• Cape support (this is a player, not a controller firmware)
• All the complexity and limitations of anything like FPP connect
• A complex plugin architecture

EZPlayer is developed in part by EZRGB. EZRGB feels that the community should have a PC-based player that is easy to use, and will host cloud-based playback functionality for future EZPlayer releases.

Because this project is AGPL, the full source code is available and the build process is documented.

• Windows (with git bash or WSL) and C++ compiler, MacOS, or Linux with the appropriate dev packages installed
• Node.js ≥ 22 (get from nvm if needed)
• pnpm
• Python 3 + build tools (for native modules)
• Git

git clone https://github.com/ezpixelplayer/ezplayer.git
cd ezplayer
pnpm install
pnpm build          # Build for current platform
pnpm build:win      # Build for Windows
pnpm build:mac      # Build for macOS
pnpm build:linux    # Build for Linux

Then, fix whatever went wrong :-).

Your main build will appear in apps/ezplayer-ui-electron/release.

Your various files (song lists, playlists, schedules) end up in your show folder in .json files. You might want to back those up.