I wasn't able to get the light elf tool to work (..maybe problems with python?)
To get my show up I went back to xlights and the conversion tool.
I found some problems with my setup, and the messages in xlights were helpful to track them down.
One set of warnings indicated some problems I could not fix. The LSP gui showed everything in order, but the exported file had problems.
Reading: C:\xlights\hallow2.lms Reading LOR sequence Track 1 length = 30503 centiseconds WARNING: channel 'Aether2-RGB #1' is unmapped WARNING: channel 'Aether2-RGB #1' is unmapped WARNING: channel 'Aether2-RGB #1' is unmapped WARNING: channel 'Aether2-RGB #2' is unmapped WARNING: channel 'Aether2-RGB #3' is unmapped WARNING: channel 'Aether2-RGB #4' is unmapped WARNING: channel 'Aether2-RGB #5' is unmapped WARNING: channel 'Aether2-RGB #6' is unmapped WARNING: channel 'Aether2-RGB #7' is unmapped WARNING: channel 'Aether2-RGB #8' is unmapped WARNING: channel 'Cheapo #1' is unmapped WARNING: channel 'Cheapo #2' is unmapped # of mapped channels with effects=83 # of effects=18898 Media file=C:\xlights\silence5m.mp3 New # of time periods=6100 New data len=3123200 Writing xLights sequence Finished writing new file: C:\xlights\hallow2.xseq Finished converting all files |
My display is using a single DMX network... a USB Lynx dongle with 512 channels, on network 1.
Looking into the lms file I found that some channels were unit="1" as I would expect, but I also found many with garbage (!?) for the unit number... in the example below I found unit="39". I don't know why this happens. I can't find a way to straighten it out in the LSP msq sequence.
<channel name="Cheapo #1" color="255" centiseconds="113379" deviceType="LOR"
unit="39" circuit="21" savedIndex="89">
I can change all of the unit="\d+" values to unit="1" and my problem is fixed, and I have cleaned up the warnings.
I am interested to know if anyone else sees these problems.
I am also interested to know how light elf will correct for these issues. Sometime the network number is legitimately something other than "1", and overwriting that value would be wrong.
Steve