Hello
I'm hoping somebody else here is running ESPixelSticks with the latest v4 firmware and also scheduling with FPP as FPP remotes with the songs loaded to the onboard SD card. I'm having an odd problem. When using FPP and stopping my show it's supposed to send an STOP and turn the pixels black, but instead... the pixels freeze (so it is sending the STOP) and then slowly turn off over 10 to 15 seconds. I've checked the boxes in FPP for "Always transmit channel data" and "Blank between sequences", which should result in the lights turning dark whenever the sequence ends. It just doesn't. I can't find any way to make this work. I've verified all my sequences are completely dark at the end, also. Everybody says it should turn them off, but it doesn't. I have 11 ESPixelSticks across 7 power supplies and I re-flashed them all with the latest v4 firmware (Beta5) and I still have the same problem, so I don't think this is an issue with a bad flash or bad data on a line because it's consistent across all 11 controllers.
I have this running correctly in xSchedule, but it appears that only works because even though I am controlling the sticks via multi sync as FPP remotes, I have the setting "Always send data between sequences" turned and it appears to be sending that data via DDP. I am inferring this because I have the primary input set to DDP and the secondary input set to FPP remote. If I disable the primary input (DDP), the lights behave in xSchedule the same as they do in FPP... they stay on when I switch songs or stop the schedule. That tells me that the data between sequences is being sent via DDP. It doesn't appear as if there's any way to make falcon player send that between sequence data via DDP. Everything is sent as multicast.
This wouldn't be a big deal, as I do have it working in xSchedule, but I'd like to move back to FPP so I can run on my Raspberry Pi. The crappy computer I have to dedicate to this shuts down randomly. This issue of the lights not being correctly shut down seems to be causing an issue where at the end of every song, the lights aren't responsive to the next song for 10-15 seconds. My amateur interpretation is the Stop is being sent (the lights do stop playing the current song), but that moment of the pixelsticks getting nothing is confusing them in some way. Rather than just blank and wait for input, they're getting stuck and having to progressively clean themselves up. Without any way to get FPP to send data via DDP, it doesn't look like there's a fix in FPP that I can use to mirror what I'm doing in xSchedule.
Thoughts? Anyone else experiencing anything like this?
I'm hoping somebody else here is running ESPixelSticks with the latest v4 firmware and also scheduling with FPP as FPP remotes with the songs loaded to the onboard SD card. I'm having an odd problem. When using FPP and stopping my show it's supposed to send an STOP and turn the pixels black, but instead... the pixels freeze (so it is sending the STOP) and then slowly turn off over 10 to 15 seconds. I've checked the boxes in FPP for "Always transmit channel data" and "Blank between sequences", which should result in the lights turning dark whenever the sequence ends. It just doesn't. I can't find any way to make this work. I've verified all my sequences are completely dark at the end, also. Everybody says it should turn them off, but it doesn't. I have 11 ESPixelSticks across 7 power supplies and I re-flashed them all with the latest v4 firmware (Beta5) and I still have the same problem, so I don't think this is an issue with a bad flash or bad data on a line because it's consistent across all 11 controllers.
I have this running correctly in xSchedule, but it appears that only works because even though I am controlling the sticks via multi sync as FPP remotes, I have the setting "Always send data between sequences" turned and it appears to be sending that data via DDP. I am inferring this because I have the primary input set to DDP and the secondary input set to FPP remote. If I disable the primary input (DDP), the lights behave in xSchedule the same as they do in FPP... they stay on when I switch songs or stop the schedule. That tells me that the data between sequences is being sent via DDP. It doesn't appear as if there's any way to make falcon player send that between sequence data via DDP. Everything is sent as multicast.
This wouldn't be a big deal, as I do have it working in xSchedule, but I'd like to move back to FPP so I can run on my Raspberry Pi. The crappy computer I have to dedicate to this shuts down randomly. This issue of the lights not being correctly shut down seems to be causing an issue where at the end of every song, the lights aren't responsive to the next song for 10-15 seconds. My amateur interpretation is the Stop is being sent (the lights do stop playing the current song), but that moment of the pixelsticks getting nothing is confusing them in some way. Rather than just blank and wait for input, they're getting stuck and having to progressively clean themselves up. Without any way to get FPP to send data via DDP, it doesn't look like there's a fix in FPP that I can use to mirror what I'm doing in xSchedule.
Thoughts? Anyone else experiencing anything like this?
Last edited:
