Nutcracker: What does this error mean?

[smeighan]

When i generate this effect in Nutcracker:


array_to_save
username   f
user_target   AA
effect_class   butterfly
effect_name   FLY_0_0
window_degrees   360
frame_delay   60
sparkles   0
seq_duration   5
formula   1
radian_shift   .05
start_color   #FFFFFF
end_color   #FFFFFF
background_chunk   #FFFFFF
background_skip   #FFFFFF
background_color   #000000
submit   Submit Form to create your effect
OBJECT_NAME   butterfly



I produced an lms file. It is located here: meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms

This file loads with no issues into LOR but if i load it into xlights, i get these messages

Reading LOR sequence
Track 1 length = 5000 centiseconds
WARNING: S1-P6-G and S2-P1-R map to the same channel
WARNING: S1-P6-B and S2-P1-G map to the same channel
WARNING: S1-P7-R and S2-P1-B map to the same channel
WARNING: S1-P7-G and S2-P2-R map to the same channel


Lets take the first line:
Here is what i have in the lms file:
<channel name="S1-P6-G" color="65280" centiseconds="0" deviceType="LOR" unit="1" circuit="17" savedIndex="16">
<effect type="intensity" startCentisecond="0" endCentisecond="6" intensity="100" />
<effect type="intensity" startCentisecond="6" endCentisecond="12" intensity="100" />
<effect type="intensity" startCentisecond="12" endCentisecond="18" intensity="91" />
<effect type="intensity" startCentisecond="18" endCentisecond="24" intensity="52" />


<channel name="S2-P1-R" color="255" centiseconds="0" deviceType="LOR" unit="2" circuit="1" savedIndex="300">
<effect type="intensity" startCentisecond="0" endCentisecond="6" intensity="73" />
<effect type="intensity" startCentisecond="6" endCentisecond="12" intensity="100" />
<effect type="intensity" startCentisecond="12" endCentisecond="18" intensity="100" />

Is there something here that says the channel is duplicated?

Maybe it is the RGB section of LOR?

Here are the two that i have mentioning these two pixels
<rgbChannel totalCentiseconds="5000" name="S1-P6" savedIndex="4802">
   <channels>
      <channel savedIndex="15"/>
      <channel savedIndex="16"/>
      <channel savedIndex="17"/>
   </channels>

<rgbChannel totalCentiseconds="5000" name="S2-P1" savedIndex="4897">
   <channels>
      <channel savedIndex="300"/>
      <channel savedIndex="301"/>
      <channel savedIndex="302"/>
   </channels>
</rgbChannel>

I also get errors like these:
WARNING: channel 'S16-P91-B' is unmapped
WARNING: channel 'S16-P92-R' is unmapped
WARNING: channel 'S16-P92-G' is unmapped
WARNING: channel 'S16-P92-B' is unmapped
WARNING: channel 'S16-P93-R' is unmapped

I expect these. These are where i do not have anything to output for that channel. When i see this, i am outputting a place holder
Here is what i have in the LMS file for the first error line
<channel name="S16-P91-B" color="16711680" centiseconds="0" deviceType="LOR" unit="16" circuit="273" savedIndex="4772">
</channel>


Should i not do this? Again, no errors or warnings when this file was loaded into LOR.

thanks

[Steve Gase]

I produced an lms file. It is located here: meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms

This file loads with no issues into LOR

I haven't tried this, but I wonder what would happen...

what if you saved back the lms file from LOR after it was imported "with no issues"...  would the newly-saved file also result in similar warnings when you imported THAT file into xLights?

If no messages you might compare the before/after effect of the LOR software to the file.

[smeighan]

I produced an lms file. It is located here: meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms

This file loads with no issues into LOR

I haven't tried this, but I wonder what would happen...

what if you saved back the lms file from LOR after it was imported "with no issues"...  would the newly-saved file also result in similar warnings when you imported THAT file into xLights?

If no messages you might compare the before/after effect of the LOR software to the file.

I tried this, i get this error "Tracke length = -1 centiseconds"

So i tried a lms file i downloaded from the net,
1) Load into LOR
2) Save as a new lms file
3) Try converting the new file in xlights

I get the same error. Maybe this is a known issue?

[tlh]

Is there something here that says the channel is duplicated?

<channel name="S1-P6-G" color="65280" centiseconds="0" deviceType="LOR" unit="1" circuit="17"
<channel name="S2-P1-R" color="255" centiseconds="0" deviceType="LOR" unit="2" circuit="1" savedIndex="300">

Hi-
I may be subject to correction, but I believe the duplication is related to the way xLights and LOR files define specific circuits/channels.  xLights assumes that each LOR controller (unit) has 16 channels (circuits), using the formula: xLights channel # = ((LOR Unit Number - 1) * 16) + LOR Circuit Number. Thus, within LOR, channel/circuit 17 can be represented as either unit="1" circuit="17" or unit="2" circuit="1".  Both S1-P6-G and S2-P1-R have defined the same xLights channel, which would mean you would not get an error in LOR, but would get the channel duplication issue in xLights.  Hope that helps. 
tlh/Terry

P.S.  I am just getting started with Nutcracker, and find it most impressive!

[Steve Gase]

Is there a way to treat them as CCRs?  ...with more channels in each unit?

[smeighan]

Is there something here that says the channel is duplicated?

<channel name="S1-P6-G" color="65280" centiseconds="0" deviceType="LOR" unit="1" circuit="17"
<channel name="S2-P1-R" color="255" centiseconds="0" deviceType="LOR" unit="2" circuit="1" savedIndex="300">

Hi-
I may be subject to correction, but I believe the duplication is related to the way xLights and LOR files define specific circuits/channels.  xLights assumes that each LOR controller (unit) has 16 channels (circuits), using the formula: xLights channel # = ((LOR Unit Number - 1) * 16) + LOR Circuit Number. Thus, within LOR, channel/circuit 17 can be represented as either unit="1" circuit="17" or unit="2" circuit="1".  Both S1-P6-G and S2-P1-R have defined the same xLights channel, which would mean you would not get an error in LOR, but would get the channel duplication issue in xLights.  Hope that helps. 
tlh/Terry

P.S.  I am just getting started with Nutcracker, and find it most impressive!

So the root cause of the error is the assumption that lms files will be driving LOR hardware. Probably normally valid, but i am creating lms files with 16 strings of 128 pixels for example. This allows people to also import the lms file into LOR.

I think LOR folks are using ELOR and E681's and are going to get more than 50 pixels on a string. LOR seems to correctly import the lms files i create.

Can the warning just be ignored or is it an issue.

BTW, i produced the exact same butterfly effect as a Vixen vir file, imported into vixen and saved as a vix file. xLights read that file in with no errors. Xlights apparently does not have this assumption about strings and pixels for Vixen files.

[tlh]

So the root cause of the error is the assumption that lms files will be driving LOR hardware. Probably normally valid, but i am creating lms files with 16 strings of 128 pixels for example. This allows people to also import the lms file into LOR.

I think LOR folks are using ELOR and E681's and are going to get more than 50 pixels on a string. LOR seems to correctly import the lms files i create.

Can the warning just be ignored or is it an issue.

BTW, i produced the exact same butterfly effect as a Vixen vir file, imported into vixen and saved as a vix file. xLights read that file in with no errors. Xlights apparently does not have this assumption about strings and pixels for Vixen files.

I do not use LOR to run my shows (I use xLights), but I think it is an issue that cannot be ignored.  Quoting the LOR help file, "do not simply set up two different channels having the same unit number, circuit number, et cetera in the two tracks; this will have unexpected and undesired results, as the two different channels will compete with each other for control of the same circuit."  I can attest to the undesired results - I had two channels with the same ID, and it was ugly.   

I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR).  For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1.  The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1. 

Again, that is my hunch, and others will have to verify.  Last year, I ran 12 flex strings programmed with SuperStar Lights in LOR and converted to xLights.  It was important that the channels did not overlap, and I had to watch the Hex IDs closely.   
tlh/Terry

[smeighan]

So the root cause of the error is the assumption that lms files will be driving LOR hardware. Probably normally valid, but i am creating lms files with 16 strings of 128 pixels for example. This allows people to also import the lms file into LOR.

I think LOR folks are using ELOR and E681's and are going to get more than 50 pixels on a string. LOR seems to correctly import the lms files i create.

Can the warning just be ignored or is it an issue.

BTW, i produced the exact same butterfly effect as a Vixen vir file, imported into vixen and saved as a vix file. xLights read that file in with no errors. Xlights apparently does not have this assumption about strings and pixels for Vixen files.

I do not use LOR to run my shows (I use xLights), but I think it is an issue that cannot be ignored.  Quoting the LOR help file, "do not simply set up two different channels having the same unit number, circuit number, et cetera in the two tracks; this will have unexpected and undesired results, as the two different channels will compete with each other for control of the same circuit."  I can attest to the undesired results - I had two channels with the same ID, and it was ugly.   

I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR).  For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1.  The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1. 

Again, that is my hunch, and others will have to verify.  Last year, I ran 12 flex strings programmed with SuperStar Lights in LOR and converted to xLights.  It was important that the channels did not overlap, and I had to watch the Hex IDs closely.   
tlh/Terry

i can do the above. This will allow my lms files to go into xlights without an error.

Another way to solve this, i will start producing a vixen vix file.

My goal , i believe, is to get my show from Nutcracker to xlights.

[smeighan]

Ok, i made a change that sets the unit number to be
multiples of 16.

i have a 16x100 tree.
First string , pixel 1 the unit is 1 and the circuit is 1
second string, pixel 1 the unit is 19, circuit is 1

Almost all of those cross mapping error messages are gone.




I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR).  For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1.  The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1. 

Now i am getting  a bunch of these

WARNING: channel 'S2-P99-G' is unmapped
WARNING: channel 'S2-P99-B' is unmapped
WARNING: channel 'S2-P100-R' is unmapped
WARNING: channel 'S2-P100-G' is unmapped
WARNING: channel 'S2-P100-B' is unmapped
WARNING: channel 'S3-P1-R' is unmapped
WARNING: channel 'S3-P1-G' is unmapped
WARNING: channel 'S3-P1-B' is unmapped
WARNING: channel 'S3-P2-R' is unmapped
WARNING: channel 'S3-P2-G' is unmapped
WARNING: channel 'S3-P2-B' is unmapped
WARNING: channel 'S3-P3-R' is unmapped
WARNING: channel 'S3-P3-G' is unmapped
WARNING: channel 'S3-P3-B' is unmapped
WARNING: channel 'S3-P4-R' is unmapped
WARNING: channel 'S3-P4-G' is unmapped
WARNING: channel 'S3-P4-B' is unmapped
WARNING: channel 'S3-P5-R' is unmapped
WARNING: channel 'S3-P5-G' is unmapped
WARNING: channel 'S3-P5-B' is unmapped
WARNING: channel 'S3-P6-R' is unmapped
WARNING: channel 'S3-P6-G' is unmapped
WARNING: channel 'S3-P6-B' is unmapped
WARNING: channel 'S3-P7-R' is unmapped
WARNING: channel 'S3-P7-G' is unmapped
WARNING: channel 'S3-P7-B' is unmapped
WARNING: channel 'S3-P8-R' is unmapped
WARNING: channel 'S3-P8-G' is unmapped
WARNING: channel 'S3-P8-B' is unmapped
WARNING: channel 'S3-P9-R' is unmapped
WARNING: channel 'S3-P9-G' is unmapped
WARNING: channel 'S3-P9-B' is unmapped
WARNING: channel 'S3-P10-R' is unmapped
WARNING: channel 'S3-P10-G' is unmapped

Strange, LOR gives no errors when it loads this file and the preview looks correct.
meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms

[Steve Gase]

My goal , i believe, is to get my show from Nutcracker to xlights.

That would be the ideal scenario.

Finding a universal format would be cool:

--------------------------------------	--------------------------------------	--------------------------------------
Software:	Can import...	Can export...
LOR S3	.las (LOR II Animated Sequence) .lms (LOR II Music Sequence)	.las (LOR II Animated Sequence) .lms (LOR II Music Sequence)
--------------------------------------	--------------------------------------	--------------------------------------
LSP 2	.asq (Animated Sequence) .dls (Downloadable Sounds?) .lms (LOR II Music Sequence) .mpj (Animated Lighting Routine) .msq (Musical Sequence) .vix (Vixen Standard Sequence)	.asq (Animated Sequence) .lms (LOR II Music Sequence) .mpj (Animated Lighting Routine) .msq (Musical Sequence) .oms (Optimized Musical Sequence)
--------------------------------------	--------------------------------------	--------------------------------------
Vixen 2	.vix (Vixen Standard Sequence)	.vix (Vixen Standard Sequence)
--------------------------------------	--------------------------------------	--------------------------------------
Nutcracker 4/30/12	none	.hls (Helix Sequence) .lcb (LOR II Clipboard) .lms (LOR II Music Sequence) .vix (Vixen Standard Sequence)
--------------------------------------	--------------------------------------	--------------------------------------

[dowdybrown]

Ok, i made a change that sets the unit number to be
multiples of 16.

i have a 16x100 tree.
First string , pixel 1 the unit is 1 and the circuit is 1
second string, pixel 1 the unit is 19, circuit is 1

Almost all of those cross mapping error messages are gone.




I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR).  For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1.  The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1. 

Now i am getting  a bunch of these

WARNING: channel 'S2-P99-G' is unmapped
WARNING: channel 'S2-P99-B' is unmapped
WARNING: channel 'S2-P100-R' is unmapped
WARNING: channel 'S2-P100-G' is unmapped
WARNING: channel 'S2-P100-B' is unmapped
WARNING: channel 'S3-P1-R' is unmapped
WARNING: channel 'S3-P1-G' is unmapped
WARNING: channel 'S3-P1-B' is unmapped
WARNING: channel 'S3-P2-R' is unmapped
WARNING: channel 'S3-P2-G' is unmapped
WARNING: channel 'S3-P2-B' is unmapped
WARNING: channel 'S3-P3-R' is unmapped
WARNING: channel 'S3-P3-G' is unmapped
WARNING: channel 'S3-P3-B' is unmapped
WARNING: channel 'S3-P4-R' is unmapped
WARNING: channel 'S3-P4-G' is unmapped
WARNING: channel 'S3-P4-B' is unmapped
WARNING: channel 'S3-P5-R' is unmapped
WARNING: channel 'S3-P5-G' is unmapped
WARNING: channel 'S3-P5-B' is unmapped
WARNING: channel 'S3-P6-R' is unmapped
WARNING: channel 'S3-P6-G' is unmapped
WARNING: channel 'S3-P6-B' is unmapped
WARNING: channel 'S3-P7-R' is unmapped
WARNING: channel 'S3-P7-G' is unmapped
WARNING: channel 'S3-P7-B' is unmapped
WARNING: channel 'S3-P8-R' is unmapped
WARNING: channel 'S3-P8-G' is unmapped
WARNING: channel 'S3-P8-B' is unmapped
WARNING: channel 'S3-P9-R' is unmapped
WARNING: channel 'S3-P9-G' is unmapped
WARNING: channel 'S3-P9-B' is unmapped
WARNING: channel 'S3-P10-R' is unmapped
WARNING: channel 'S3-P10-G' is unmapped

Strange, LOR gives no errors when it loads this file and the preview looks correct.
meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms

I think you are getting close! What lighting networks do you have do you have defined in xLights? This error means that the channels you are importing don't match up to the networks you have defined in xLights.

Matt

[Steve Gase]

I think you are getting close! What lighting networks do you have do you have defined in xLights? This error means that the channels you are importing don't match up to the networks you have defined in xLights.

Matt

in my case, I had 9 strings of 85 pixels each defined in nutcracker, and exported as LMS.
in xlights I had E1.31 with 3 universes of 512 channels each. 

HOWEVER,
i got the mismatch upon doing a file conversion from lms to xseq -- is the network definition used for the file conversion?

[smeighan]

Ok, i made a change that sets the unit number to be
multiples of 16.

i have a 16x100 tree.
First string , pixel 1 the unit is 1 and the circuit is 1
second string, pixel 1 the unit is 19, circuit is 1

Almost all of those cross mapping error messages are gone.




I suspect that you'll have to adopt LOR's channel system in order for the files to play correctly (in xLights or LOR).  For example, with a 128 string node (assuming a starting channel of 1), the first string would have a Unit (Hex) ID of "1" and Circuit # 1.  The remaining 383 channels for that string could follow sequentially on Unit 1 through circuit 384. For string two, the Unit (Hex) ID would be 19 (i.e., the 25th, 16-channel), with a Circuit ID of 1. 

Now i am getting  a bunch of these

WARNING: channel 'S2-P99-G' is unmapped
WARNING: channel 'S2-P99-B' is unmapped
WARNING: channel 'S2-P100-R' is unmapped
WARNING: channel 'S2-P100-G' is unmapped
WARNING: channel 'S2-P100-B' is unmapped
WARNING: channel 'S3-P1-R' is unmapped
WARNING: channel 'S3-P1-G' is unmapped
WARNING: channel 'S3-P1-B' is unmapped
WARNING: channel 'S3-P2-R' is unmapped
WARNING: channel 'S3-P2-G' is unmapped
WARNING: channel 'S3-P2-B' is unmapped
WARNING: channel 'S3-P3-R' is unmapped
WARNING: channel 'S3-P3-G' is unmapped
WARNING: channel 'S3-P3-B' is unmapped
WARNING: channel 'S3-P4-R' is unmapped
WARNING: channel 'S3-P4-G' is unmapped
WARNING: channel 'S3-P4-B' is unmapped
WARNING: channel 'S3-P5-R' is unmapped
WARNING: channel 'S3-P5-G' is unmapped
WARNING: channel 'S3-P5-B' is unmapped
WARNING: channel 'S3-P6-R' is unmapped
WARNING: channel 'S3-P6-G' is unmapped
WARNING: channel 'S3-P6-B' is unmapped
WARNING: channel 'S3-P7-R' is unmapped
WARNING: channel 'S3-P7-G' is unmapped
WARNING: channel 'S3-P7-B' is unmapped
WARNING: channel 'S3-P8-R' is unmapped
WARNING: channel 'S3-P8-G' is unmapped
WARNING: channel 'S3-P8-B' is unmapped
WARNING: channel 'S3-P9-R' is unmapped
WARNING: channel 'S3-P9-G' is unmapped
WARNING: channel 'S3-P9-B' is unmapped
WARNING: channel 'S3-P10-R' is unmapped
WARNING: channel 'S3-P10-G' is unmapped

Strange, LOR gives no errors when it loads this file and the preview looks correct.
meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms

I think you are getting close! What lighting networks do you have do you have defined in xLights? This error means that the channels you are importing don't match up to the networks you have defined in xLights.

Matt

I changed to pixlenet and most of the unmatched went away.

Here is the new list


Reading LOR sequence
Track 1 length = 5000 centiseconds
WARNING: S3-P97-R and S4-P1-R map to the same channel
WARNING: S3-P97-G and S4-P1-G map to the same channel
WARNING: S3-P97-B and S4-P1-B map to the same channel
WARNING: S3-P98-R and S4-P2-R map to the same channel
WARNING: S3-P98-G and S4-P2-G map to the same channel
WARNING: S3-P98-B and S4-P2-B map to the same channel
WARNING: S3-P99-R and S4-P3-R map to the same channel
WARNING: S3-P99-G and S4-P3-G map to the same channel
WARNING: S3-P99-B and S4-P3-B map to the same channel
WARNING: S3-P100-R and S4-P4-R map to the same channel
WARNING: S3-P100-G and S4-P4-G map to the same channel
WARNING: S3-P100-B and S4-P4-B map to the same channel
WARNING: S7-P97-R and S8-P1-R map to the same channel
WARNING: S7-P97-G and S8-P1-G map to the same channel
WARNING: S7-P97-B and S8-P1-B map to the same channel
WARNING: S7-P98-R and S8-P2-R map to the same channel
WARNING: S7-P98-G and S8-P2-G map to the same channel
WARNING: S7-P98-B and S8-P2-B map to the same channel
WARNING: S7-P99-R and S8-P3-R map to the same channel
WARNING: S7-P99-G and S8-P3-G map to the same channel
WARNING: S7-P99-B and S8-P3-B map to the same channel
WARNING: S7-P100-R and S8-P4-R map to the same channel
WARNING: S7-P100-G and S8-P4-G map to the same channel
WARNING: S7-P100-B and S8-P4-B map to the same channel
WARNING: S11-P97-R and S12-P1-R map to the same channel
WARNING: S11-P97-G and S12-P1-G map to the same channel
WARNING: S11-P97-B and S12-P1-B map to the same channel
WARNING: S11-P98-R and S12-P2-R map to the same channel
WARNING: S11-P98-G and S12-P2-G map to the same channel
WARNING: S11-P98-B and S12-P2-B map to the same channel
WARNING: S11-P99-R and S12-P3-R map to the same channel
WARNING: S11-P99-G and S12-P3-G map to the same channel
WARNING: S11-P99-B and S12-P3-B map to the same channel
WARNING: S11-P100-R and S12-P4-R map to the same channel
WARNING: S11-P100-G and S12-P4-G map to the same channel
WARNING: S11-P100-B and S12-P4-B map to the same channel
WARNING: S15-P97-R and S16-P1-R map to the same channel
WARNING: S15-P97-G and S16-P1-G map to the same channel
WARNING: S15-P97-B and S16-P1-B map to the same channel
WARNING: S15-P98-R and S16-P2-R map to the same channel
WARNING: S15-P98-G and S16-P2-G map to the same channel
WARNING: S15-P98-B and S16-P2-B map to the same channel
WARNING: S15-P99-R and S16-P3-R map to the same channel
WARNING: S15-P99-G and S16-P3-G map to the same channel
WARNING: S15-P99-B and S16-P3-B map to the same channel
WARNING: S15-P100-R and S16-P4-R map to the same channel
WARNING: S15-P100-G and S16-P4-G map to the same channel
WARNING: S15-P100-B and S16-P4-B map to the same channel
# of mapped channels with effects=4797
# of effects=154681
Media file=
New # of time periods=1000
New data len=4800000
Writing xLights sequence
Finished writing new file: C:\Users\sean\Documents\Light-O-Rama\Sequences\AA+FLY_0_0.xseq
Finished converting all files


I notice any channel > 96 is coming up unmapped.

I have 16 strings of 100 pixels each.

[dowdybrown]

Do you just have one pixelnet network defined in xLights? Since Pixelnet is 4096 channels and your configuration requires 4800, I'm just wondering what you are doing with the last 704 channels.

Try adding a second pixelnet network in xLights and changing the LOR sequence mapping in xLights to single network.

Matt

[smeighan]

Do you just have one pixelnet network defined in xLights? Since Pixelnet is 4096 channels and your configuration requires 4800, I'm just wondering what you are doing with the last 704 channels.

Try adding a second pixelnet network in xLights and changing the LOR sequence mapping in xLights to single network.

Matt

since i own no hardware and have never used any othese interfaces, i am probably seting something up wrong.

here is the file i am trying to import
meighan.net/htdocs/nutcracker/effects/workspaces/2/AA+FLY_0_0.lms