I don't know if this is related or not, but it seems weird that its happening now after I made the changes to use an LOR Optimized output for these channels, but the sequencing is like... pulsing and flashing, now. This is in the sequencer itself, even though it's only drawing data from a Faces effect set to a Lyric track. I reloaded a backup of the xlights_networks.xml file that only had the OpenDMX set up, and it went back to normal when I rendered it again. I've always thought the networks file had nothing to do with rendering or FSEQ generation, that it was only to tell xlights what channels go where when outputting directly via xLights. I guess I'm wrong, there, as it wouldn't be behaving this way if it were otherwise. My only real question is why? Why does changing it to an LOR Optimized output type cause it to render my faces all funny-like?
I had initially set up only the channels going to the faces as LOR Optimized, and left OpenDMX on either side of those channels (1-96 OpenDMX, 97-128 (ID 7 & 8 ) LOR Optimized, then back to OpenDMX from 129-512), and it was under that setup that I saw the weird behavior in the sequencer. I've redone it again now, using LOR Optimized for the entire first universe, and gave it a render. The sequencing still appears normal, as it should, but when outputting to lights I'm getting weird effects again - it looks like it's doing a chase through all the channels, and not following the sequencer as it should. I've tried a few different baud rates, but that doesn't seem to affect the output. This is so friggin' weird.
I'd wondered if it was chasing and stuff because I had set up ID 7 & 8 first in the list, then listed the remaining 30 IDs after that, which might have been causing it to follow my 1:1 A/C data, which it looked suspiciously like. I rebuilt the entire 32 IDs in order, and then was unable to get ANY output on my faces. So, I went back, tried again, and set it up as NULL for 1-96, LOR Optimized for 97-128, and then NULL for 129-512). From this, it's gone back to acting all chasey and pulsey. I've noticed that when it is configured like this, my Face 1 in the Layout tab now shows 2:1 (97) as the Start Channel. I select the face, and the place where you enter that parameter still shows 1:97 as it always has. Clearing and re-entering it has no effect, and it insists that 1:97 = 2:1 (97) in the model list's Start Channel column. I guess this is related to having NULL entries, or OpenDMX entries, alongside the LOR Optimized, but I don't get any of this behavior - it all seems buggy and broken to me. I don't get what is causing it to insist that ch97 is the start of universe 2, when in the networks tab both the LOR Optimized and both NULL outputs are set as 1, and Universe 2 doesn't start until Ch 513 with my E1.31 outputs.
I'm sure I got a little confusing through there, entering each paragraph as I went back and tried something different to see if I could narrow down on a solution and the proper way to set it up, but I just got more and more confused myself, as none of it made sense to me. Configuring as LOR Optimized seems to hose my layout and the sequencing that goes to the Faces gets confused for whats in 1:1 instead of 1:97, apparently. Configuring as OpenDMX, despite working fine in xSchedule and via FPP, flickers like mad in xLights and makes it impossible to do the adjustments to the phoneme timing that I have to do (visualizer isn't enough to get it done right - I have to see it).
It all seemed to work okay at first on Saturday when I set it up initially, but I wasn't staying in the office long that day and I went home after I saw that the faces were singing properly. I wish I knew what changed, as it wasn't anything I did overtly, that I can tell. Maybe it was all jacked up then too, I just hadn't tested it thoroughly enough to tell. But, then again, idk, because the the faces looked right, and that was when the LOR Optimized was sandwiched between the two OpenDMX outputs (which were disabled, then as now).
