"simple tree" solution

[Steve Gase]

In a presentation (yesterday) about Lynx Smart Strings, xLights and Nutcracker, I suggested that a "simple" solution could exist that allows you to create your sequencing in Nutcracker as LMS output, and import that into xLights so that LSP and LOR could be completely side-stepped.

This could be useful for a standalone tree that ignores all of the other elements in the yard -- like arches, bushes, etc.

Here is the plan:

1) create the target model in Nutcracker
2) create a series of effects and apply them to the target -- exporting each to LMS

3) for each LMS file, convert to xseq files inside xLights
4) create a schedule that pulls in each of the xseq files

5) assemble the tree
6) load the xseq configuration into EtherDongle conductor -- OR use your computer

7) enjoy


Thoughts?

[Steve Gase]

I pulled together working hardware and lights before my Saturday walkthrough, but I didn't try doing the Nutcracker/xLights steps before the session...  like the worst presenter, I tried it for the first time during my presentation.     

After creating the target, effects and LMS file I tried to import the LMS directly into xLights.  It generated LOTs of similar warning messages. 

it would be great to see a solution available to make this a simple error/warning-free configuration that works without going through hoops. 

As a quick solution...

Maybe channel number can be assigned as:
  ChannelNum  :=  ((StringNum - 1) x (pixelCnt)) + PixelNum

(assuming that numbers are 1-based...)

It would work well for me, because I have assigned my pixel channels within a contiguous block that fits on a single 4096-channel hub.

I could create a filter to transform the file, but I think for other users it would be great to just have it work for the simplest of configurations.  Regardless of how you assign channels, I think ensuring that no channel number should be reused -- it will eliminate the loading problem.  in another tool remapping could be addressed, or more robustly addressed by Nutcracker.

Here are the warnings from Nutcracker user "sgase", target model "PTREE10" and effect "SPIRAL1":

Code: You are not allowed to view links. Register or Login

Reading LOR sequence
Track 1 length = 10000 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
WARNING: S1-P7-B and S2-P2-G map to the same channel
WARNING: S1-P8-R and S2-P2-B map to the same channel
WARNING: S1-P8-G and S2-P3-R map to the same channel
WARNING: S1-P8-B and S2-P3-G map to the same channel
WARNING: S1-P9-R and S2-P3-B map to the same channel
WARNING: S1-P9-G and S2-P4-R map to the same channel
WARNING: S1-P9-B and S2-P4-G map to the same channel
WARNING: S1-P10-R and S2-P4-B map to the same channel
WARNING: S1-P10-G and S2-P5-R map to the same channel
WARNING: S1-P10-B and S2-P5-G map to the same channel
WARNING: S1-P11-R and S2-P5-B map to the same channel
WARNING: S1-P11-G and S2-P6-R map to the same channel
WARNING: S1-P11-B and S2-P6-G map to the same channel
WARNING: S1-P12-R and S2-P6-B map to the same channel
WARNING: S1-P12-G and S2-P7-R map to the same channel
...
WARNING: S9-P83-B and S10-P78-G map to the same channel
WARNING: S9-P84-R and S10-P78-B map to the same channel
WARNING: S9-P84-G and S10-P79-R map to the same channel
WARNING: S9-P84-B and S10-P79-G map to the same channel
WARNING: S9-P85-R and S10-P79-B map to the same channel
WARNING: S9-P85-G and S10-P80-R map to the same channel
WARNING: S9-P85-B and S10-P80-G map to the same channel
# of mapped channels with effects=2541
# of effects=798
Media file=
New # of time periods=2000
New data len=3072000
Writing xLights sequence
Finished writing new file: C:\Users\steve_gase\Desktop\PTREE10+SPIRAL1.xseq
Finished converting all files


[smeighan]

I pulled together working hardware and lights before my Saturday walkthrough, but I didn't try doing the Nutcracker/xLights steps before the session...  like the worst presenter, I tried it for the first time during my presentation.     

After creating the target, effects and LMS file I tried to import the LMS directly into xLights.  It generated LOTs of similar warning messages. 

it would be great to see a solution available to make this a simple error/warning-free configuration that works without going through hoops. 

As a quick solution...

Maybe channel number can be assigned as:
  ChannelNum  :=  ((StringNum - 1) x (pixelCnt)) + PixelNum

(assuming that numbers are 1-based...)

It would work well for me, because I have assigned my pixel channels within a contiguous block that fits on a single 4096-channel hub.

I could create a filter to transform the file, but I think for other users it would be great to just have it work for the simplest of configurations.  Regardless of how you assign channels, I think ensuring that no channel number should be reused -- it will eliminate the loading problem.  in another tool remapping could be addressed, or more robustly addressed by Nutcracker.

Here are the warnings from Nutcracker user "sgase", target model "PTREE10" and effect "SPIRAL1":

Code: You are not allowed to view links. Register or Login

Reading LOR sequence
Track 1 length = 10000 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
WARNING: S1-P7-B and S2-P2-G map to the same channel
WARNING: S1-P8-R and S2-P2-B map to the same channel
WARNING: S1-P8-G and S2-P3-R map to the same channel
WARNING: S1-P8-B and S2-P3-G map to the same channel
WARNING: S1-P9-R and S2-P3-B map to the same channel
WARNING: S1-P9-G and S2-P4-R map to the same channel
WARNING: S1-P9-B and S2-P4-G map to the same channel
WARNING: S1-P10-R and S2-P4-B map to the same channel
WARNING: S1-P10-G and S2-P5-R map to the same channel
WARNING: S1-P10-B and S2-P5-G map to the same channel
WARNING: S1-P11-R and S2-P5-B map to the same channel
WARNING: S1-P11-G and S2-P6-R map to the same channel
WARNING: S1-P11-B and S2-P6-G map to the same channel
WARNING: S1-P12-R and S2-P6-B map to the same channel
WARNING: S1-P12-G and S2-P7-R map to the same channel
...
WARNING: S9-P83-B and S10-P78-G map to the same channel
WARNING: S9-P84-R and S10-P78-B map to the same channel
WARNING: S9-P84-G and S10-P79-R map to the same channel
WARNING: S9-P84-B and S10-P79-G map to the same channel
WARNING: S9-P85-R and S10-P79-B map to the same channel
WARNING: S9-P85-G and S10-P80-R map to the same channel
WARNING: S9-P85-B and S10-P80-G map to the same channel
# of mapped channels with effects=2541
# of effects=798
Media file=
New # of time periods=2000
New data len=3072000
Writing xLights sequence
Finished writing new file: C:\Users\steve_gase\Desktop\PTREE10+SPIRAL1.xseq
Finished converting all files


Guess, i will need to install xlights and try this out.

thanks