Import of mega tree sequence applies to other model

[lonepainter]

I am using an AlphaPix 16 if it has any bearing on the issue.  I have added 16 SPI and 3 DMX outputs to Xlights, created a tree and star model.  In the tree model I specify each universe and start channel.  The star is using the three DMX outputs to (3) three channel dumb controllers. 

When I import the sequence, I specify only the tree model, however it is being rendered on both the tree and star.  I have tried creating a single model, import then create the star, yet it still renders on the star after adding it as a new model.

How can I force the rendering to only occur on the tree model?  Better yet, how can I map the 6 channel LOR channels to my DMX channels?

[Gilrock]

There are two import methods so we need to know what steps you are using.  It sounds like the channels overlap.

[lonepainter]

I performed the import via the "New Sequence" and selected the LOR sup file and lms files.  Would I be able to see the overlap in a file?   I created 16 universes for the SP1 connections (#1:1 through #16:1) and 3 for the DMX (#50:1 through #52:1), which I had hoped would prevent overlap.

What can I provide to make it easier to find the issue?

[Gilrock]

As far as I know you cannot select a .sup file during the new sequence wizard that can only be done using the "Import Effects" function after you create a sequence.  The new sequence import is creating a data layer.  To figure out where its going to place the data you need to just do a Convert and select the LMS file and check the verbose channel map option and it will list how it maps all the LOR channels to the xlights channels.  You don't need the results of the conversion but it will let you know how it doing the mapping because it uses the same process.

[lonepainter]

Thanks for the help Gil.  I read further into the manual and found the section on importing LOR sequences to non LOR hardware.  I added an entry for a LOR controller with 6 channels, moved it to the beginning of my channel setup.  Then performed the "convert" to a .xseq,  deleted the LOR controller
, imported the subsequent .xseq file that was created as what I believe is a data layer.  All is working as intended now.

You mentioned there are multiple ways to import sequences, would you be able to explain more about that? 

[Gilrock]

1) You can import by creating a Data Layer which will be fixed data only that cannot be manipulated.

2) You can use the Import Effects feature where you create a mapping file mapping every channel you are importing to the model/channel you want it to land on in xLights.  This method creates editable effects.

By the way we don't use the .xseq format anymore that is only there to support xLights3 sequences.  You should convert to fseq files but technically you did in 2 steps what you could do in one.  Just import the LMS file as a data layer.

[sean]

sup files really work well using Gil's (2) above. Use "Import, Import Effects". Each effect that was in superstar is mapped to o an xlights effect. Besides bring in the sequence it has the additional advantage that you can edit the sequence.