Author Topic: Importing LOR / LMS Data Layer problem and fix  (Read 2048 times)

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Importing LOR / LMS Data Layer problem and fix
« on: July 22, 2015, 09:28:58 PM »
I had this problem all last season and so did FDunham (Fred).

What happens is that when we either Convert (in Nutracker 3) or Import as a Data Layer in Nutcracker 4, it does NOT like our old LOR sequences.

What it does is related to various things like Tracks and Beat Channels. It confuses the import enough that it shifts ALL the data by Two DMX Universes (1024 channels).

So, tonight I was checking to see if that was still happening. Yes, it was.
But, as you can see in the attached picture, there is an "Offset" option in the Data Layer.
If I manually edit that number to be negative 1024 ( -1024), then click Done, then Save, it moves all my data down for me.

I am verifying that it works in the Preview Window by creating some non-RGB models that exist only in my LOR sequence. After applying the -1024 offset, they display perfectly.


Offline Gilrock

  • Supporting Member
  • Hero Member
  • *
  • Posts: 6946
    • View Profile
Re: Importing LOR / LMS Data Layer problem and fix
« Reply #1 on: July 22, 2015, 09:40:20 PM »
What options are you selecting for the LOR Import?  The "Map Empty LMS Channels" and "Map LMS Channels with no network" can affect the number of channels imported.  I leave those blank myself because I don't want xLights to map my beat channels (which doesn't have a network) and none of my channels I want are empty so I don't need the other option either.

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Importing LOR / LMS Data Layer problem and fix
« Reply #2 on: July 22, 2015, 09:52:03 PM »
I have tried with all combinations of those check boxes. Depending on my LOR sequence, it would either import correctly or shift it by 1024.

I did find that if I went into my LOR sequence and got it down to a single Master Track with no blank channels, it would work. That was way too much work. It has something to do with the Import or Conversion process detecting two "networks" that no longer exist. This problem probably dates back to when I actually used LOR protocol, then switched my sequences by manually changing EACH element to DMX. There is some trash somewhere in those old files.

Never could find it conclusively. Now I don't have to. I will probably IMPORT 3 or 4 of my old sequences for 2015. Everything else will probably be a total new Nutcracker 4.0 creation with no LOR data layer at all. I'm working at creating all my old single channel elements as models over the next few days.

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Importing LOR / LMS Data Layer problem and fix
« Reply #3 on: August 04, 2015, 08:59:40 PM »
I'll add a little to this for LOR users looking to bring in their LMS files.

My "problem" on import is that many of my old LMS files still think they have LOR Network (USB dongle) information. I haven't found the magic bullet in the import settings to make it ignore them short of re-creating the LMS file with massive Copy/Paste efforts. Time consuming and error likely.

If you do a "convert" in xLights of an LMS file to an FSEQ file, and you notice that it consistently lists an LOR Network or two before beginning the DMX networks, then the conversion or Data Layer import process is going to "add" 512 channels for every LOR Network it thinks you have.

Since I really don't have any, but it lists 2, all my DMX channels were 1024 too high.
Adding the channel offset of -1024 removed the offset easily and effectively.