Repository navigation
Add MicroSD Support AND Falcon Pi Player Remote Support #1278
Description
Activity
Have you seen https://github.com/ShaunPrice/FSEQLib. This can read fseq from SD card and display them. Doesn't have a pretty UI like WLED.
I would have to think how this could be integrated. I noticed the some what incompatible licenses between WLED (MIT) and FSEQ (GNU).
- Could FSEQ be treated like special effect? Copies the next frame from the file.
- What config options required? File name? Universe number?
Don't see why the FSEQ couldn't be treated as a special effect. We do something like that today in FPP & xScheduele.
The FSEQ format is detailed in the fseq spec. Some assumptions would need to be made by WLED regarding the channel numbers. Now that DDP is an option ya could just use the absolute channel numbers.
I do own a couple of micro sd shields so I can can help test once this gets support.
One Vote for this.
vote
vote
Lock here: https://github.com/Danit2/WLED_FSEQ/tree/FSEQ_Effect_player
I have done it and make a PR for this but it is no merges at the moment.
Reacted by HAPPY SMART LIGHTReacted by nibblerrickHi @Danit2 ,
Normally in xLights, we program sequences for multiple WLED controllers at the same time. Does WLED_FSEQ branch support that use case, or is this branch designed to work with only a single controller?
Hey @happysmartlight
Sure. It works exactly the same way in xLights.
The ESPs are set up as controllers and then programmed.
The sequence is then sent to each controller via FPP Connect.
xLights recognizes the ESPs as FPP Remotes.Just make sure that the upload of the models is not selected on the FPP master. Otherwise, the xLights models will be loaded onto the FPP master, and the FPP player will play the sequence via DDP.
The FPP Player will then also recognize the ESPs as FPP Remotes. Multysync must be enabled there.
The ESP functions like an FPP Remote Player.
I’m using this for this project:
https://youtu.be/SKAtECH3hnM?si=jFPXWkenM_vfabIQReacted by HAPPY SMART LIGHTThanks @Danit2 i can try it!
What are the advantages of this approach compared to running through DDP? @Danit2
The advantage is that you have significantly less Wi-Fi traffic.
If you have many controllers that need to control a lot of pixels and the FPP player has to send all that LED data live via unicast to all controllers, the larger your system is, the greater the Wi-Fi load will be.
If the LED data is all stored locally on the ESPs and only a time signal is sent to all ESPs via multicast, this places almost no load on the Wi-Fi network.
The ESPs are also much more synchronized than if you were to send everything separately.Reacted by HAPPY SMART LIGHTHi @Danit2 ,
If xLights uses effects such as visual video playback synchronized with music to display on an LED matrix of 80x50 pixels, is that possible? How is the performance in this case?
Also, could you explain how your mechanism handles this scenario (if supported)?Hey @happysmartlight
If you play the sequence using an FPP player, it works from the SD card.
If you do it directly through Xlights, it will still be played via DDP Love from Xlights.
It just always works when the FPP player is the master.
But please just give it a try.
Is your feature request related to a problem? Please describe.
Wifi is inherently noisy and congested which often results in choppy e131 & DDP playback. Since ethernet isn't an option for most esp8266/esp32 devices we must work with what's been given.
Describe the solution you'd like
Add support for a MicroSD card, reading FSEQ files (maybe compressed if the CPU can handle it), and FPP/xSchedule remote support.
Describe alternatives you've considered
N/A
Additional context
QuinLED doesn't support MicroSD today but other esp "Capes" do such as the ESPixelStick hardware. The ESPixelStick software also has the required remote support built in and sd card support which WLED can run on. Perhaps if this feature were to exist then Quindor may even be more receptive for adding a v2 of his boards with MicroSD support. Especially on the Quad boards.
I realize this is a major ask and I'm hopeful you can understand where this is coming from. With more and more data coming from xLights this will be a significant improvement.