Import not working when a model is split across controllers

[PKingRoch]

I'm importing an LOR LMS file into xLights.  I have a sequence in xLights that has a model split across two controllers and is not contiguous.  The model is a group of arches with individual start channels for each arch, eight in total.  The first two arches/strings are on one controller and they import fine, the other 6 arches are on a different controller and the channels are not contiguous.  My last 6 arches are not being input and I see this warning in the verify sequence log:

Models spanning controllers
    WARN: Model 'Arches' starts on controller 'CCR1' with IP '192.168.0.51' but ends on a controller 'CCR 2-4' with IP '192.168.0.61'.

This of course has many other warnings about other overlapping channels as well.

In order for my sequence to be imported correctly, do the channels need to be contiguous?  My LOR sequence has a gap on the universe number and starting channel numbers, but I'm not sure if xLights handles imports that way.
Thanks!

Paul

[keithsw1111]

The model spans controllers warning is ok

But the lor inport has some rules which I don’t recall the details of that require all channels to be defined in lor.


Sent from my iPhone using Tapatalk

[PKingRoch]

I think this may have been my problem. I didn't have the blank universes defined in xLights.  I've since changed my network layout and everything is working just fine.

[Gilrock]

If your stuff in LOR is defined as universe/channel numbers it should not matter if there are gaps because we will just match up the universe numbers.  You just need to have an xLights setup that matches.  Plus I haven't tried in awhile but I thought the new import mapping method made it so that there are no restrictions since you could just map one model if you wanted which is something you couldn't do in the old way.