After our first EZPlayer video, one of the biggest questions we received was: Does Remote Falcon work with EZPlayer? The answer is yes! In fact, setting up Remote Falcon with EZPlayer turned out to be much easier than I expected.

In this guide, we'll walk through connecting Remote Falcon to EZPlayer, choosing which songs your visitors can request, setting when viewer control is available, and testing an actual song request on the display. By the end, you'll have everything you need to start letting visitors interact with your show from their phones.

1. What Is Remote Falcon and EZPlayer?

Before connecting the two, it helps to understand what each one does.

EZPlayer is the show player running your display. It plays your sequences, manages playlists and schedules, and sends the data out to your lights. Once your sequences are prepared and loaded into EZPlayer, it can handle running your nightly show.

Remote Falcon adds a way for the people visiting your display to interact with that show. Visitors can scan a QR code or open your Remote Falcon viewer page on their phone, see the songs you've made available, and request the one they want to watch. That request is then sent to your show player.

When you use Remote Falcon with EZPlayer, the two have different jobs:

EZPlayer = the show player

Remote Falcon = the visitor experience

For example, maybe a visitor really wants to see All I Want for Christmas Is You, but it's buried deep in your playlist. Instead of waiting around hoping it plays, they can select it from your Remote Falcon page. EZPlayer receives that request and can play it after the currently playing sequence finishes.

Remote Falcon offers many more features and customization options than we're going to cover here. For this guide, we're keeping things simple: connect Remote Falcon with EZPlayer, give visitors a selection of songs, and make sure their requests actually play on the display.

2. Prepare EZPlayer for Remote Falcon

Before connecting Remote Falcon, make sure your show is ready to run normally in EZPlayer. Your sequences should already be rendered, and EZPlayer should be pointed to the correct folders for your display.

Start by opening Settings and checking your Show Folder. If you keep your audio files in a separate location, you can also use Choose Media Folder to tell EZPlayer where to find your music. This was one of the most common questions after our previous EZPlayer video, and the newer option makes managing music stored outside your show folder much easier.

Adding Your Songs

EZPlayer now includes a Bulk Import option that can save quite a bit of time when you're adding multiple sequences. Instead of entering every song individually, select Bulk Import and bring your prepared sequences into EZPlayer together.

During our test, Bulk Import flagged one static sequence because it didn't have a matching MP3. Since a static sequence doesn't necessarily need music, we simply added that sequence manually. At the time of recording, the EZPlayer developers were aware of this issue and were working on improving how Bulk Import handles sequences without audio.

Create Your Remote Falcon Playlist

Once your songs are imported, create the playlist you want to make available to Remote Falcon. For our test, we created a playlist called Fan Playlist Selections.

This playlist doesn't necessarily have to match the playlist you normally run each night. You might have dozens of sequences in your library but only use a smaller selection in your regular show. Remote Falcon gives us the opportunity to make some of those additional songs available for visitors to request without putting every sequence into the nightly rotation.

With your songs imported and your Remote Falcon playlist created, EZPlayer is ready to make the connection.

3. Connect Remote Falcon to EZPlayer

With your songs imported and your playlist ready, it's time to connect Remote Falcon to EZPlayer. Fortunately, this part of the setup is surprisingly simple.

In EZPlayer, go to Settings → Viewer Control. Under Viewer Control Type, select Remote Falcon. You'll notice EZPlayer also has a built-in Viewer Control option in development, but for this tutorial we're sticking with Remote Falcon.

EZPlayer will now ask for your Remote Falcon Show Token. This token is what connects your Remote Falcon account to EZPlayer.

Find Your Remote Falcon Show Token

Head over to RemoteFalcon.com and sign into your account. Once you're on the dashboard:

1. Enable Viewer Control using the slider at the top of the page.
2. Select Account Settings from the menu.
3. Open Account.
4. Find Show Token.
5. Click Copy Show Token.

You don't need to manually type or even display the token. Simply copy it, return to EZPlayer → Settings → Viewer Control, and paste it into the Remote Falcon token field.

That's the basic connection complete. Next, we need to tell EZPlayer when Remote Falcon can accept requests and which playlist your visitors are allowed to choose songs from.

4. Choose When and What Visitors Can Request

Once Remote Falcon and EZPlayer are connected, the next step is deciding when visitors can make song requests and which songs they can choose from.

Under Viewer Control, select Add Schedule Entry. This gives you control over the days and times Remote Falcon is available. You can make viewer requests available every day, only on certain days, or during specific hours.

This can be especially useful for displays with heavy traffic. For example, if Friday and Saturday evenings are your busiest times, you may want to limit viewer requests during those hours to help keep cars moving. On slower nights, you could give visitors more freedom to choose what they want to see.

Next, select the playlist you want Remote Falcon visitors to access. In our example, we created Fan Playlist Selections specifically for this purpose. This playlist can contain your regular show songs, additional sequences that aren't in that night's rotation, or a combination of both.

Once you've selected your days, times, and playlist, click Add Schedule Entry.

The easiest way to think about these settings is:

Schedule = WHEN visitors can make requests.
Playlist = WHAT visitors can request.

5. Test Remote Falcon with EZPlayer

With everything connected, it's time to see if Remote Falcon with EZPlayer actually works.

Head back to your Remote Falcon dashboard and give it a moment to update. You should see your active sequences listed. From there, select View Public Page to open the same page your visitors will see when they access your show from their phones.

Your available songs should now appear on the page. Select one just as a visitor would and submit the request. In our test, we selected Jingle Bells Batman Smells, and Remote Falcon immediately added it to the queue.

EZPlayer receives the request while continuing to play the current sequence. Once that sequence finishes, it checks Remote Falcon for the next request and begins playing the selected song.

And just like that, Remote Falcon is controlling song requests through EZPlayer.

Before using it during an actual show, try several requests yourself. Test the public page from your phone, make sure the correct songs play, and confirm everything works the way you expect from the same perspective as someone visiting your display.

6. A Better Way to Use Your Sequence Library

One of the things I didn't really consider before using Remote Falcon with EZPlayer was how it could change the way I build my nightly playlists.

Over the years, it's easy to collect 20, 30, 40, or even more sequences. But having that many sequences doesn't mean they all need to play every night. You might create shorter playlists for different nights, build themed playlists, or simply limit the number of songs playing to help keep traffic moving through your display.

With Remote Falcon, those other sequences don't have to sit unused. You can keep a larger selection of songs available in EZPlayer and allow visitors to request them through your Remote Falcon page, even when they aren't part of that night's regular rotation.

This gives you the best of both worlds: a shorter, manageable nightly show with a much larger library available for visitors who want to request something different.

That's something I hadn't really considered before trying Remote Falcon. After seeing how easily it worked with EZPlayer, it's definitely a feature I'm considering adding to my own holiday light show.

Continue Learning

EZPlayer for xLights - Learn more about setting up and running our xLights show with EZPlayer

How to Build Your First Pixel Controller - Working on your show hardware? Follow our Beginner-friendly controller build guide

Controller Output Labels: Methods and Organization - See the labeling methods we've learned through years of display building

DIY Pixel Mini Mega Tree and Star - Build our inexpensive 200 pixel Mini Mega Tree with Star.

The post How to Use Remote Falcon with EZPlayer appeared first on Pixel Pro Displays LLC.

A DIY Pixel Mini Mega Tree is a smaller version of the large pixel mega trees commonly used as centerpieces in animated Christmas light displays. It uses vertical strands of individually controlled RGB pixels arranged around a center mast to create the familiar Christmas tree shape.

Calling this one a mini tree might be stretching the definition a little. At around six feet tall, it's nearly as tall as I am! That's why I tend to call it a Mini Mega Tree. It's large enough to create some great effects in xLights, but still small and lightweight enough to move, store, and use as an accent prop in different areas of the display.

From 150 Pixels to 200 Pixels

I originally built these trees back around 2015 using six strips with 150 total 5V pixels at 3-inch spacing. Pixels were more expensive at the time, so spreading them farther apart allowed me to build a larger prop without using as many pixels.

Eventually, my display changed and these trees were removed from the show. They went into storage around 2017 and hadn't been used since. Instead of throwing away a perfectly good project, I decided it was finally time to bring them back and improve the original design.

The redesigned DIY Pixel Mini Mega Tree now uses eight vertical strips with 200 total 5V pixels at 2-inch spacing. The additional strips and closer pixel spacing give the tree considerably more density than the original version while still allowing me to reuse many of the parts I already had.

I also added a 50-pixel Bethlehem Star to the top, turning a fairly simple pixel tree into a more complete Christmas display prop.

A Simple Pixel Prop You Can Build Yourself

One of my favorite things about this project is that the frame doesn't require anything particularly complicated. The basic structure is made from PVC pipe and fittings, a few screws, bungee balls, and a short piece of EMT used to support the star.

Even better, much of what I needed was already sitting in my shop.

That's really the bigger lesson behind this build. As our displays change over the years, it's easy to end up with old props and good components packed away in storage. Sometimes, instead of buying everything new, you can take what you already have, make a few improvements, and turn it into a prop you're excited to put back into your show.

In the next section, we'll look at the original Mini Mega Trees and what I wanted to change before rebuilding them.

DIY Pixel Mini Mega Tree Build Specifications

2. Rebuilding My Original Pixel Mini Mega Trees

This DIY Pixel Mini Mega Tree project actually started many years ago. I originally built four of these trees around 2015 for my Christmas display. At the time, each tree used six vertical strips with 150 total 5V pixels spaced approximately three inches apart.

The original design worked, but it wasn't perfect.

Each pixel strip hung from screws mounted around the topper. At the bottom, I used ground anchors to stretch the strips out and hold them in place. The idea was simple and inexpensive. However, the anchors had one major problem: wind could pull them out of the ground.

The trees did their job, but I could always see some of these strips sagging. Eventually my display changed.

Nine Years in Storage

Around 2016 and 2017, the front of my light show was redesigned. As a result, these Mini Mega Trees no longer had a place in the new layout. I packed them away, thinking I would eventually find another use for them.

Instead, they sat in storage.

And sat.

And sat some more.

The pixels hadn't even been powered on for roughly nine years when I finally pulled the trees back out for this project.

Fortunately, there was no reason to throw everything away and start over. The PVC structure, pixel strips, and many of the other components could still be reused.

Improving the Original DIY Pixel Mini Mega Tree

This time, I wanted to fix some of the weaknesses of the original design, simplify the setup, and also improve how the tree looked.

The biggest change was pixel density.

The original trees had six strips and 3-inch pixel spacing. The rebuilt version uses eight strips with 2-inch spacing, bringing each tree up to 200 pixels. This gives xLights more pixels to work with and creates a fuller-looking prop.

Previously, the tree was 6 strips wide by 25 pixels tall. That was roughly 75 inches in length

Pulling the pixels from the strips and re-pushing them at 2-inch spacing makes a whole lot of difference. Then increasing the width to 8 strips, was like icing on the cake.

I also changed how the strips attach at the bottom. Instead of relying on individual ground anchors, the new design uses a PVC base with two arms. Bungee balls connect the pixel strips to those arms, helping maintain the shape and tension of the tree.

Finally, I added a 50-pixel Bethlehem Star above the tree to finish the prop.

The result is still based on my original design, but it's a more taut and neat version of it.

More importantly, rebuilding these trees allowed me to take something that hadn't been part of my display in years and give it another purpose.

🎥 Watch the Complete DIY Pixel Mini Mega Tree Build

Next, we'll look at the parts and materials used to build the updated DIY Pixel Mini Mega Tree.

3. What You'll Need to Build a DIY Pixel Mini Mega Tree

One of the things I like most about this DIY Pixel Mini Mega Tree is how simple the basic frame really is. You don't need a complicated metal structure or a collection of specialty hardware to build one.

In my case, I was able to reuse many of the parts from the original trees. However, most of the materials are inexpensive items you can find at a local hardware store or order online.

DIY Pixel Mini Mega Tree Materials

For each tree, I used:

• 3/4-inch PVC pipe for the center mast and base arms
• 3/4-inch PVC Cross Connector fitting
• 2-inch to 3/4-inch PVC reducer for the topper
• Eight pixel mounting strips
• 200 5V pixels at 2-inch spacing
• Eight screws for the strip attachment points
• White bungee balls
• 50-pixel Boscoyo Bethlehem Star
• Approximately 2 feet of 1/2-inch EMT for the star support
• Zip ties for attaching the star to the EMT
• Screws for securing the star support to the tree

You'll also need a few basic tools, including a tape measure, marker, drill, and something to cut the PVC. I used PVC cutters, which made it easy to make the relatively small number of cuts required for each tree.

Reuse What You Already Have

Before buying everything on the list, take a look around your shop.

The 5V pixels used in my stars were leftovers from other projects. I already had sections of EMT cut to the length I needed, and much of the PVC structure came directly from my original trees.

That's part of what made rebuilding these props worthwhile. You may already have pixels, PVC, mounting strip, wire, or other hardware left over from previous projects that can be put back to work.

Even if you're starting from scratch, the frame itself uses only a handful of basic components.

With our materials together, the next step is getting the measurements for the DIY Pixel Mini Mega Tree and cutting the PVC for the frame.

4. DIY Pixel Mini Mega Tree Measurements

Before building the remaining trees, I took one of my completed DIY Pixel Mini Mega Trees apart so I could measure each piece and duplicate the frame. If you're working from an existing prop like I was, this is an easy way to recreate a design that you already know works.

Ironically, once I started taking everything apart, I discovered that I had written the measurements directly on the PVC years ago. I had completely forgotten about that! At least tearing it apart gave me a chance to double-check everything and show you how the frame goes together.

Center Mast Measurement

The main center mast measures 50 1/2 inches long.

Since I already had one center mast cut to the correct length, I used the original piece as a template. I simply placed it alongside the new PVC, marked the cut, and duplicated the same measurement for each additional tree.

Using an existing piece as a template is also a great way to keep several identical props consistent.

Bottom Arm Measurements

After cutting the 50 1/2-inch center mast, I used the remaining PVC to make the two arms at the bottom of the tree.

Each bottom arm measures:

10 inches long

The two 10-inch arms connect to either side of a 3/4-inch PVC T fitting, while the center mast extends vertically from the remaining opening in the T.

Those arms provide the attachment points for the pixel strips at the bottom of the tree. Instead of staking each strip individually into the ground like I did with my original design, the rebuilt tree uses bungee balls to connect the strips to this PVC base.

Basic PVC Cut List

For each DIY Pixel Mini Mega Tree, the primary PVC pieces are:

• 1 center mast: 50 1/2 inches
• 2 bottom arms: 10 inches each
• 1 PVC Cross Connector: 3/4 inch
• 1 topper: 2-inch to 3/4-inch PVC reducer

The star uses a separate piece of EMT, which we'll cover when we add the Bethlehem Star later in the build.

Once the PVC pieces are measured and cut, assembling the basic frame only takes a few minutes. Next, we'll connect the center mast, base arms, and topper to create the structure for our pixel strips.

5. Building the PVC Mini Mega Tree Frame

With all of the PVC cut to size, assembling the frame for the DIY Pixel Mini Mega Tree is pretty simple. There are only a few pieces, and the frame can be put together without building a complicated support structure.

Start with the 3/4-inch PVC cross connector at the bottom. The 50 1/2-inch center mast slides into the top of the cross, while the two 10-inch PVC legs extend from the left and right sides.

The fourth opening in the cross faces downward. This gives us a true four-way cross rather than the PVC T fitting I mistakenly called it a few times in the video.

Adding the PVC Topper

At the top of the center mast, install the 3/4-inch to 2-inch PVC coupler.

The orientation matters:

• 3/4-inch side faces down and connects to the center mast.
• 2-inch side faces up and becomes the wider portion of the topper.

Around this wider section, I use eight screws spaced around the coupler. Each screw becomes an attachment point for one of the eight pixel mounting strips.

You don't need to make the spacing absolutely perfect. However, keeping the screws reasonably even around the topper helps spread the strips and gives the finished tree a more consistent shape.

Why I Changed the Bottom of the Frame

My original Mini Mega Trees didn't have the two PVC legs we're using today. Instead, the pixel strips came down from the topper and were stretched outward using individual stakes in the ground.

It worked, but wind could loosen or pull those stakes out.

The updated DIY Pixel Mini Mega Tree keeps the bottom attachment points as part of the prop itself. The two 10-inch PVC legs give me a place to secure the strips with bungee balls while also helping keep the tree's shape consistent.

It also makes the prop easier to move and store. Instead of recreating the shape every time I set it up, the structure stays together, with extension cords, even when stored in the off-season.

Don't Glue Everything Together Yet

One thing to consider before reaching for the PVC cement is storage.

A permanent PVC frame may be convenient during show season, but it can become awkward when it's time to put everything away. Leaving some connections removable lets you break the DIY Pixel Mini Mega Tree into smaller pieces for storage or transportation.

How permanent you make the frame is really up to you and how you plan to use the prop. I have storage that will fit my tree, complete without having to break it down at the end of the season. Your results may vary.

Once the center mast, cross connector, bottom legs, and topper are assembled, the basic PVC frame is complete.

Now we can start turning that simple PVC frame into a pixel tree by adding the eight mounting strips.

6. Adding Pixel Strips and Wiring the Tree

Now that the PVC frame is assembled, it's time to add the pixel mounting strips and start giving our DIY Pixel Mini Mega Tree its shape.

For my rebuild, I'm using eight vertical strips with 200 total 5V pixels. Each strip contains 25 pixels at 2-inch spacing. That gives me four strips on the left side of the tree and four on the right.

However, this is also the point in the build where you can make this tree your own.

Attaching the Pixel Strips

At the top of the tree, each mounting strip attaches to one of the eight screws installed around the PVC coupler. At the bottom, I use white bungee balls to connect the strips to the PVC base.

The bungee balls do two things. First, they hold the strips in position. More importantly, they provide some tension while still allowing the strips to move slightly instead of being pulled completely rigid.

When attaching the strips, I like to work back and forth across the tree rather than completely finishing one side first. This helps keep the tension more balanced as the tree begins taking shape.

You want the strips tight enough to stay straight. Move your bungee ball to a lower hole on the strip if it's too hard to attach around the PVC arm. The goal is a clean tree shape without putting unnecessary stress on the mounting strip, pixels, or PVC frame.

Wiring My 200-Pixel Mini Mega Tree

I'm using two strings of 100 5V pixels for this build. Each controller output runs one half of the tree.

From the front view, Output 1 starts at the bottom left side of the tree. The pixels travel up the first strip, cross over at the top, travel down the second strip, cross at the bottom, travel up the third strip, and finally cross at the top and travel down the fourth strip.

That gives us one continuous 100-pixel zigzag:

Up → Down → Up → Down

Output 2 follows the same pattern on the right side of the tree. It begins near the center mast at the bottom and zigzags across the remaining four strips.

This gives each controller output:

4 strips × 25 pixels = 100 pixels

And the complete DIY Pixel Mini Mega Tree has:

8 strips × 25 pixels = 200 pixels

DIY Pixel Mini Mega Tree Wiring Diagram

This is much easier to understand when you can actually see it:

The diagram shows the tree from the front and identifies the START and END of both 100-pixel strings. This will also become important when we configure the tree in xLights later.

You Don't Have to Build Mine Exactly Like Mine

Here's where I want to emphasize something: 200 pixels isn't a requirement.

It's simply what I'm using.

If you're building your own DIY Pixel Mini Mega Tree, this is a great place to adjust the design based on the pixels, mounting strips, controller outputs, and supplies you already have.

For example, instead of eight strips, you could build the tree with 10 strips of 25 pixels. That would increase the tree to 250 pixels and give you additional density around the tree.

You could take it even further.

With approximately 52-inch mounting strips and 1-inch pixel spacing, you could use 10 strips with 50 pixels on each strip. Now you've created a much denser 500-pixel Mini Mega Tree using essentially the same basic PVC frame design.

Of course, adding more pixels also changes your power and controller requirements. Plan your controller outputs, power needs, pixel voltage, and wiring for the version you decide to build.

Build the Tree That Fits Your Display

That's one of the nice things about a simple DIY design like this. The PVC frame gives you the basic structure, but it doesn't lock you into one particular pixel count.

You can change the number of strips. You can change the pixel spacing. You can increase the pixel density. You can also adapt the wiring pattern to match the controller outputs you have available.

My version uses eight strips, 200 5V pixels, and two 100-pixel controller outputs because that's what made sense for the parts I already had.

Your DIY Pixel Mini Mega Tree doesn't have to be identical to mine. You may chose to use 12v pixels and run 200 pixel on a single output.

Use this build as the starting point, then adjust it to fit your display, your equipment, and the look you want to create.

7. Adding the Pixel Star

With the 200 pixels installed on the tree, the next step is adding the finishing touch to our DIY Pixel Mini Mega Tree: the star.

For this build, I'm using a Boscoyo Bethlehem Star with 50 5V pixels. I had several of these stars already assembled and sitting in storage, so once again, this was a good opportunity to reuse something I already owned instead of buying another prop. The star also gives the Mini Mega Tree a more finished look and adds another model we can control separately in xLights.

Building the Star Support

The star needs to sit above the PVC topper, so I use a piece of 1/2-inch EMT approximately 2 feet long as the support.

The EMT runs vertically behind the tree and extends above the PVC center mast. I attach the Bethlehem Star to the EMT using zip ties, which keeps the star centered while still making it easy to remove later.

We start by drilling 2 holes into the center of the star. These mounting holes will be used to route the zip ties around the EMT.

The EMT is then secured to the PVC frame with screws (not shown in the video). We will drill 2 holes in the coro star and secure it to the 1/2 inch EMT using a zip tie. Another zip tie secures the EMT lower on the coro star, through the flutes in the coro material. Using two attachment points keeps the support from rotating and helps the star remain upright.

Before tightening everything completely, step back and look at the tree from the front. This is the easiest time to make small adjustments and get the star centered over the EMT.

Wiring the 50-Pixel Star

The Bethlehem Star uses 50 additional 5V pixels, bringing the complete prop to:

200 pixels in the tree + 50 pixels in the star = 250 total pixels

However, I treat the star as its own model rather than simply making it another part of the Mini Mega Tree.

That gives me much more flexibility when sequencing in xLights. The tree and star can work together when I want them to, but I can also apply completely different effects to each model.

Keep the Star Removable

Just like the PVC frame, I like having the ability to take things apart.

Perhaps in the future, a new star will be created and fit this build? How easy will it be to swap one star for a new style when it is attached to the same EMT?

A six-foot tree is one thing to store. A six-foot tree with a star permanently sticking another couple of feet above it becomes much more annoying.

Using EMT, screws, and zip ties gives me a simple support system without permanently attaching everything together. When show season is over, I can remove the star and break the prop down into pieces that are much easier to store.

Beginner Tip: Don't overlook storage when you're designing a new prop. Something that's easy to assemble in August can become a giant pain when you're trying to put the entire display away in January.

While the original prop was a very easy prop to setup, it still took time to assemble and take it down each season.

The Star Is Optional

Just like the pixel count we discussed in the previous section, you don't have to build your DIY Pixel Mini Mega Tree exactly like mine.

You could use a different pixel star, change the size, use another mounting method, or leave the star off completely. If you already have an unused star in your collection, you may even be able to adapt it to this design.

For me, the 50-pixel Bethlehem Star was already available, fit the size of the tree nicely, and gave another old prop a reason to come back out of storage.

With the physical build complete, we can move over to the computer.

Next, we'll create the DIY Pixel Mini Mega Tree in xLights and make sure the software matches the way we actually wired the pixels.

8. Setting Up the DIY Pixel Mini Mega Tree in xLights

With the physical build complete, it's time to move into xLights. This is where the way we wired our DIY Pixel Mini Mega Tree becomes especially important.

The xLights model needs to match the physical direction of the pixels on the actual tree. Fortunately, the zigzag pattern we used during the build is easy to reproduce once you understand how the two strings are arranged.

Creating the Mini Mega Tree Model

In the xLights Layout tab, add a tree model and position it where you want it in your display.

For my tree, I'm using:

• 2 strings
• 100 pixels per string
• 4 strands per string
• 25 pixels per strand
• 200 total pixels

Remember, each 100-pixel string travels across four vertical strips:

Up → Down → Up → Down

The second 100-pixel string repeats that same pattern across the other four strips. This allows our xLights model to match the way the pixels are physically installed on the tree.

Use Wiring View to Check Your Work

One of the easiest ways to verify the model is with Wiring View in xLights.

Right-click the tree model while in the xLights Layout Tab and open Wiring View. This lets you see the path xLights expects the pixels to follow through the prop.

Keep in mind that Wiring View initially defaults the display to show the tree from the back side of the prop.

You can switch it to the front view, by right-clicking and selecting that option. Because the tree is shown from the front during the build, switching Wiring View to the front makes it much easier to compare the xLights model with the physical wiring.

Look at where the first pixel begins and follow the path through each strip. It should match the physical tree.

If xLights thinks your pixels travel one direction while the actual pixels travel another, effects may appear backwards, reversed, or jump between sections of the tree unexpectedly.

Adding the Bethlehem Star in xLights

The star is created as a separate model.

I'm using the existing xLights model for the Boscoyo Bethlehem Star, listed as the Boscoyo Beth Star 2. Since the physical star contains 50 pixels, we can configure it separately from the 200-pixel tree and position it directly above the tree model in our layout.

This model is located in the Model Downloads, under the Boscoyo section.

Keeping the star separate gives us much more control when sequencing. We can apply an effect across the tree while doing something completely different on the star, or group them together when we want effects to work across the complete prop.

Assigning the Controller Outputs

For my test setup, the tree and star use three controller outputs:

Output 1 — 50-pixel Bethlehem Star
Output 2 — First 100-pixel tree string
Output 3 — Second 100-pixel tree string

Once the models are assigned to the correct ports, the controller configuration can be uploaded and we're ready to begin testing the physical prop.

If you modified the design from the previous section by adding more strips or increasing the number of pixels, your xLights configuration will naturally be different. That's perfectly fine.

The important rule is simple:

Build the xLights model to match the tree you actually built... not necessarily the tree I built.

Check the Model Before Sequencing

Before spending time creating effects, take a few minutes to make sure the model behaves correctly.

Run a simple Bars effect across the tree and watch the physical pixels. Look for effects moving in the correct direction and verify that all eight strips behave the way they do in the xLights preview.

Watch Content: Testing your Props Using xLights Sequencer

This quick test can catch a wiring or model configuration problem before it becomes much more confusing later.

Once the physical DIY Pixel Mini Mega Tree matches what we're seeing in xLights, we're ready for the fun part.

Let's put some effects on it and see what 200 pixels at 2-inch spacing can actually do.

9. Testing the Finished DIY Pixel Mini Mega Tree

With the physical tree built and the xLights model configured, there's only one thing left to do: turn on the lights and see how it looks.

This is also where we find out whether the extra work we put into increasing the pixel density was worthwhile.

For this DIY Pixel Mini Mega Tree, we're testing 200 5V pixels at 2-inch spacing, with eight strips spread across the front of the tree. The Bethlehem Star adds another 50 pixels above it.

Start with a Simple xLights Test

Before worrying about how the tree looks in a finished sequence, start with a few simple effects in xLights.

This gives you an opportunity to check that:

• Both 100-pixel strings are responding.
• All eight strips are working.
• The zigzag wiring matches the xLights model.
• Effects travel across the tree in the correct direction.
• The Bethlehem Star responds as its own model.
• The physical tree matches what you see in the xLights preview.

If something looks wrong, this is the time to fix it.

A simple effect moving across the tree makes it much easier to spot a reversed strand, incorrect starting location, or xLights configuration problem than trying to troubleshoot it in the middle of a complicated sequence.

How Does 2-Inch Pixel Spacing Look?

This was one of the things I really wanted to see when I rebuilt these trees.

The original version used pixels at approximately 3-inch spacing. That helped keep the pixel count and cost down when I first built them, but we've learned a lot over the years about how much difference additional pixel density can make.

The rebuilt DIY Pixel Mini Mega Tree uses 2-inch spacing with the strips positioned fairly close together at the bottom. Once we started playing effects across it, I was really happy with the amount of definition we were getting from only 200 pixels.

For a prop this size, the effects looked much more detailed than they did on the original trees.

Test the Tree with a Sequence

After verifying that the basic wiring and model are correct, load or import the effects from one of your existing xLights sequences. Render and "output to lights" and see what the tree actually does with real effects.

This is the fun part!

Effects that sweep across the tree, move vertically, change color, or use the individual strands will quickly show you what the additional density adds to the prop.

It's also a good opportunity to experiment with the star. Since the Bethlehem Star is its own xLights model, you can let it complement the effects on the tree instead of simply copying them.

[

Don't Skip the Test Before Installation

I always recommend testing a new or rebuilt prop before putting it out in the yard.

It's much easier to fix a bad extension cord, incorrect controller assignment, or xLights model setting while the tree is sitting in the shop than after you've installed it outside.

In this case, testing was even more important because many of these components had been sitting unused for years.

Once everything is responding correctly and the physical tree matches the xLights preview, the DIY Pixel Mini Mega Tree is officially ready to return to the show.

And for a prop that spent nearly nine years packed away, I'd say that's a pretty good comeback.

10. Reuse What You Already Have

One of the biggest lessons from this DIY Pixel Mini Mega Tree project really has nothing to do with PVC, pixels, or xLights.

It's about looking at what you already have before buying something new.

We spend a lot of money building our Christmas light displays. Over time, we replace props, redesign areas of the yard, change controllers, and move on to newer ideas. However, that doesn't always mean the things we've stopped using are no longer useful.

These Mini Mega Trees are a perfect example.

An Old Prop Doesn't Have to Be a Dead Prop

My original trees hadn't been part of the display since around 2017. For nearly nine years, they sat packed away because I didn't have a good place to use them.

The pixels were old. The design wasn't as dense as I wanted. The original ground-anchor system had problems. Still, most of the components were perfectly usable.

Instead of throwing everything away, I looked at what I didn't like about the original design and asked a much better question:

What can I change to make these useful again?

That led to the redesigned PVC base, two additional pixel strips, closer pixel spacing, bungee-ball attachments, and the addition of a Bethlehem Star.

Suddenly, something that had been sitting in storage for years became a prop I was excited about again.

Check Your Storage Before You Go Shopping

If you've been in this hobby for a few years, there's a chance you have your own version of this project hiding somewhere in a storage tote like I did.

Maybe it's an old Mini Tree. Maybe you have unused pixel mounting strips, an extra star, leftover pixels, PVC from another build, or an entire prop that disappeared from your layout several seasons ago.

Before ordering everything new, go look through those boxes.

You may already have most of what you need for your next project.

For this DIY Pixel Mini Mega Tree, I reused 100 percent of the original components. Strips, pixels, PVC, tools, and more... I also used leftover 5V pixels from other projects for the stars and EMT pieces that were already cut and sitting on my service cart under my Halloween pumpkins.

That kept the cost of rebuilding these trees extremely low.

Improve It Instead of Simply Rebuilding It

Reusing an old prop doesn't mean you have to recreate it exactly the way you originally built it.

Actually, I think that's where some of the fun begins.

You've already had years to learn what worked and what didn't. You've probably learned new construction techniques. Pixels and controllers have changed. Your xLights skills have improved. You may even have tools today that you didn't own when the original prop was built.

Use that experience.

My rebuilt DIY Pixel Mini Mega Tree isn't simply the 2015 version put back together. It's the version I would rather have today.

And that's really the point of this project.

Sometimes the next great addition to your display isn't something you need to order.

It may already be sitting in a tote in your shop, waiting for you to give it another chance.

11. Final Thoughts

Building this DIY Pixel Mini Mega Tree turned out to be more than just another weekend project. It gave me a chance to take something I built years ago, look at it with everything I've learned since then, and turn it into a prop that I'm excited to use again.

The basic design is intentionally simple. A PVC frame, pixel mounting strips, bungee balls, 5V pixels, and a star are really all it takes to put one together. You don't need an elaborate frame or expensive specialty hardware to build a Mini Mega Tree that can produce some great effects in xLights.

My version uses eight strips with 200 pixels at 2-inch spacing, plus a 50-pixel Bethlehem Star. However, as we discussed throughout this build, those numbers aren't rules. They're simply what worked for the materials I had available.

Make the Project Your Own

If you want more density, add more strips. If you want closer pixel spacing, use more pixels. If you already have a different star, figure out a way to mount it. If your controller setup works better with a different wiring pattern, design your xLights model around the way you choose to build the physical tree.

That's one of the best parts of building your own props.

You can take the basic idea and modify it to fit your display.

The important thing is to plan your pixel direction, controller outputs, and xLights model before everything is permanently assembled. As long as the physical prop and the xLights model agree with each other, you have plenty of room to get creative.

Give an Old Prop Another Chance

For me, though, the most satisfying part of this project is seeing these trees running again.

They were built around 2015, removed from the display a couple of years later, and then spent nearly nine years packed away. Now they're rebuilt with better pixel density, a better mounting system, a new star on top, and a new purpose in the show.

If you've been setting up your Christmas display for a while, I'd encourage you to take a look through your own storage before planning your next purchase.

You might have an old prop you've forgotten about. You might have leftover pixels, mounting strips, PVC, stars, or other parts from previous projects.

Pull them out.

Look at them with fresh eyes and ask yourself what you could do differently today.

Sometimes building something new doesn't mean starting from scratch. Sometimes it means taking something you already have and making it better than it was before.

I hope this DIY Pixel Mini Mega Tree gives you an idea for your own display... and maybe inspires you to bring one of your forgotten props back to life.

Continue Learning

How to Set Up a Mega Tree in xLights
Learn how strings, strands, starting locations, and zigzags work when creating your xLights tree model.

How to Build Your First Pixel Controller
Follow our beginner-friendly Baldrick 8 controller build from start to finish.

How to Build the RGB2Go Octa8 Controller: A Beginner's Guide
Build the RGB2Go controller we used while testing projects like this Mini Mega Tree.

Controller Output Labels: Methods and Organization
See how years of trial and error changed the way I label and organize my pixel controllers.

The post How to Build a DIY Pixel Mini Mega Tree and Star appeared first on Pixel Pro Displays LLC.

Getting started with and using the EZPlayer Setup begins with downloading and installing the player on the computer you'll use to run your light show. EZPlayer is available for Windows, Mac, and Linux, so you can choose the version that matches your show computer.

Head to the EZRGB website and select EZPlayer from the main menu. On the EZPlayer page, you'll find the available downloads along with a Quick Start Guide. Choose the correct version for your operating system, download the installer, and follow the normal installation process.

In our Twinkle Tips Friday demonstration, we're installing EZPlayer on a Windows computer. Depending on your Windows security settings, you may see a warning when opening the installer. In our case, we selected More Info → Run Anyway to continue the installation.

Once installation is complete, open EZPlayer for the first time. Don't worry about adding sequences or creating schedules yet. The first important step is telling EZPlayer where your existing xLights show lives on your computer.

That's what we'll do next.

Before Moving On

Make sure you have:

• EZPlayer installed and running.
• Your existing xLights show folder available on the computer.
• Your rendered .fseq sequence files in your show folder.
• The audio files used by your sequences available in that folder as well.

Keeping your sequence and audio files together will become especially useful when we start adding songs to EZPlayer later in this guide. In the video, EZPlayer was able to locate the matching MP3 automatically when the corresponding FSEQ was added.

Beginner Tip: You aren't moving your xLights show into EZPlayer. Your existing show folder remains the foundation; in the next step, we'll simply tell EZPlayer where to find it.

2. Connecting the EZPlayer setup to Your xLights Show Folder

Once EZPlayer is installed, the next step is connecting it to the xLights show folder you already use. This tells EZPlayer where to find the files it needs to run your display.

From the EZPlayer home screen, click the three-line menu, open Settings, and select Show Folder. Browse to the folder you currently use for your xLights display and select it. Once the change is saved, EZPlayer is connected to your existing show directory.

If you've been using xLights for a while, this should be the same show folder where you save and render your sequences. You don't need to create a second copy of your display just for EZPlayer or move all of your files into a new location.

Why Your Show Folder Matters

Your xLights show folder becomes the common location that helps connect your sequences, audio, and EZPlayer together. In particular, it's a good idea to keep the MP3 audio files used by your show in this folder along with your rendered FSEQ files.

That organization pays off in the next step. When we added an FSEQ file during the video, EZPlayer located the matching MP3 in the show folder automatically. Instead of browsing around the computer looking for the audio file for every sequence, the two files were paired together for us.

Beginner Tip: Connecting your show folder does not change your xLights layout or sequences. You're simply pointing EZPlayer toward the existing files it will use to run your show.

Remember you MUST render your sequences and SAVE them in order to create the FSEQ files. Without the FSEQ files, EZPlayer cannot run the songs.

Check Your Controller Status

After selecting the show folder, return to the main EZPlayer screen. You'll notice a Controller Status area that shows the controllers EZPlayer can see on your network. During our test, the two controllers connected to the small demonstration display appeared online in green.

This gives you a quick check before moving forward. If your controllers are powered on, connected to the network, and visible to EZPlayer, you're one step closer to sending your first sequence out to the lights.

Related Video: xLights Show Folder File Structure

3. Adding Songs and Sequences to your EZPlayer Setup

Now that EZPlayer knows where your xLights show folder is located, it's time to start adding the sequences you want to play. This is where the pieces of your show begin coming together inside the player.

From the Songs page, select Add Song and choose the rendered .fseq file for the sequence you want to add. For a musical sequence, EZPlayer also needs the corresponding audio file. If you've kept your MP3 files inside your xLights show folder as recommended earlier, this process can be surprisingly simple.

During our demonstration, we selected the FSEQ file for Hark! The Herald Angels Sing. Because its MP3 was already stored in the show folder, EZPlayer found and selected the matching audio file automatically. That's one of the reasons organizing your xLights show folder before setting up the player can save time later.

Adding Information About Your Sequences

EZPlayer also gives you several options for organizing and fine-tuning each song. You can add information such as the song title, artist, and sequence vendor, which becomes increasingly useful as your library grows.

There are also a few playback adjustments available. For example, you can adjust the volume of an individual song if its audio is noticeably louder or quieter than the rest of your show. You can also compensate for extra time at the beginning or end of an audio track when needed.

Another useful option is Tags. You might create tags such as Classic, Kids, Patriotic, or any other category that makes sense for your display. Once your song library becomes larger, tags provide a quick way to sort and find the sequences you're looking for.

Adding Sequences Without Music

Not every sequence in a light show needs an MP3.

You may have a static sequence for a tune-to sign, landscaping, background lighting, or another part of your display that you want running without music. EZPlayer can add these FSEQ files as well.

In the video, we added a static sequence called Patriotic Panorama. Because it didn't use an audio track, no MP3 was required. Instead, we manually entered the title and artist information before saving it to the song library.

This makes the Songs area more than just a list of music. It's really your library of playable show content, including both musical and non-musical sequences.

Beginner Tip: Before adding dozens of sequences, take a little time to organize your audio files and decide how you want to name and tag your content. A few extra minutes of organization now can make building and managing playlists much easier later.

Once you've added the sequences you want to use, the next step is putting them together into an actual show.

That's where EZPlayer Playlists come in.

4. Creating Your First EZPlayer Playlist

Once your songs and sequences have been added to EZPlayer, the next step is organizing them into a playlist. A playlist tells EZPlayer which sequences you want to run together as part of your show.

Select Playlist from the main menu, then choose the option to create a new playlist. Give it a name that makes sense for your display. In our Twinkle Tips Friday demonstration, we simply called ours 2026 Christmas Show.

From there, you can begin adding songs from your EZPlayer library to the new playlist. Select the sequences you want and add them to the playlist in the order you'd like them to play.

Organizing Different Playlists

You aren't limited to a single playlist. In fact, creating multiple playlists can be a useful way to change what your visitors see without rebuilding your entire show.

For example, you could create separate playlists for:

• Your regular Christmas show
• Kids' songs
• Christmas classics
• A shorter show for busy nights
• Special events or themed nights
• Static or background sequences

As your sequence library grows, the search function also makes finding a particular song much easier. Instead of scrolling through dozens or eventually hundreds of sequences, start typing part of the song title and EZPlayer will narrow down the available choices.

Your Playlist Determines What Plays

It's helpful for beginners to understand the difference between the Songs and Playlist sections.

Think of the Songs page as your library. It contains the individual sequences you've made available to EZPlayer.

A playlist takes selections from that library and turns them into the group of sequences you actually want to run together.

That means you can keep a large library of sequences inside EZPlayer without having to play every one of them each night. Simply create the playlist you want and add the appropriate songs.

Beginner Tip: Give your playlists clear names. Something like 2026 Christmas Show, Kids Night, or Christmas Classics will be much easier to recognize later than names such as Playlist 1 or New Playlist.

At this point, we've installed EZPlayer, connected our xLights show folder, added our sequences, and created our first playlist.

Now we need to tell EZPlayer when to play it.

That's where the EZPlayer Schedule comes in.

5. Setup Your EZPlayer Show Schedule

With your playlist created, the final step is telling EZPlayer when you want your show to run. This is handled through the Schedule page, where playlists can be assigned to specific dates and times.

One of the first things you'll notice is that EZPlayer uses a familiar calendar-style view. Instead of looking at a long list of scheduled events, you can see your show schedule laid out by date and time. For me, this makes it much easier to visualize when a show is scheduled to start and stop.

To create a schedule, select the date and time on the calendar where you want your show to run. Then choose the playlist you created in the previous step.

Setting Your Show Start and End Times

Next, enter the start time and end time for your show.

For example, if your Christmas display runs from 5:00 PM until 10:00 PM, those times define the window when EZPlayer should run the selected playlist.

If you want the playlist to continue repeating throughout that window, enable the Loop option. Once EZPlayer reaches the end of the playlist, it can start again and continue playing until the scheduled show period ends.

Choosing How Your Show Ends

EZPlayer also includes options that control what happens when your scheduled end time arrives.

For example, you may want the song that's currently playing to finish before the show stops instead of abruptly ending the sequence at exactly the scheduled time. These options give you more control over how the show transitions at the end of the night.

Because EZPlayer is actively being developed, some of the scheduling options, descriptions, and locations within the interface may change as the software is updated. However, the basic scheduling process remains straightforward:

Choose your playlist → Set the start time → Set the end time → Choose your playback options → Save the schedule.

Be Careful When Testing a Schedule

There's one behavior worth knowing when you're experimenting with EZPlayer for the first time.

If you create or update a schedule whose start time is right now, EZPlayer may begin playing the scheduled show immediately. We demonstrated this behavior in the video, so when we wanted to test an automatic start, we scheduled the show a few minutes into the future instead.

That gave us enough time to save the schedule, return to the main Player page, and watch what happened when the scheduled start time arrived.

Beginner Tip: For your first test, schedule a short playlist to begin a few minutes in the future. This lets you confirm that EZPlayer starts the show automatically without waiting until your normal evening show time.

Once the schedule is saved, you can return to the Player page and see when the next show is scheduled to begin. In our test, we could see the upcoming show time displayed before anything started.

Then we waited.

At the scheduled time, EZPlayer started the playlist and our test display came to life.

And that's the point where all five steps we've completed finally come together:

Install EZPlayer → Connect Your Show Folder → Add Songs → Build a Playlist → Schedule Your Show

Next, we can cover that first real-world test and a few things you should check before trusting your new schedule to run the display on its own.

6. Testing Your First Scheduled xLights Show

Now comes the part that really matters: will the show actually start on its own?

For our first EZPlayer test, we didn't want to wait until the normal evening show time. Instead, we created a short schedule that would begin just a few minutes later. This gave us enough time to save the schedule, return to the main Player page, and watch EZPlayer prepare to run the show.

On the Player page, EZPlayer displayed the next scheduled show time, giving us an easy way to confirm that the schedule had been recognized. We could also see the scheduled block on the timeline and verify that the controllers connected to our small test display were online.

Check Your Controllers Before the Show Starts

Before running your first scheduled show, take a moment to look at the Controller Status section. During our demonstration, the controllers connected to the test display appeared in green, indicating that EZPlayer could see them on the network.

This provides a useful final check before the scheduled start time. If the playlist is ready but a controller isn't available, you'll want to investigate that before assuming there's a problem with the schedule itself.

For your first test, verify:

• Your controllers are powered on and connected to the network.
• EZPlayer shows the controllers as available.
• The correct playlist is scheduled.
• Your start and end times are correct.
• Looping is enabled if you want the playlist to repeat.
• Your sequence and audio files have been added correctly.

Let EZPlayer Start the Show

Once everything looks correct, resist the temptation to press Play.

The point of this test is to confirm that EZPlayer can start your xLights show automatically from the schedule you created.

That's exactly what we did in the video. We waited on the Player page as the scheduled start time approached. When that time arrived, EZPlayer automatically started the playlist and began sending sequence data to the controllers.

And, right on schedule, the lights behind me came to life.

That successful test confirmed the complete workflow we'd just created:

xLights Show Folder → Songs and Sequences → Playlist → Schedule → Controllers → Lights

Start Small Before Running Your Full Display

If this is your first time using EZPlayer, I recommend doing exactly what we did: start with a small test.

You don't need your entire Christmas display assembled to learn how the player works. A controller and a few props are enough to verify your files, network connection, playlist, scheduling, and output.

Once that simple test works, you can begin adding more sequences and building the playlists you'll use for your actual display.

Beginner Tip: Don't make your first EZPlayer test opening night of your Christmas show. Create a short test schedule ahead of time and make sure the player, controllers, sequences, audio, and schedule all work together.

For our first scheduled test, they did.

The schedule started, the playlist played, and the lights turned on—exactly when they were supposed to.

7. You're Ready to Run Your Show

At this point, you've completed the basic setup needed to run an xLights display with EZPlayer. You've installed the software, connected your existing xLights show folder, added your sequences and audio, created a playlist, and scheduled that playlist to run automatically.

The entire process can be summed up pretty simply:

Install EZPlayer → Connect Your Show Folder → Add Your Sequences → Create a Playlist → Build Your Schedule → Run Your Show

That's really the goal of this Twinkle Tips Friday tutorial. We aren't trying to explore every setting or advanced feature available in EZPlayer. Instead, we wanted to take a fresh installation and walk through the basic steps needed to get an actual xLights sequence playing on real lights.

Keep Testing Before Show Season

Getting your first scheduled show running is only the beginning. Before relying on any show player for an entire season, spend some time testing it with your own controllers, sequences, playlists, and network.

That's exactly what I've been doing with EZPlayer. At the time this video was recorded, I had been running it for roughly two weeks and testing it with several different controller setups. During those tests, my scheduled shows started as expected, and I was able to successfully run sequences through multiple types of controllers.

Of course, your display may be completely different from mine. That's why I recommend starting small, experimenting with the player, and becoming comfortable with the basic workflow before show season arrives.

EZPlayer Is Still Growing

It's also important to remember that EZPlayer is under active development. Some buttons, menu options, scheduling controls, or other parts of the interface you see in our video may move or change as new versions are released. New capabilities are also continuing to be added.

For that reason, this guide focuses primarily on the workflow rather than documenting every button on the screen. The interface may evolve, but the fundamental process of preparing your show remains easy to understand.

Once you understand that process, adding another song, changing a playlist, or adjusting your schedule becomes much less intimidating.

And most importantly, you've crossed the biggest hurdle:

You went from installing a new show player to watching your xLights sequences run automatically on your display.

The post EZPlayer Setup: How to Run Your xLights Show appeared first on Pixel Pro Displays LLC.

Introduce the idea that every RGB decorator eventually discovers that organizing controllers is just as important as building them.

Mention that this article isn't about buying a fancy label maker—it's about developing a system that makes setup, troubleshooting, and next year's installation easier. Clyde reflects on how his methods evolved over more than a decade, improving a little each season rather than trying to get everything perfect the first time.

Why Controller Output Labels Matter

If you've only built one or two controllers, Controller Output Labels might seem like a small detail. After all, when everything is fresh in your mind, it's easy to remember which pigtail goes to which prop. However, that changes quickly as your display grows and another season rolls around.

Controller Output Labels do much more than identify a cable. They help you set up your display faster, troubleshoot problems with confidence, and make future upgrades much easier. It is possible to remember the output configuration, however, your labels will remove the guessing when it comes time to connect up to your show. A clear labeling system lets you identify each output at a glance.

Just as importantly, good organization saves time every year. During the holiday season, there is always another prop to repair, another sequence to tweak, or another project waiting for your attention. Investing into a reliable and easy to read labeling system for your controllers will save hours of frustration when it's time to set up this season and beyond.

As you'll see throughout this article, my approach to Controller Output Labels has changed dramatically over the past 13 years. Some methods worked well, others didn't last as long as I had hoped, and each new controller taught me something valuable. The goal isn't to build the perfect controller the first time, it's to make each build a little better than the last.

First, let's look at why Controller Output Labels are worth the effort.

📷 Old controller with faded and missing labels

Early Controller Output Labels using tape and printed numbers

These labels were placed on this controller build 2015. Curious where this journey began? Watch the original 2015 controller review video below. You'll see how much my building techniques and Controller Output Labels have evolved over the years.

My First Controller Output Labels

Like many decorators, I didn't spend much time thinking about Controller Output Labels when I built my first controllers. My goal was simple: get the controller finished, save as much money as possible, and put those savings toward buying more pixels. At the time, the labeling system I came up with seemed like a perfectly reasonable solution.

I used a simple handheld label printer to create numbers for each output and attached them to the pigtails with ordinary clear tape. It was inexpensive, quick to install, and worked well enough to identify outputs 1 through 16. For those early builds, that was all I needed.

However, time has a way of exposing the weaknesses in even the best ideas. After years of sitting outdoors through changing weather conditions, the tape began to peel, the labels started falling apart, and what once looked organized became much harder to read. The system had done its job, but it wasn't built to last for the long haul.

Looking back, I don't consider those early Controller Output Labels a mistake. They were simply the best solution I knew at the time. One of the great things about this hobby is that your skills evolve with every controller you build. As you gain experience, you'll naturally discover better materials, cleaner installation methods, and more efficient ways to organize your display.

That's exactly what happened to me. Each new controller became an opportunity to improve on the last one, and over the years those small improvements added up to a much cleaner, easier-to-maintain system.

Transition:

However, time has a way of exposing the weaknesses in every shortcut.

Improving Controller Output Labels with Heat Shrink

Improving Controller Output Labels with Heat Shrink

As my controller builds became more organized, I knew my original Controller Output Labels needed to improve as well. The tape-and-label method had served its purpose, but I wanted something that would stand up to years of outdoor use.

My first upgrade was simple. I continued using my handheld label printer, but instead of taping the labels to each pigtail, I slipped a piece of clear heat shrink tubing over the printed label before wiring the pigtail into the controller. Once the wiring was complete, I slid the heat shrink into place and applied heat to seal everything together.

The difference was immediate. The labels looked cleaner, were protected from the weather, and held up much better through multiple display seasons. For a long time, this became my standard method for creating Controller Output Labels.

Then, another opportunity came along. Ricky from CCL Controllers included professionally printed heat shrink labels with several of the controller build kits he sent me. These labels looked fantastic and gave my controllers an even more polished appearance. They were durable, easy to read, and made each enclosure look professionally finished.

Unfortunately, there was one drawback. Once I used up the supply Ricky had provided, I couldn't easily make more. Creating custom printed heat shrink labels requires specialized equipment that I simply didn't own, and purchasing a dedicated heat shrink printer wasn't practical for the number of controllers I build.

That left me searching for another solution.

Image 1: Close-up of a pigtail with a heat shrink label.

Clear heat shrink protected the printed labels far better than tape and held up well through multiple seasons.

Heat shrink Controller Output Labels on RGB pixel controller pigtails

But sometimes the outcome wasn't as good as I thought?

Faded by the sun and hard to read

Next, I wanted something that would last longer.

Why I Switched to 3D Printed Controller Output Labels

Why I Switched to 3D Printed Controller Output Labels

By this point, my display had grown considerably. I was no longer building only 16-output controllers. Suddenly I had 8-output controllers, 4-output smart receivers, and a variety of custom controller layouts that didn't fit neatly into my original numbering system.

At the same time, many of my oldest Controller Output Labels were beginning to show their age. Some had faded, others had become difficult to read, and several simply weren't as durable as I wanted after years of outdoor use.

As a result, I started experimenting with 3D printing.

What began as a way to replace worn-out labels quickly became an opportunity to completely rethink how I organized my controllers. Instead of creating labels for only one specific controller, I could design custom clip-on labels for virtually any output number or controller configuration. Whether I needed labels for an 8-output controller, a 4-output smart receiver, or something entirely different, I could print exactly what I needed whenever I needed it.

Looking back, switching to 3D printed Controller Output Labels wasn't just about replacing old labels—it was about creating a system that could grow along with my display.

Eventually, 3D printing opened the door to an entirely new approach.

First generation 3D printed Controller Output Labels (above) did a great job when attaching to the outputs with missing tags.

Current Controller Labels

After years of experimenting with different labeling methods, I finally settled on using 3D printing for my Controller Output Labels. What started as a way to replace worn-out labels has evolved into an ongoing project that's still changing today.

Unlike my earlier methods, 3D printing gives me complete freedom to create exactly the label I need. If I add another controller, build a smart receiver, or decide I want a different numbering system, I simply design a new label and print it. I don't need a specialized heat shrink printer or pre-printed labels—I can create exactly what I need whenever I need it.

However, I quickly discovered that there wasn't one perfect design. Over the years, I've created several different versions of my Controller Output Labels, and each one taught me something new. Some feature raised numbers that can be highlighted with a permanent marker, making them easy to read from a distance. Others use recessed, or "negative," numbers where the color of the pigtail jacket shows through the opening instead of printing the number itself. By printing those clips in a contrasting color—such as white or yellow on a black cable—the number becomes surprisingly easy to identify at a glance.

The reason for multiple designs is simple: not every controller is built the same. On some enclosures, raised-number clips fit perfectly and provide excellent visibility. On others, especially controllers with a retaining nut on the female pigtail, the raised style doesn't fit as well. That's where my recessed designs shine. Rather than forcing one solution to work everywhere, I refined the labels to fit different hardware and different installation situations.

As a result, my current Controller Output Labels aren't really a single design—they're a collection of designs that I've developed and refined over the years. Each version solved a different problem, and each improvement came from actually using the controllers in my display season after season.

j

In addition, I've learned that good Controller Output Labels work best when they're paired with good controller organization. During my more recent builds, I've switched to PG9 cable glands because they provide a little more room around the pigtails and have proven to be more durable than the smaller PG7 glands I used years ago. I also spend more time planning the spacing of each output so the pigtails line up neatly.

Does that mean this is the only way to label a controller? Absolutely not. Every decorator will eventually develop a system that fits their own workflow. What I've learned is that the best Controller Output Labels are the ones that make your display easier to build, easier to troubleshoot, and easier to set up next season. Could I go out and spend another $50 or $75 on a printer to make the nice heat shrink printed labels? Sure I could, but it's another tool that is only used for one thing in the hobby. I already spent the money on my 3D printers and so it stands to reason that I should use those for this exact task.

More importantly, they remind me of something I've learned over the past 13 years: your first idea rarely becomes your final one. Every controller you build teaches you something, and every improvement makes next year's setup just a little easier.

That's why I say... Next Year Will Thank You.

Newest controller labels clip right on to the cable. No need for a zip tie. And, this version allows the connector's nut to pass right over top of it, allowing for a solid connection at the controller.

Modern Controller Output Labels using 3D printed clip-on markers

More Than Your Outputs...

While Controller Output Labels make it easy to identify individual pigtails, don't stop there. Over the years, I've learned that labeling the enclosure can save much time.

Once the controller build is finished, the last things I do is create a label for the enclosure

Enclosure labels allow me to know at lot of information at a glance. Exactly which controller I'm looking at and what voltage it runs help insure I'm connecting the correct props to it.

For example, I like to include information such as:

• Controller model
• Operating voltage (5V or 12V)
• Assigned IP address
• Smart receiver identification
• Controller or enclosure name (when applicable)

Having this information visible from the outside makes setup, troubleshooting, and future maintenance much easier. Instead of opening multiple enclosures to find the one you need, the information is already right in front of you.

In addition, labeling your controllers creates consistency throughout your display. Whether you're setting up after a long offseason, expanding your show, or helping someone else troubleshoot a problem, clear identification eliminates unnecessary guesswork.

One habit I've developed over the years is assigning an IP address to every controller and printing that information directly on the enclosure. If I ever need to connect to a controller for configuration or troubleshooting, I don't have to remember the address or search through documentation—it's already labeled exactly where I need it.

The same idea applies to smart receivers and other supporting hardware. Even though a receiver may not have its own IP address, identifying its purpose and voltage helps eliminate confusion later. The more information you can see without opening an enclosure, the easier your display becomes to maintain.

Ultimately, Controller Output Labels are only one piece of an organized display. By labeling both the outputs and the controller itself, you'll spend less time searching for information and more time enjoying your holiday display.

Beginner Tips for Controller Output Labels

Clyde's Tips

If you're building your first controller, don't worry about making everything perfect. Every experienced decorator has looked back at an older controller and found something they would do differently today. The important thing is to develop good habits early, because those habits will save you time every holiday season.

Here are a few lessons I've learned after more than 13 years of building and rebuilding controllers.

Plan Before You Build

First, think about your controller layout before drilling a single hole. Consider where your pigtails, power cables, and network connections will be located. Spending a few extra minutes planning now will make your controller easier to wire, organize, and maintain later.

Label Every Output

Even if you think you'll remember which pigtail goes where, label it anyway. Months from now, after your controller has been stored away and you're setting up for another season, you'll be glad every output has a clear, easy-to-read label.

Keep Your Numbering Consistent

Choose a numbering system and stick with it. Whether you're building a single controller or an entire display, consistent Controller Output Labels make troubleshooting much easier and reduce confusion when adding new props or expanding your show.

Build for Next Year

It's easy to focus on getting the controller finished as quickly as possible. However, think about the next time you'll need to open that enclosure. Can you easily identify the controller? Can you tell which output feeds each prop? Will someone else be able to understand your labeling system? Small improvements today will save time every season.

Don't Be Afraid to Improve

One of the biggest lessons I've learned is that your first solution doesn't have to be your final solution. My own Controller Output Labels have changed several times over the years as my display grew and my building techniques improved. Every new controller gave me an opportunity to make the next one a little better.

Organization Saves More Than Time

Good organization isn't just about having a clean-looking controller. It helps prevent mistakes, speeds up setup, makes troubleshooting easier, and allows you to spend less time searching for information and more time enjoying your display. That's one of the best returns you'll ever get from a few extra minutes spent organizing your controller.

Common Mistakes When Creating Controller Output Labels

Every controller you build teaches you something new. Looking back over more than 13 years of building RGB controllers, there are several lessons I wish I had learned much sooner. Fortunately, these are all easy mistakes to avoid, and making a few small changes today can save you a lot of time and frustration next season.

Waiting Too Long to Create a Labeling System

One of the biggest mistakes I made was treating Controller Output Labels as an afterthought. When you're excited to get a controller built and into the yard, it's easy to tell yourself you'll label everything later. Unfortunately, "later" often turns into next season.

Thinking One Labeling Method Will Last Forever

As your display grows, your organization system needs to grow with it. What works well for a single 16-output controller may not work nearly as well once you're managing multiple controllers, smart receivers, and dozens of outputs. Don't be afraid to improve your Controller Output Labels as your display evolves.

Focusing Only on the Pigtails

It's easy to think that labeling the outputs is enough. However, good organization goes beyond the pigtails. Clearly identifying the controller model, operating voltage, and other important information on the enclosure itself makes setup and troubleshooting much easier. The less time you spend opening boxes to figure out what's inside, the more time you can spend enjoying your display.

Rushing the Build

I've learned that the cleanest controller builds almost always begin with good planning. Taking a little extra time to position cable glands evenly, plan wire routing, and organize your layout creates a controller that's easier to service for years to come. It's tempting to rush through the build, but those extra few minutes usually pay for themselves many times over.

Being Afraid to Change

Perhaps the biggest lesson I've learned is that there isn't one "perfect" way to organize a controller. My own Controller Output Labels have gone through several generations—from taped labels, to heat shrink, to professionally printed sleeves, to multiple versions of 3D-printed clips. Every change solved a problem that the previous version couldn't. That's part of the hobby, and it's one of the reasons I enjoy it so much.

Remember...

Your first controller isn't supposed to be your best controller.

The goal isn't perfection—it's progress.

If every controller you build is just a little more organized than the last one, you'll eventually create a system that makes setup, troubleshooting, and maintenance almost effortless.

Or, as I've learned over the years... You get BETTER with every setup!

Watch the Complete Video

Final Thoughts

Looking back over the past 13 years, it's interesting to see how something as simple as Controller Output Labels has continued to evolve. What started as a few printed labels and a roll of tape eventually became heat shrink labels, professionally printed sleeves, and finally a collection of custom 3D-printed designs that continue to improve with every new controller I build.

The biggest lesson I've learned isn't that one labeling method is better than another. It's that every controller you build is an opportunity to improve your process. Each season you'll discover something that could be organized a little better, labeled a little clearer, or planned a little more carefully. Those small improvements don't just make your controllers look nicer—they make setup faster, troubleshooting easier, and maintenance far less frustrating.

If you're building your very first controller, don't feel like you have to get everything perfect. None of us did. Start with a system that makes sense today, then refine it as your display grows and your experience increases. Before long, you'll have a labeling system that's tailored to your display and the way you work.

Most importantly, remember that Controller Output Labels aren't really about labels at all. They're about respecting your future self. Every few minutes you spend organizing a controller today is time you'll get back when you're setting up your display next season.

So, whether you're using a label printer, heat shrink, or designing your own 3D-printed clips, keep improving, keep learning, and don't be afraid to rethink yesterdays ideas.

Because after all...

Next Year Will Thank You.

Continue Learning

Keep building your controller knowledge with these related Pixel Pro Displays tutorials and guides.

Assemble Your First RGB Pixel Controller

How to Build the RGB2Go Octa8 Controller

RGB2Go Octa2Go Controller Review

Backer Board Template for your controller build

Controller Wiring Basics (Build the Baldrick 8 Controller)

Controller Output Labels: Create Them in Tinkercad for 3D Printing

The post Controller Output Labels: Methods and Organization appeared first on Pixel Pro Displays LLC.

Building your first RGB pixel controller is one of the biggest milestones in the Christmas lighting hobby, and today we're using the RGB2Go Octa8 Controller to demonstrate this. Once you've assembled your first controller, you'll better understand how your entire display works and gain the confidence to tackle larger projects.

In this Twinkle Tips Friday guide, we'll build an RGB2Go Octa8 Controller from the ground up. Rather than simply showing where every screw goes, we'll explain the thought process behind planning the enclosure, organizing the wiring, and creating a controller that's easy to install, maintain, and expand in the future.

Whether this is your very first controller or you're adding another enclosure to your display, these techniques will help you build with confidence.

New to RGB lighting? Before starting this project, we recommend reading our How to Build Your First RGB Pixel Controller guide, where we explain the basics of controllers, power supplies, and enclosure planning.

Components Used in RGB2Go Octa8 Build

Before picking up a drill, it's helpful to understand what each component does and why it's included.

• RGB2Go Octa8 Controller
• Mean Well LRS-350-12 Power Supply
• 3D Printed Mounting Plate
• Weatherproof Enclosure PVC Backer Board
• Eight Pixel Pigtails
• RJ45 Network Pass-through
• PG9 Cable Glands
• AC Power Cable Gland
• 14 AWG Copper Wire
• Mounting Hardware

While your exact hardware may vary, the planning techniques shown in this guide apply to almost any controller enclosure.

Tools You'll Need

Having the right tools makes the build easier and helps produce cleaner and consistent results.

Recommended tools include:

• Drill
• Step Drill Bits small and large
• Phillips Screwdriver
• Flat Screwdriver
• Wire Strippers
• Tape Measure
• Marker
• Scissors
• Small Wrenches or Nut Drivers
• Paper for Creating Templates

Why the RGB2Go Octa8?

This controller is compact eight-output pixel controller. Jason designed it for hobbyists who want a straightforward controller that's easy to build and maintain.

For many decorators, eight outputs provide plenty of flexibility for a small to medium-sized display while keeping the enclosure compact and organized. As your show grows, you may find a larger controller may come in hand, replacing the location where you're using the Octa8. That's okay! Your Octa8 is now free to use for other areas to expand into without spending more money with a future addition. Remember, it's okay to have a backup controller!

This article focuses on the Octa8. Lessons found here are universal, you can apply them to any controller build.

Plan Your Layout Before Drilling

One of the most valuable lessons in this build has nothing to do with wiring.

Before drilling any holes, spend time planning:

• Where the power supply will sit?
• How will you mount the controller?
• Which direction each pigtail should exit.
• Where AC power or the network cable enter the enclosure.
• How will you access everything later if maintenance is required.

Thinking ahead often prevents having to enlarge holes or relocate components later.

Create a Mounting Template

Guessing where components belong is a bad idea. Create a simple paper template.

This allows you to:

• Verify spacing.
• Check screw locations.
• Ensure the enclosure lid will close properly.
• Avoid accidentally blocking mounting screws.

It's a simple step that can save a lot of frustration.

Related Reading: Creating a Controller Backer Board Template

Building with Future Maintenance in Mind

An experienced builder doesn't just think about today's project. Clyde suggest that you think about your next season.

Can you easily drop in a replacement controller? Controller can break down, be ready with a spare.

Are the cable connection inside the box easily identifiable on the outside of the controller? You'll want to use some sort of labeling system.

One thing that Clyde remarked in his original video on building your First Pixel Controller, was the offset of the screw that held down the backer board. The power supply placement was slightly off and it covered 2 mounting screw positions.

A little extra planning now can make future upgrades much easier.

Wiring the RGB2Go Octa8

As with any controller build:

• Use quality copper wire.
• Make secure terminal connections.
• Route wiring neatly.
• Leave enough slack for future maintenance.

Make sure you pay attention to wire color, terminal labels, and voltage jumper alignments (5v or 12v). The Rgb2Go Octa8 controller can run both 5v and 12v pixels. Insure your controller's jumper is set correctly before powering on and connecting your pixels.

Routing the wiring efficiently and with enough slack can help make servicing the controller easier.

Waterproof Every Connection

Since controller enclosures spend months outdoors, weather protection is essential.

Cable glands serve several important purposes:

• Keep moisture out.
• Provide strain relief.
• Protect wiring from sharp edges.
• Keep insects and debris from entering the enclosure.

Taking time to install cable glands correctly will improve the long-term reliability of your controller.

Label Every Output

We LOVE this part. Labeling each output is one of the best habits you can develop.

Clear labels make it much easier to:

• Connect props during setup.
• Troubleshoot wiring issues.
• Identify errors when setting up your show (helpful neighbors?)
• Expand your display later.

Many experienced decorators will tell you that proper labeling saves hours every year.

Beginner Tips

Most first-time builders encounter the same challenges. Fortunately, they're easy to avoid.

Clyde's Tips

• Drilling before planning the layout.
• Forgetting cable glands or pigtails.
• Using wire that's too small.
• Blocking mounting hardware.
• Skipping cable labels.
• Rushing through the wiring process.
• Not testing the fit before tightening everything.
• Hiding or burying the power supply deep in a build.

Watch the RGB2Go Octa8 Complete Build

The companion Twinkle Tips Friday video walks through the complete RGB2Go Octa8 build from start to finish.

Watch the full video below.

FAQs

• Is the RGB2Go Octa8 good for beginners?

Yes! The Octa8 controller runs from WLED firmware. You can do this simple setup through your cell phone or PC

• What enclosure should I use

BudBoxes and MD-1500's are the most common and desirable box. Boxes used in this build are known as Demarkation Enclosures. Some hobbyists use Ammo Cans (like the MTM AC50C-40 seen below). You can see them in the video as well. They are large enough to hold 2 power supplies stacked and mount a 16 port controller on the top... along with 16 pigtail outputs.

• What power supply should I buy?

Clyde suggests you order the MeanWell LRS 350-12 of the LRS 600-12. These are the gold-standard when it comes to controller building. Some of those have been used for 15 seasons or more. He's only experienced 3 generic power supply failures over the past 19 years of this hobby k

• Can I use 5V or 12V?

12v has become the hobby standard. You're welcome to use 5v pixels if you like. Clyde uses both

Continue Learning

Introduction to the Octa2Go Controller, a first look

3D Printable Octa8 Power Supply mount STL (as seen in the video)

Making a Controller Mounting Template

Baldrick 8 Build

RGB2Go 3D Printable Files from the RGB2Go website

How to Label Pixel Controllers for Easier Maintenance

The post How to Build the RGB2Go Octa8 Controller: A Beginner’s Guide appeared first on Pixel Pro Displays LLC.

Moving heads are among the most exciting props you can add to a holiday display,

They're also one of the few devices where two models that look nearly identical can behave completely differently.

At Pixel Pro Displays, we've created PPD Certified Mapping Files for many of the most popular hobby moving heads sold by U.S. vendors.

These files help bridge the differences between our programming layout and your moving head models

Our goal is to make it easier to import PPD moving head sequences while preserving the intended movement and effects.

The video accompanying this article walks through the entire process, from downloading and importing a sequence into your own layout.

The reason comes down to mapping.

Why Moving Head Mapping Is Different

Unlike pixels, where every node simply turns on with a color value, moving heads contain many different DMX channels.

A typical fixture may include channels for:

• Pan
• Tilt
• Dimmer (Intensity)
• Color Wheel
• Gobos
• Focus
• Prism
• Shutter
• Speed
• Additional specialty functions

The challenge is that manufacturers don't always place these functions on the same DMX channels. One moving head might use Channel 1 for the dimmer, while another uses Channel 8. Pan and tilt directions can also vary between manufacturers. And of course, each moving head can rotate in different directions, either clockwise or counter-clockwise.

It is exactly for these reasons that Moving Heads sequence importing is not simple. With multiple vendors sequencing with many different models of moving head lamps, it's easy to get lost on how you can effectively import a vendor sequence. Pixel Pro Displays has gone out of their way to create Certified Mapping Files for the most popular US vendor moving head models. Moving Heads are considered an advance prop and you should be warned from the start that there is a lot of ground work and understanding you must have in order to successfully run these into your show.

Start by Creating a Dimmer Submodel

The first recommendation is creating a dedicated Dimmer submodel for every moving head in your layout.

This allows xLights to correctly map the PPD Intensity effects and ensures that dimming behaves exactly as it was programmed. In the video, Clyde demonstrates how to determine which DMX channel controls the dimmer and then creates matching submodels before importing any effects.

Although this only takes a few minutes, it's one of the most important preparation steps.

Organize Your Moving Heads with Groups

Once you've created the dimmer submodels, the next step is organizing your layout.

We recommend creating two groups:

• All MH – Contains all of your moving head models.
• MH Dimmers – Contains the dimmer submodels you just created.

These groups make importing future PPD Moving Head sequences much easier.

When you import your first PPD Moving Head sequence, you'll map the PPD moving head models and dimmer submodels to your own layout. At that point, save the mapping as a Sequence Map.

Save Your Mapping File Once

One of the biggest time savers demonstrated in the video is creating your own mapping file between the PPD layout and your layout.

A Sequence Map is different from a PPD Certified Mapping File.

A Sequence Map simply remembers how the models and groups in a PPD sequence correspond to the models and groups in your xLights layout. The next time you import a PPD Moving Head sequence, you can click Load on the Import Effects mapping screen, select your saved Sequence Map, and xLights will automatically match the PPD moving head models and dimmer submodels to your layout—no dragging, double-clicking, or remapping each model individually.

This is a huge time saver if you regularly purchase PPD Moving Head sequences, since you'll only need to create the Sequence Map once. Future PPD moving head sequences can then reuse that mapping file, allowing new imports to take only a few clicks instead of rebuilding everything from scratch.

Using PPD Certified Mapping Files

Even after mapping the models themselves, some fixtures require additional channel remapping.

This is where the PPD Certified Mapping Files come in.

Each certified file is built specifically for a supported moving head model and automatically remaps channels to match that fixture's DMX configuration.

Some models may also require additional adjustments, such as:

• Pan offsets
• Pan inversion
• Other model-specific corrections

These instructions are listed directly alongside each Certified Mapping File on the Certified Moving Head page of the PPD website so you know exactly what changes need to be made.

As you saw in the video, not all moving heads point perfectly in the direction you want them to. Clyde mentions in the video that you may need to use the xLights Adjust Effect in order to limit the DMX movement that may point your beams in an undesirable direction such as into other homes or cars. An extensive review of the Adjust effect can be found in this PPD Webinar video below and is relevant to correcting any issues you may have after mapping a moving head sequence.

Supporting the Hobby Vendors

One thing that makes the Certified Models program unique is that it focuses on the hobby community.

Rather than supporting generic imported fixtures with countless variations, PPD has worked to create mapping files for moving heads offered by well-known U.S. hobby vendors. This helps ensure compatibility while also supporting the companies that provide customer service, xLights models, and ongoing support to the Christmas lighting community.

What moving head models are not supported?

While we have great respect for all vendors, Pixel Pro Displays cannot provide Certified Mapping Files for every brand of moving head.

Creating a Certified Mapping File requires more than a vendor simply offering a fixture. To properly certify a model, we need access to reliable xLights model definitions, consistent DMX channel information, and enough documentation to thoroughly test the mapping process. Many off-brand or generic vendors will purchase a quantity of moving heads from any Chinese manufacture, only to replenish their with a different version as they move their inventory. We find that the US Vendors demand consistent quality and work closely with their manufacture to insure a quality fixture from season to season.

Because of these vendor demands, we confidently support and recommend only the hobby vendors. By focusing on these xLights community leaders, our ability to provide you with an effective Certified Mapping File can be insured.

Small Adjustments Can Make a Big Difference

Even with certified files, every display is a little different.

Some installations may need:

• Minor pan adjustments
• Tilt corrections
• Fixture alignment tweaks

Fortunately, once you've identified the correct settings for your particular model, those changes typically remain the same for every future sequence you import.

Watch the Complete Tutorial

This article covers the concepts behind moving head mapping, but the accompanying Twinkle Tips Friday video demonstrates every step inside xLights, including:

• Creating dimmer submodels
• Building moving head groups
• Importing PPD sequences
• Creating reusable mapping files
• Loading Certified Mapping Files
• Applying pan offsets and inversion
• Verifying that your moving heads perform exactly as intended

If you're planning to add moving heads to your holiday display—or already own them—this tutorial can save you hours of trial and error.

You can also browse all currently supported fixtures by visiting the PPD Certified Models page and downloading the mapping file that matches your moving head.

What If My Moving Head Isn't Supported?

If your moving head was purchased through Amazon, eBay, AliExpress, or another marketplace that doesn't provide an xLights model, getting it working with PPD Moving Head sequences will require a few additional steps.

The first step is creating or obtaining a working xLights model for your fixture. Before any mapping can begin, the model must accurately represent your moving head and be tested to verify that pan, tilt, dimmer, color wheel, gobos, and any other DMX functions operate correctly within xLights. PPD does not create moving head models.

Once you have a working xLights model, the process of importing PPD Moving Head sequences is very similar to the workflow shown in this guide. You'll create the necessary dimmer submodels, organize your moving heads into groups, create a reusable Sequence Map, and then determine any channel remapping or adjustments your fixture may require. The video link below shows a step by step process to create your own DMX channel remapping file that custom works for your moving head.

You can follow the Moving Head Mapping video here on how to create your own mapping:

While we're always happy to help our customers, creating xLights models for unsupported moving heads is outside the scope of our support. Building and validating a new moving head model can take many hours and requires detailed knowledge of the fixture's DMX implementation. Because every unsupported fixture is different, it simply isn't practical for us to create custom models for every moving head on the market.

However, if you already have a fully functioning xLights model and need assistance with creating your own mapping file, we'd be happy to work with you during a scheduled one-on-one consultation. Together, we can use one of your PPD Moving Head sequences to identify the required channel remapping, offsets, inversion settings, and any other adjustments needed to get your moving heads performing correctly. Click the link here to setup a one-on-one consultation with Pros at Pixel Pro Displays:

While moving heads can seem intimidating at first, once you've created your xLights model, saved your Sequence Map, and applied the correct Certified Mapping File, importing future PPD Moving Head sequences becomes fast and repeatable. Most of the setup only needs to be done once, allowing you to spend more time creating great-looking shows and less time troubleshooting.

The post Mapping PPD Moving Head Sequences using Certified Mapping files appeared first on Pixel Pro Displays LLC.

We'll cover how to measure your enclosure, size a template for your backer board, transfer mounting hole locations from your power supply, and lay everything out so you can visualize the finished controller before assembly. I also share a couple of inexpensive material options, including a cutting board from Walmart that's perfect for many controller builds.

Whether you're building your first controller or looking for a cleaner, more organized layout, this simple planning step can make your next build much easier.

If you enjoyed this video, be sure to like, subscribe, and let me know what you'd like to see covered in a future Twinkle Tips Friday!

Happy building!

The post Creating a Controller Backer Board Template appeared first on Pixel Pro Displays LLC.

Pixel Poles and Exploding Stars are some of the most popular props for patriotic displays, but they don't have to be limited to basic animations. With just two built-in xLights effects, you can create eye-catching movement that makes these props feel more energetic and coordinated.

In this week's Twinkle Tips Friday, we're looking at two effects that work especially well together:

• Morph for the Pixel Pole
• Shockwave for the Exploding Star

These aren't complicated techniques. They're simple changes that can make a big difference in the finished look of your sequence.

Why These Two Effects Work So Well Together

A Pixel Pole naturally draws your eye upward. The Morph effect enhances that movement by creating a clean flow from the bottom of the pole to the top.

Once the animation reaches the Exploding Star, the Shockwave effect spreads outward from the center of the prop, creating a bold, energetic burst that complements the movement of the pole.

The result is a smooth transition between the two props that feels intentional and polished.

Sequence the Props as a Group

One tip we share in the video is to apply these effects to a Group Model instead of sequencing each prop separately.

Doing this allows the Pixel Pole and Exploding Star to work together as a single visual element, making the transition between the Morph and Shockwave effects much more natural.

Related Article: How to Use Model Groups in xLights

Morph Effect Tips

The Morph effect is one of the most versatile tools in xLights. While it's commonly used on Mega Trees and matrices, it also works exceptionally well on Pixel Poles.

In this application, it creates a clean upward movement that naturally leads into the Exploding Star.

Related Article: Getting Started with the Morph Effect with New Updates

Bringing Your Exploding Stars to Life

Many people treat Exploding Stars as static props, but adding the Shockwave effect gives them much more personality.

Instead of simply lighting the prop, Shockwave creates expanding motion from the center, making the star feel alive without adding complicated layering.

A few small adjustments to the timing can completely change the feel of the animation.

Related Article: Updated Effects in xLights

Related Video: The Shockwave Effect in xLights

Watch the Complete Tutorial

In this week's Twinkle Tips Friday, we walk through the setup step by step and show exactly how these two effects work together.

The post How to Animate Pixel Poles and Exploding Stars in xLights appeared first on Pixel Pro Displays LLC.

If you're just getting started with RGB pixel lighting, building your first pixel controller can seem intimidating. Between power supplies, cable glands, network connections, and wiring terminology, it's easy to wonder where to even begin.

The good news is that building a controller is much simpler than it first appears.

In this Twinkle Tips Friday tutorial, we walk through building a complete Baldric 8 pixel controller inside a weatherproof enclosure. Along the way, you'll learn not only how to assemble the controller but also why each component is important.

Whether you're planning your very first Christmas display or expanding an existing show, this guide will help you understand the basics with confidence.

What Is a Pixel Controller?

A pixel controller is the "brain" of your lighting display. It receives data from your show computer or player and tells each pixel exactly what color and brightness to display.

Without a controller, your RGB pixels can't perform animations or synchronized effects.

If you're new to the hobby, think of the controller as the translator between your sequencing software and your lights.

Related Reading: xLights Pixel Controller Options

What You'll Need

For this build, we used:

• Baldric 8 Pixel Controller
• Weatherproof enclosure
• Power Supply
• SFL Designs dual-controller mount
• Pixel pigtails
• RJ45 network pass-through
• AC power cable gland
• PG9 cable glands
• Mounting hardware
• 14 gauge Copper wire

You don't necessarily need these exact parts, but understanding what each one does will help you build almost any controller enclosure.

Related Video Short: Pixel Controller Parts Explained

Planning the Layout

One of the biggest mistakes beginners make is mounting components before deciding where everything should go.

Before drilling a single hole, think about:

• Power supply location
• Controller placement
• Pixel cable exits
• AC power entry
• Network cable entry
• Future maintenance

Taking a few extra minutes here can save a lot of frustration later. Identify where cable will eventually run once connected. Then you can begin laying out your cable entry points.

Mounting the Power Supply

In the video, Clyde demonstrates a simple trick using a piece of paper as a template. Then he attaches the template backer board before drilling holes.

It's a small detail, but it helps ensure the power supply lines up correctly and reduces the chance of drilling in the wrong location.

Simple techniques like this make the entire build go much smoother.

Organizing Your Pixel Outputs

Instead of randomly installing pigtails, Clyde uses the top-bottom approach as found on the pixel controller board. He mimics the placement of the pigtails and wires it up similarly to the actual controller. The template makes it easy to mark out and drill the holes at so each output is evenly spaced.

Clyde uses some left-over Boscoyo strip material and cuts it down... stacking two strips of four to create a template. Placing this template over the box, he can trace out the holes to drill out

Outputs1 through 8 are now well organize which makes troubleshooting much easier later.

A few extra minutes during assembly can save hours once your display is outside.

Related Reading: How to Label Pixel Controllers for Easier Maintenance (Internal Link)

Wiring Your Controller Safely

Once all of the major components are mounted, it's time to begin wiring the controller. This is one of the most important parts of the build because a properly wired controller is both reliable and safe.

Throughout the video, Clyde emphasizes taking your time and making clean, secure connections. Loose wires can create intermittent problems and, in extreme cases, generate enough heat to damage components.

For builders in the United States, the standard AC wiring colors are:

• Black = Line (Hot)
• White = Neutral
• Green = Ground

Always double-check your wiring before applying power, and if you're not comfortable working with household AC voltage, seek assistance from someone with electrical experience.

Why Cable Management Matters

One of the easiest ways to make your controller easier to maintain is by keeping the wiring neat from the very beginning.

A well-organized enclosure isn't just about appearance, it makes future troubleshooting much easier. If you ever need to replace a pigtail, replace fuses, or troubleshoot a wiring issue, you'll appreciate taking the extra time during the initial build.

Simple habits such as routing wires neatly, bundling cables, and leaving a little extra wire for future updaes can save hours of frustration later.

Label Everything

As your display grows, you'll quickly discover that every controller starts looking the same.

That's why Clyde labels each output from 1 through 8 before closing the enclosure build. He is using his own homemade 3D printed Cable Labels. These visual clips make it much easier to identify which output is associated to the controller inside the box. Imagine the time you'll save. You won't need to open up the enclosure and trace cables to insure they are routed to their proper port on the main control board.

A few inexpensive cable labels today can save a lot of time during setup and troubleshooting. If you would like to try using the same 3D printed cable labels Clyde, click here to download them.

Why We Chose the Baldrick 8

There are many excellent pixel controllers available today, and the Baldrick 8 is just one option. For this tutorial, it was selected because it's an affordable, beginner-friendly controller that offers enough outputs for many first-time displays while still leaving room to grow.

The concepts demonstrated in this article apply to almost any pixel controller, regardless of manufacturer. Planning your layout, mounting components, wiring safely, and organizing cables will solve the majority of issues you will find when building an animated light show.

The goal isn't simply to build a Baldrick 8. It's to understand the fundamentals of building any pixel controller enclosure.

Common Beginner Mistakes

Everyone makes mistakes on their first controller build. Fortunately, most of them are easy to avoid with a little planning, some patients, and being mindful of the build process. Some of the most common include:

• Drilling enclosure holes before planning the layout.
• Forgetting to order pigtails or cable glands.
• Using wire gauge that is too small for the application.
• Failing to label outputs.
• Mounting components too close together, making future maintenance difficult.
• Rushing through AC wiring without checking each connection.
• Insuring that all pigtail connections to the removable pluggable connection are very tight

Remember, building a controller isn't a race. Taking your time almost always leads to a cleaner, more reliable finished product. This controller build took well over 4 hours to record. Great care was put into insuring completeness, and a fast-build controller can breed too many mistakes you'll likely feel during your setup when things aren't quite going right.

Watch the Complete Build

Reading about the process is one thing, but seeing each step completed makes everything much easier to understand.

In this Twinkle Tips Friday episode, Clyde walks through the complete build from an empty enclosure to a finished Baldrick 8 controller. Along the way, he shares practical tips and explains why each step is performed, making this an excellent resource for first-time builders.

Continue Your Controller Build Journey

Building your first pixel controller is one of the most rewarding milestones in the RGB lighting hobby. Once you understand how the enclosure, power supply, controller, and wiring work together, you'll have the confidence to tackle larger displays and more advanced projects.

Remember, every experienced decorator built their first controller at some point. Take your time, ask questions, and don't be afraid to learn as you go. Each project builds on the last, and before long you'll be helping the next newcomer get started.

Continue Learning

If you found this guide helpful, you may also enjoy these Twinkle Tips Friday tutorials:

• xLights Pixel Controller Options
• Creating a Controller Backer Board Template
• Lightshow Controller Layout Strategy
• How to Make Your Pixels Talk!
• Beginner's Guide to RGB Hobby and Pixels

The post How to Build Your First Pixel Controller appeared first on Pixel Pro Displays LLC.

How to Connect Your Baldrick 8 Starter Kit to xLights

Building your first RGB controller is exciting, but seeing your pixels respond inside xLights is where the real fun begins.

After assembling the Baldrick 8 Starter Kit, the next step is connecting everything to your network, configuring the controller inside xLights, and sending your very first effects to real pixels.

In this video, Clyde from Pixel Pro Displays walks beginners through the entire process—from plugging in the controller to seeing pixels light up with effects like Butterfly and Single Strand. If you're new to RGB lighting, this guide will help simplify the setup process and get your first controller talking to xLights.

What You'll Need Before Starting

Before diving into xLights, make sure you've already completed the controller assembly covered in Part 1.

Your starter kit should include:

• Baldrick 8 Controller
• 12V Power Supply
• Two strings of EZRGB Pixels
• Two pixel extension cables
• Pixel pigtails
• Power wiring (from power supply to the controller)
• AC power cord

You'll also need an Ethernet network cable (RJ45/Cat5e) to connect the controller to your home network. Clyde points out that many people already have one of these cables lying around from an old router or modem.

Powering Up the Baldrick 8

Before connecting to xLights, it's important to verify all of your wiring connections.

Clyde reviews the key connections:

• Red wires connected to voltage positive
• Black wires connected to voltage negative
• Green wire connected to ground
• White wire connected to neutral
• Black AC wire connected to line/load

Taking a few minutes to double-check these connections can save a lot of troubleshooting later. Once everything looks good, it's time to power up the controller.

Connecting the Controller to Your Network

The Baldrick 8 communicates with xLights through your home network.

After connecting the Ethernet cable, you'll notice activity lights beginning to flash near the network port. These LEDs indicate the controller is communicating with the network and ready for configuration.

For many beginners, networking can seem intimidating, but this part is actually quite simple. Once the cable is plugged in, the controller will typically receive an IP address automatically from your router.

Finding the Controller in Your Web Browser

One of the first things Clyde demonstrates is connecting to the controller through a web browser.

Simply enter:

baldrickboard.local

into your browser's address bar. This allows you to access the Baldrick setup page and view information about the controller.

From there, you can locate the IP address assigned by your router.

In Clyde's example, the controller received:

192.168.1.54

However, your address will likely be different depending on your network. The important thing is learning where to find it.

Once you know the IP address, you can access the controller directly using that address anytime.

Adding the Baldrick 8 to xLights

Now it's time to jump into xLights.

Starting with a blank show directory, Clyde demonstrates how to add a new Ethernet controller.

The process is straightforward:

1. Open the Controllers tab.
2. Add a new Ethernet controller.
3. Select Baldrick as the vendor.
4. Select Baldrick 8 as the model.
5. Enter the controller's IP address.
6. Save the configuration.

At this point, xLights begins attempting to communicate with the controller.

The Green Light Moment

One of the most satisfying moments in the entire setup occurs when the controller indicator changes from red to green.

As Clyde points out:

"It's now talking and communicating with the Baldrick 8 controller."

That green indicator means:

• The controller is online
• xLights can see the controller
• Communication is working correctly
• You're ready to start configuring outputs

For beginners, this is often the first major milestone in their RGB journey.

Creating Your First Pixel Models

With communication established, the next step is creating some simple models.

Clyde creates:

String One

• Single line model
• 100 pixels

String Two

• Single line model
• 100 pixels

These models represent the two pixel strings included in the starter kit.

Creating models is how xLights knows what pixels exist and where effects should be sent.

Assigning Pixels to Controller Outputs

After creating the models, Clyde returns to the Controllers tab and maps each string to a physical output.

The assignments are simple:

• String One → Output 1
• String Two → Output 2

xLights makes this easy through a drag-and-drop interface, allowing you to visually assign models to controller ports.

Uploading the Configuration

Many beginners stop after creating models, but one critical step remains.

The controller needs to receive the configuration from xLights.

Using the Upload Outputs function, Clyde sends the configuration to the Baldrick 8. Once xLights reports:

Output Upload Complete

the controller is fully configured and ready to run pixels.

Connecting the Pixels

With the controller configured, it's finally time to connect the actual pixel strings.

Clyde demonstrates the difference between the male connectors on the controller and the female connectors on the pixel strings.

Once connected, everything is physically ready for testing.

Sending Your First Effects to the Lights

Now comes the fun part.

Inside a new xLights sequence, Clyde demonstrates several simple effects to verify everything is working.

On Effect

The first test uses a simple On effect with a red color.

After enabling Output to Lights, both pixel strings immediately illuminate.

Butterfly Effect

Next, Clyde applies a Butterfly effect to one of the strings, creating colorful animated patterns.

Single Strand Effect

The second string receives a Single Strand effect with multiple chases and color combinations.

By the end of the demonstration, both strings are displaying different effects and colors, proving the entire system is working correctly.

Why This Step Matters

Many people can assemble a controller.

The real confidence boost comes when you successfully connect that controller to xLights and watch actual pixels respond.

This video bridges the gap between hardware and software, showing that the process is much easier than many beginners expect.

By breaking the setup into small, manageable steps, Clyde helps remove the fear that often keeps people from getting started with RGB lighting.

Learning xLights One Step at a Time

One of the biggest advantages of the Pixel Pro Displays Starter Kit is that it teaches both hardware and software together.

Instead of trying to learn everything at once, you're building knowledge piece by piece:

• Controller assembly
• Power connections
• Networking basics
• xLights controller setup
• Model creation
• Pixel testing

Before long, you're creating your own effects and running your first light show.

A Huge Milestone for New Hobbyists

Every advanced RGB display started exactly here.

A controller on a workbench.

A couple strings of pixels.

A first successful connection.

A few simple effects running across the lights.

The Baldrick 8 Starter Kit and this xLights setup walkthrough make that first success much easier to achieve.

If you've been wanting to learn RGB lighting and xLights, this is one of the best ways to get started while building confidence every step of the way.

https://youtu.be/U4NGIXXcDNY?si=aPbs4q-gzxySiE3v

The post Setup the Baldrick8 Controller in xLights: Pt 2 appeared first on Pixel Pro Displays LLC.