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.
