Does this method still work for xLights and Falcon Player?

[dirknerkle]

At one time back in 2019 I wrote up a relatively generic method to create a matrix in xLights. I haven't messed with it since, and I'm asking if this method still works with the most recent version of xLights?

1. Start Xlights, set up your working directory.
2. Define the matrix's construction and save those settings so you use it again later.
3. In Xlights, open a blank sequence.
4. Insert the matrix you just defined into the sequence.
5. In Xlights, type the text the matrix is to display, set colors, speed, etc.
6. Save the combined sequence/matrix. Xlights saves this as an .fseq type file in the working directory.
7. Open Falcon Player on the Pi, upload the new .fseq file to the Pi using the Falcon Player's FILE Manager menu.
8. Include the new .fseq in the Falcon player's playlist; be sure to save the revised playlist.
9. Play the playlist on the Pi from the Falcon player's main status screen.

 

[algerdes]

You missed one important move. Upload the controller settings that contain the layout.
In xLights we usually use the FPP Connect function to upload the settings. You also use FPP Connect to upload the .fseq file(s).

If you wish to continue using the "old method", you can setup the controller manually and then copy the .fseq file to the FPP, but why?

 

[dirknerkle]

Thanks, Al. I was just going through some stuff, updating my PCs, etc. and noticed this brief text file in my xLights folder. Interestingly, my version of xLights is from 2019 and is a 32-bit version, which they don't produce anymore....

My goal was to fire up xLights again (it's been a long time since I last did that...) and maybe try to figure out some things, like maybe how to actually use it... because as you know, I'm still a Vixen 2.1 guy.... but before I get started again, I thought I'd check my existing cheat-sheets and see if they still apply....

 

[rstehle]

Thanks, Al. I was just going through some stuff, updating my PCs, etc. and noticed this brief text file in my xLights folder. Interestingly, my version of xLights is from 2019 and is a 32-bit version, which they don't produce anymore....

My goal was to fire up xLights again (it's been a long time since I last did that...) and maybe try to figure out some things, like maybe how to actually use it... because as you know, I'm still a Vixen 2.1 guy.... but before I get started again, I thought I'd check my existing cheat-sheets and see if they still apply....

Hey Dave, I was a diehard Vix 2.1 guy also as you know. I've tried both xlights and Vix 3. For me, xlights is so much easier to use. The expert help available is unmatched. DL the latest version and you will be amazed at the capabilities. The developers have gone berserk, but in a good way. Like Al said, you build your layout, insert your effects and let xlights do the rest of the work for you. The upload to controller and or FPP is the bomb.

 

[algerdes]

Boy oh Boy, did I goof. Sorry.
The program within xLights to send the setup to your CONTROLLERS is under the "Controllers" tab. Choose the controller you want to update, then use the "Upload" buttons on the right bottom.

You use the FPP Connect to send the sequence file (.fseq) to the FPP instance(s) you have.

The user manual, available under "Help" is pretty good. I think I'll try using it again.

I do this a couple of dozen times a day when creating the new layouts, so why I forgot the upload under the controllers is beyond me. Perhaps a need another fancy shake from Snuffy's.

 

[dirknerkle]

Thanks, Randy and Al.

So far, it sounds like the original concept/method outline is basically okay, with the newer option of uploading, which is likely because one can have both master and remote controllers? And this is the xLights method, right? Doesn't Vixen3 work a bit differently?

 

[rayhjr]

I got to agree with Randy. I started in 2015 with both Vixen3 and xLights. I kept my profile up in both and sequenced in both
untill a few years ago. I do everything in xLights now. It has become alot easier to use over the years, and I still run 6
Renard Plus boards along with all them pixels.
xLights sees everything as a grid. Right click on a prop and go to node layout and expand the pop up. Of course a matrix is
a grid already, but a star or candy cane will show the nodes in the grid to form the star or candy cane.

 

[algerdes]

One thing that has been a game changer is the visualizer. Check it out.

 

[TomsLEDs]

I am making the move to Xlights this year. I can already see 2 major advantages from setting up compared to using Vixen 3. 1) The ability to use null controllers and sequence everything, then map it to the physical controllers. 2) As mentioned above, Xlights will send everything to the controllers or PI player for you.

 

[Mark_M]

xLights is very good now for controller management and universes/channel auto counting.

I've done manual channel/universe assignment between xLights and my controller before, but having xLights configure it all in a second is much easier. Particularly when you miscount a model by 2 pixels and need to offset everything else!