Messages

1

Do You Need Help? Post it here / Re: Import of mega tree sequence applies to other model

« on: November 14, 2016, 07:57:15 AM »

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? 

2

Do You Need Help? Post it here / Re: Import of mega tree sequence applies to other model

« on: November 12, 2016, 01:29:16 PM »

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?

3

Do You Need Help? Post it here / Import of mega tree sequence applies to other model

« on: November 12, 2016, 01:05:13 PM »

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?