Export .FSEQ of only one controller

[gb70]

Hi,
I'm almost ready, I just need the .FSEQ extraction to copy to the micro sd of each single controller.
For next Christmas I'm testing the transmission system from FPP (on the BBB) to EPS32 in wifi multicast mode.
On the FPP I will have to copy the file. fseq of all controllers with the .mp3 file for audio
all.jpg
I think I will make 7 sequences, consequently I will copy the 7 .fseq files with the relative .mp3 files to the FPP.

For each ESP32 I will have a micro sd, where I should copy the relative .fseq file for that group of the show;
in the vixen export, of .fseq, if I choose to extract only one group I see that the numbering of the channels changes
mini.jpg

Is it possible to be able to keep the numbering that I set in FPP as well?
Or can I upload the same file (with all controllers) to each ESP32?

thanks
Graziano

[jchuchla]

You're on the right path. Just select the controllers you want to export for each SD card. Each one will start at one. That's fine. Just set up each controller to match.

One thing I'm a bit unclear of in your description though is whether you plan on streaming the data to the ESP32s from the FPP, or just using multisync and having it play local data. The latter makes more sense.

Channel numbering is always relative. Multisync simply transmits sync data. It basically says, "Playing XYZ sequence, current frame 12345" The slaves then make sure they're playing the sequence with the matching name, and at the same point in time. What is contained in the sequence files and what channels they go to is irrelevant to the multisync process. Because the ESP32 is a relatively resource limited microcontroller, you don't want to give it lots of extraneous data to sort thru. You only want to have the channels that are relevant to the pixels you're controlling. It doesn't matter how that channel range fits in to the whole overall sequence, it only matters with respect to the sequence file and the string it's going to. So each ESP will be set that its output starts at 1. It will be different data, because you put different data starting at slot 1 to each fseq file.

[gb70]

hello, jchuchla
yes i would like to stream everything from FPP deleting the pc; yes i would like to play files locally but with FPP, is it possible?

so if I extract each controller, the channel always starts from the number 1 and that file extracted .fseq I copy it on the esp32 micro-sd.
On the FPP instead? do I leave the .fseq file complete with all the controllers? Or should I enter something else?
I guess I didn't understand multisync very well.

[jchuchla]

I think you're missing the point. If you're playing from SD cards, you're not streaming from FPP. If you were streaming the data from FPP, you don't need SD cards.

The file you export for the master FPP only needs the data for the channels it's directly controlling, or streaming to. It does not need the channel data for the ESPs that are each playing local data.

If the FPP isn't directly controlling any lights you still need an FSEQ file on the FPP to use as a timing reference. It could be any of the files, in this case, the actual channel data would be irrelevant.

[gb70]

OK thank you, jchuchla
now i started to understand the difference.
Yes I'm configuring everything for FBB on BBB master and I will have 13 ESP32 as remotes... so ok only .fseq sequence on the FPP with mp3 files.

Just for info, maybe it will be useful for the future... would the single files on the sd of the ESP32 be controlled only if I have unicast connections? and data sent directly from Vixen on PC?

last question... the "timing", with FPP better 25 - 50 - 100?
timing.jpg

[jchuchla]

.

Just for info, maybe it will be useful for the future... would the single files on the sd of the ESP32 be controlled only if I have unicast connections? and data sent directly from Vixen on PC?

last question... the "timing", with FPP better 25 - 50 - 100?
timing.jpg

No. Vixen does not act as a multisync master. It would not cause the ESP32s to play from their SD cards.

Don't mistake multisync with multicast. Multisync is a method of keeping FPP masters and remotes in sync. Multicast is a method for transmitting data to many devices at once. They are not related.

Your choice of timing speed depends on what you're doing. If you've got a lot of fast movement, 25ms (40FPS) would look best but at the expense of larger file sizes and longer upload times. 100ms (10 FPS) is ok for mostly static or slow moving patterns. You get small file sizes and fast uploads. 50ms (20FPS) is a compromise in performance vs file sizes.

[gb70]

ok, thanks ... now the difference between the transmissions is already clearer to me.
For now I'll stop at the FPP mlticast, I'll do some tests and if I still notice slowdowns on the shows I'll try the multisync.
To program the effects I'm using Vixen, but could Vixen (in multisync) also send the package files to the single ESPixelStick as xLights?
I saw a video on youtube where this .fseq file transfer is very fast, rather than extracting it on the PC and then copying it to the micro-sd cards.

[jchuchla]

Again, i think you might be thinking backwards. There's a lot going on here to get your head wrapped around.

Vixen can create fseq sequence files for the individual SD cards. But Vixen does not have the ability to automatically send it to all of the units. You have to manage those files manually. Furthermore, vixen cannot act as the sync master. FPP needs to do this part.

xLights has the FPP connect feature that Vixen currently does not have. This is what manages and uploads settings and sequence files directly to the controllers. In Vixen, you have to do this process manually.

Or you can use Vixen to play directly to the ESP units (without using SD cards). You have your choice of DDP or sACN protocol to stream data to them. Your mileage will vary. The whole multisync paradigm with local playback from local storage was designed to overcome the limitations of streaming large amounts of timing sensitive sequence data over wireless networks.

[gb70]

OK thank you,
since I don't know everything well yet, for now I don't want to upset my settings.
On Vixen, for now, I have active 9 controllers (all ESP32 with ESPixelStick) in E1.31 unicast.
The ESP32s are connected to a TP-Link router, dedicated and not connected to the internet, via Wi-Fi.
On FPP I have already set all the IP addresses in unicast with the relative start/end of the channel.
I did some tests with test files and it seems to me that everything is ok for now.
This evening I'm exporting the files (.fseq and .mp3) of my show (9 in all) and tomorrow I'll try the complete show.

[jchuchla]

When you get around to it, I'd recommend reading this article regarding sACN over WiFi. It will help you get thru some of the challenges.
https://www.diychristmas.org/wiki/in..._ACN_over_WiFi