Sean Meighan
Software => Bugs in xLights/Nutcracker => Topic started by: pixelpuppy on November 16, 2015, 10:37:54 AM
-
I am attempting to create a background.eseq file to run on the FPP. This is for pathway lights. They are single channel AC lights (DMX dimmer), but there are multiple strings and each string has its own channel.
I created a model and now when I try to Export Model to eseq it crashes. (crash files attached) I thought perhaps it may have a problem with all the channels not being continguous so I modified the Model to only have contiguous channels. Now when I try to Export Model the xLights program closes with no crash files.
xLights version 4.2.22
-
Perhaps he model got corrupted. Try creating a new one and see if that works ?
Alternatively , the FP has some sample script effects called StaticOn and StaticOff (or something very similar) that you could use to turn on and off your static lights if u cant get this to work. (Just amend the channel numbers). I think there are also similar ones for block of channels.
-
The sequence file inside your crash report exports to eseq just fine for me. All I see is a single On effect.
-
Gerry, Thanks for the tip. The model must have become corrupted in the crash. I recreated it and it seems to export without errors. Now I just need to confirm that the .eseq file plays correctly on the FPP.
Gil, yes, its just a single on effect across a multiple channel model called "pathway". As I mentioned in the first post, I want to create a background.eseq that will turn on the pathway lights whenever the FPP starts up.
As a curious test, I made another model with a gap in the middle of the channels and sure enough, xLights shutdown. No crash this time, just the popup window that the program has closed. I restarted xLights, fixed the channel gap and it exports without shutdown.
I realize that at this time, eseq files must be contiguous channels. But I wasn't expecting the program shutdown/crash. I guess the fix would be to check for gaps and disallow the export. My preference would be for it to warn the user of the gaps and optionally continue with the export by filling the gaps with zeros. This way, model groups could potentially be exported too (it would be a shame to disallow all groups if there are no gaps in a group). I understand this could "black out" anything on those filler channels but that's not an issue if they are unused channels.
If Captian Murdoch is reading this, could you tell us how the FPP handles overlapping channels if/when a background.eseq is playing and an fseq sequence plays over the top of it.
-
Eseq takes precedence over fseq data.
-
Sounds like some great coding ideas...when you gonna join the team and fix it up for us? :)
There's so much code there that none of the developers really know it all. I don't even know what file to look at to find where that export happens but I'm sure I could find it. So yeah we don't want it to crash either but I'm pretty sure whoever wrote the code isn't doing that on purpose. I kinda laugh cause I consider crashes like this to be like a child touching a hot stove. You learn quick to not do what caused that pain again...lol. That's the fun part of freeware. If we were charging for the code we'd have to suck it up and say sorry sir we will get that fixed right away.
-
I'd be happy to help in any way I can. But I haven't even peeked at any of the xLights code yet. I would need some initial guidance on what modules to start hunting in.
-
Eseq takes precedence over fseq data.
Good to know. Thanks!