Sean Meighan
Hardware => Falcon Pi Player => Topic started by: starsman20 on September 29, 2020, 11:51:36 AM
-
First year using XLights, switching from Vixen. I have 4 Beagle Bone black controllers from Kulp lights. last year I had a master FPP on a BBB running the music and some renard lights, another FPP running in remote mode dedicated to a mega tree, another one to some other props, and the last one across the street at the neighbors running a few props. In Vixen I output 4 fpp files with the same name with just the pixels that I want to control on each controller then I would download them from the FPP download page in each controller separately. I think the master sends a start command and they all run concurrently. What I haven't been able to find is a similar function in xlights. How do I separate out the files for what I want to run on each controller?
-
Fpp connect does this for you.
-
As Keith said, FPP Connect does this for you. However, you should also keep in mind that it is done DIFFERENTLY than what Vixen does.
If I remember correctly, in Vixen, the FSEQ files that are generated for each FPP instance are more or less non-sparse FSEQ files and start at channel "1" for each controller. Thus, when you configure the FPP outputs, you pretty much restart each controller at 1.
With xLights/FPP Connect, the controllers are configured to exactly match the channel numbers that xLights uses. The FSEQ files are "sparse" and will only contain the data for that FPP instance, but they retain the xLights channel numbers. If the first string on controller FPP1 starts at channel 1000 in xLights, it needs to be configured that way in FPP. The good news is that if you have all the controller connection things and such setup in xLights, xLights/FPP Connect can also upload that configuration to FPP.