Conversion of LMS files is not working for me anymore

[JonB256]

Ran across this earlier today with fdunham (Fred) because his LOR data in DMX Universe #1 was not playing.

We accidentally found out that the Nutcracker 3.6.11 conversion was transposing his Universe #1 into Universe #3.
He was checking the boxes for blank channels and No network (my first question).

So, what should have been Channel #1 was actually Channel #1025.  We updated his FPD outputs to start at 1025 instead of 1, restarted the Player, and it worked.  Pixelnet data inserted from Nutcracker was still perfect.

So, any ideas why it got moved?

Oh, and I just went back into one of my own LOR files and updated it. Converted it to XSEQ.  Guess what - all my DMX from LOR is missing/shifted. 

JonB

[JonB256]

Troubleshooting results -

If I go all the way back to version 3.0.2 (March of 2013) and convert the same LMS file to XSEQ, then all my DMX data is right were it belongs.

So, until this gets sorted, I'll use the "old" version workaround if I need to convert.

[dkulp]

Check the very top of the status messages.   It will tell you what it found in the file.   If the DMX stuff is shifted, that usually means it has found some LOR networks.   

[JonB256]

Check the very top of the status messages.   It will tell you what it found in the file.   If the DMX stuff is shifted, that usually means it has found some LOR networks.

It does say that it found some LOR networks. But I don't have any and haven't for years.  I'm assuming that is what causes the problem.

As I said, though, if I use the very old version of xLights, it converts and works perfectly.

I'll create a completely new LOR sequence and see if I still get any LOR Network conversion messages.

[dkulp]

The old version may or may not have worked perfectly.   The old version mapped both DMX 1 and LOR 1 to the same output and would end up over writing things depending on what is found first in the LMS file.   If the LOR stuff was first, it would map the LOR stuff, then would over write the LOR stuff with the DMX stuff.   If the DMX stuff was first in the file, the reverse would have been true.   You may have just been "lucky" that LOR stuck you DMX stuff later in the file.

If you have access to a unix like machine that has grep installed, you can do something like:

Code: [Select]

grep "deviceType" sequencename.lms | grep -v DMX

to get a list of channels not defined with DMX.  That may be able to help you fix those channels.

[JonB256]

Looking through one of my oldest "legacy" LOR files, I find 556 channel entries that include a unit="##" between the DMX Universe value and the circuit value. Most lines omit the unit value.

The lines with a unit value are some of the "oldest" elements.
I will try a search and replace to remove the unit value and see how it works.

I do have a Linux laptop and will try the GREP later.  Thanks for checking.

update -
Editing out all the Unit references did not corrupt the LMS file, but it also still converts showing LOR Network 1 and LOR Network 2 which is probably why it is shifting me by 2 universes (1024).

[JonB256]

Another test - when I create a totally new LOR sequence and DON'T use my old layout template, just a bunch of pure DMX channels, the file does convert in xLights 3.6.12 without showing any LOR Network entries and it displays properly in the preview window (DMX channels from 33 to 272 are on)

[dkulp]

If you are hand editing the file, search for network="1" or deviceType="LOR

They may help find the LOR channels.


Sent from my iPhone using Tapatalk

[sean]

I just want to take a moment to thank Dan Kulp! Dan is an HLS user, he has no LOR hardware, no LOR experience creating sequences in LOR. He took over the task of fixing some issue with the LOR import in xlights last spring, Because he did that, I send all LOR conversion questions to him.

He is probably sorry he helped out. I really appreciate all the improvements and the support he has given to the LOR user base.

Thanks Dan!

sean

[rando1957]

Thanks Dan - All my conversions have worked perfectly once I knew to remove tracks and blank, unassigned channels.  Not one single issue with my conversions.
Randy