Your prop works from xLights. Good—save that setup before moving show playback to Falcon Player. The next job is to get the rendered sequence, FPP outputs and actual wiring working together.
We recommend handing over one short test sequence first. Once that works, transfer the rest. This guide assumes FPP is installed and reachable; use the official quick start and your hardware instructions for a fresh installation. Menu names can vary by release.
Save what already works
Back up the xLights show folder and note the working controller addresses, protocols, ports and pixel counts. Label each enclosure with a name that matches your setup notes. If you have several FPP devices, give them distinct hostnames.
Pick one prop you can see easily, perhaps a CoroWorks character or a short EVO pixel test string. Use a brief sequence with unmistakable colors and movement. A complicated song makes a poor first connection test.
Decide what each box is supposed to do
The main FPP player runs the show and schedule. An FPP remote participates in a synchronized arrangement under another player's control. A device may drive local cape or hat outputs, send data to separate network controllers, or do both.
Write down the role before copying settings. For example, an FPP player sending network data to a Mattos MD1500 Baldrick8 needs an output path to that controller. That is a different arrangement from using only local pixel outputs on the player hardware. Check the receiving controller's supported protocol and configuration.
For synchronized remotes, work through the MultiSync instructions. Each device needs the files and settings required for its particular job.
Render the file you actually intend to play
The .xsq file contains your editable xLights sequence. The .fseq contains rendered playback data. An old FSEQ can still reflect yesterday's addressing even when today's preview looks right. The file glossary explains the difference.
Open the right show folder, render, and save with FSEQ saving enabled. Check the saved file's name and modification time. If you changed the layout or channel assignments, rebuild every affected sequence before transferring it. Review the render-and-save settings if the expected playback file is missing.
Use FPP Connect carefully
Open Tools > FPP Connect in xLights. Match each destination's name and address to the box you mean to update. If a device is missing, confirm network access before using Add FPP with its known address.
Select the intended sequence files, include media where that device needs it and choose a compatible FSEQ format. Model data can also be transferred for model-based testing. The xLights FPP Connect guide describes these choices.
Check the boxes deliberately. Every sequence, media file and output setting does not need to go to every device.
Give each player only the outputs it needs
A player sending E1.31, Art-Net or DDP to network controllers needs the matching network-output configuration. A device using only local outputs does not need all those network outputs enabled just because another device uses them.
Review FPP Connect's UDP Out setting against your plan. Sending every output configuration to every device can create extra transmitters. Also check local output assignments when your hardware uses them. Use the FPP Connect reference and Channel Outputs guide for the relevant controls.
After uploading, open the destination device and inspect its addresses, active outputs, channel ranges and port assignments. A successful transfer tells you the files arrived; the light test proves the rest.
Play manually before adding a schedule
Create a small playlist. Pair the correct sequence and media for musical entries, then confirm the audio output and volume. Stop xLights output and other test sources before playing from FPP.
Watch the beginning, a recognizable section in the middle and the final shutdown. If only the sound is missing, check the media and audio path. If xLights worked but FPP does not, compare the new FSEQ and FPP outputs with your saved working setup. See the playlist reference.
Prove both ends of the schedule
Check the player's clock, time zone, date range, active days, playlist, repeat setting and stop behavior. Sunset scheduling also needs the correct location. Run a short scheduled test while you are there to watch it start and stop. The scheduler guide explains the available stop options.
Then save a recovery copy. FPP's configuration-only backup excludes sequences, music and video, so back those files up too. Keep configuration backups private because they can contain credentials; follow FPP backup and restore.
Write down the device names, addresses, playlist and schedule next to the backup location. That small note is useful when you have to restore a show in a hurry. For help matching the next prop to your setup, start with Mattos Education & Support.
Connect the steps before and after this checklist
If you cannot yet reach the player, start with FPP first connection and network setup. That guide distinguishes a fresh supported installation from hardware supplied with FPP already installed.
Once files and outputs pass here, complete the audio setup and test. If a screen is part of the show, use the video and projector guide to plan the actual display connection and playback path. Test the entire arrangement after a normal restart, then save a fresh backup.
Keep learning
- xLights for Beginners: Set Up and Test Your First Pixel Prop
- How to Import an xLights Model and Match Your Prop Wiring
- xLights Controllers, Ports, Channels, and Universes Explained
Browse all Mattos education and support guides.
Reviewed October 29, 2026.
Put the guide to work
Once playback works, use Run Your Baldrick Show Every Night with FPP for the playlist, clock, schedule and restart checks. For controller setup and troubleshooting, start at the Baldrick Learning Center.
