Author Topic: Convert from LOR/LMS to XSEQ giving unexpected messages  (Read 5666 times)

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Convert from LOR/LMS to XSEQ giving unexpected messages
« on: November 20, 2014, 08:37:37 AM »
By Unexpected Message, it is telling me that it finds 2 LOR Networks with channels.
I don't have any LOR networks defined, only DMX, and my setup is 100% E1.31 (32 universes)
I do have some old, abandoned channels with "No Network" defined. Could it be counting those?

I don't remember this from last year (who knows what version :( ) but I'm seeing it this year in 3.6.4


[attachment deleted by admin]
« Last Edit: November 20, 2014, 08:39:16 AM by JonB256 »

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #1 on: November 20, 2014, 08:50:09 AM »
Note - I did go back through the old releases - in Nov 2013 I was probably using ver 3.2.9, so I installed that.

Back then, there was no "Map Blank Channels" choice, just "All channels off at end:"
So I tried it and I don't see anything about LOR Networks in the older messages, but I do see messages about blank channels being unmapped.

Is there any reason that I must use the newer 3.6.4 conversion program to get LMS into XSEQ ?
I used both versions (3.6.4 and 3.2.9) on the same file and the final XSEQ is identical in size.
« Last Edit: November 20, 2014, 08:55:30 AM by JonB256 »

Offline Lights On Fifth

  • Sr. Member
  • ****
  • Posts: 287
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #2 on: November 20, 2014, 08:56:05 AM »
Note - I did go back through the old releases - in Nov 2013 I was probably using ver 3.2.9, so I installed that.

Back then, there was no "Map Blank Channels" choice, just "All channels off at end:"
So I tried it and I don't see anything about LOR Networks in the older messages, but I do see messages about blank channels being unmapped.

Is there any reason that I must use the newer 3.6.4 conversion program to get LMS into XSEQ ?

I just downloaded the newest version of xlights, last night I converted all my sequences from Lor over to xlights with no hiccups at all, it might be worth a shot at it. the problem I was having is I had tracks with in my Lor seqs, after I removed all the tracks the conversions were flawless.
Don Gillespie
Medicine Hat Ab.

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #3 on: November 20, 2014, 08:59:10 AM »
The problem I was having is I had tracks with in my Lor seqs, after I removed all the tracks the conversions were flawless.

Don, I have tracks in mine, also, but it never made a difference because my Master Track had 100% of all channels in other tracks.

I may try removing the Tracks from a copy of the LMS files and see what it does differently.

Update - removed tracks, re-converted. Conversion messages are virtually unchanged; still say I have 2 LOR networks.
Next step may be to remove the undefined channels. A bit more labor intensive.
« Last Edit: November 20, 2014, 09:07:20 AM by JonB256 »

Offline rando1957

  • Full Member
  • ***
  • Posts: 200
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #4 on: November 20, 2014, 10:16:33 AM »
I know my setup is probably more simple, but I ended having to remove my 'dummy' channels for beats in LOR before I converted to xseq. After that it worked fine.
Randy McMasters
Graham, NC

Offline Lights On Fifth

  • Sr. Member
  • ****
  • Posts: 287
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #5 on: November 20, 2014, 10:42:03 AM »
Yes you can not have any beat channels or timing channels xlights doesn't like them
Don Gillespie
Medicine Hat Ab.

Offline Lights On Fifth

  • Sr. Member
  • ****
  • Posts: 287
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #6 on: November 20, 2014, 10:43:17 AM »
The problem I was having is I had tracks with in my Lor seqs, after I removed all the tracks the conversions were flawless.

Don, I have tracks in mine, also, but it never made a difference because my Master Track had 100% of all channels in other tracks.

I may try removing the Tracks from a copy of the LMS files and see what it does differently.

Update - removed tracks, re-converted. Conversion messages are virtually unchanged; still say I have 2 LOR networks.
Next step may be to remove the undefined channels. A bit more labor intensive.

Can you send me the lms seq you are having trouble with.
Don Gillespie
Medicine Hat Ab.

Offline dkulp

  • Supporting Member
  • Hero Member
  • *
  • Posts: 812
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #7 on: November 20, 2014, 01:29:55 PM »
Could you send me the files as well?  dan@kulp.com

Daniel Kulp
Framingham, MA

Offline sean

  • Administrator
  • Hero Member
  • *****
  • Posts: 1727
    • View Profile
    • Xlights and Nutcracker Forum
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #8 on: November 20, 2014, 01:34:31 PM »
thanks for helping dan! People may not know, Dan is the person who rewrote the xlights LOR conversion this last summer. Many things were improved, fixed. Dan did this even though he does not have LOR.

so , again i say Thanks!

sean
Sean
Littleton, CO
Latest releases http://nutcracker123.com/nutcracker/releases
xLights/Nutcracker Forum http://nutcracker123.com/forum/index.php
Fbook [url=https://www.facebook.com/groups/62

Offline JonB256

  • Hero Member
  • *****
  • Posts: 832
    • View Profile
    • My Christmas Website
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #9 on: November 20, 2014, 02:18:55 PM »
I think it is doing a correct conversion but the LOR Network Messages (since I don't have any) made me ask the question.
I did a test conversion from LMS to XSEQ then back to LMS (of a smaller file) and it got channel numbers (DMX and Pixelnet) correct

JonB

Offline dkulp

  • Supporting Member
  • Hero Member
  • *
  • Posts: 812
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #10 on: November 20, 2014, 02:48:58 PM »

(Sharing with permission after getting the sequence via email mostly to provide information to folks that may be following this)

I’ve include a list of the channels that are going into the two LOR networks. 

There are two types:

1) Channels that explicitly have network=“1” attributes on them.  These look like mostly your floods.   

2) Channels that don’t have any “network” attribute on them.   We currently map these into the first output (if any of these exist) and then map the network=“1” to the second output.   The main reason is that many of the programs that export LMS files (including xLights) don’t write out the network attributes.  We pretty much assume they are all part of first output.  It looks like most of the “timing” and blank channels are falling into there for you.

I’m kind of thinking about adding another checkbox for “Map LOR channels with no network” or similar that we would enable by default (for compatibility), but can easily be disabled.  Thus, the beat channels and such would be ignored.   I need to think about this some more.   Could POSSIBLY assume that if a channel has a network on it someplace, then it’s not one that was written by xLights/Vixen/etc.. that don’t include that and thus automatically drop the channels with no network defined.   I’d be concerned about compatibility though.

The network=1 things are things you would need to resolve though.   In older versions of xLights, they would have been mapped onto output 2 ALONG with DMX channel 1.  The two would overwrite each other and not warn about it or anything.  Thats why it “looked” like it worked OK last year, but in reality, it may not have.   Luckily, almost all your channels in the LOR network=1 are empty so they didn’t overwrite much.






      <channel name="Beat channel" color="12615744" centiseconds="30263" savedIndex="1106">
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1170"/>
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1171"/>
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1172"/>
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1173"/>
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1174"/>
      <channel name="Beat Channel" color="4194368" centiseconds="30263" savedIndex="1191">
      <channel name="Nativity flood" color="16777215" centiseconds="30263" network="1" savedIndex="1204">
      <channel name="blank" color="12615744" centiseconds="30263" savedIndex="1229">
      <channel name="blank" color="16777215" centiseconds="30263" savedIndex="1230">
      <channel name="blank" color="255" centiseconds="30263" savedIndex="1231">
      <channel name="blank" color="0" centiseconds="30263" savedIndex="1234">
      <channel name="blank" color="12615744" centiseconds="30263" savedIndex="1256">
      <channel name="Blank" color="12615744" centiseconds="30263" savedIndex="1261">
      <channel name="beat" color="12615744" centiseconds="30263" savedIndex="1283">
      <channel name="Unit 08.7" color="12615744" centiseconds="30263" savedIndex="1284"/>
      <channel name="Unit 08.6" color="12615744" centiseconds="30263" savedIndex="1285"/>
      <channel name="Unit 08.5" color="12615744" centiseconds="30263" savedIndex="1286"/>
      <channel name="Unit 07.8" color="12615744" centiseconds="30263" savedIndex="1287"/>
      <channel name="Unit 07.7" color="12615744" centiseconds="30263" savedIndex="1288"/>
      <channel name="Unit 07.6" color="12615744" centiseconds="30263" savedIndex="1289"/>
      <channel name="Unit 07.5" color="12615744" centiseconds="30263" savedIndex="1290"/>
      <channel name="Unit 07.4" color="12615744" centiseconds="30263" savedIndex="1291"/>
      <channel name="Unit 07.3" color="12615744" centiseconds="30263" savedIndex="1292"/>
      <channel name="blank" color="12615744" centiseconds="30263" savedIndex="1296"/>
      <channel name="blank" color="12615744" centiseconds="30263" savedIndex="1297">
      <channel name="Blank" color="0" centiseconds="30263" savedIndex="1327">
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1399">
      <channel name="New Channel" color="12615744" centiseconds="30263" savedIndex="1400">
      <channel name="40 Left flood (R)" color="255" centiseconds="30263" network="1" savedIndex="1688"/>
      <channel name="40 Left flood (G)" color="65280" centiseconds="30263" network="1" savedIndex="1689"/>
      <channel name="40 Left flood (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1690"/>
      <channel name="Next Flood over (R)" color="255" centiseconds="30263" network="1" savedIndex="1692"/>
      <channel name="Next Flood over (G)" color="65280" centiseconds="30263" network="1" savedIndex="1693"/>
      <channel name="Next Flood over (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1694"/>
      <channel name="Next Flood Over (R)" color="255" centiseconds="30263" network="1" savedIndex="1696"/>
      <channel name="Next Flood Over (G)" color="65280" centiseconds="30263" network="1" savedIndex="1697"/>
      <channel name="Next Flood Over (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1698"/>
      <channel name="40 Right Flood (R)" color="255" centiseconds="30263" network="1" savedIndex="1700"/>
      <channel name="40 Right Flood (G)" color="65280" centiseconds="30263" network="1" savedIndex="1701"/>
      <channel name="40 Right Flood (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1702"/>
      <channel name="41 Left Flood (R)" color="255" centiseconds="30263" network="1" savedIndex="1704"/>
      <channel name="41 Left Flood (G)" color="65280" centiseconds="30263" network="1" savedIndex="1705"/>
      <channel name="41 Left Flood (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1706"/>
      <channel name="41 Next over (R)" color="255" centiseconds="30263" network="1" savedIndex="1708"/>
      <channel name="41 Next over (G)" color="65280" centiseconds="30263" network="1" savedIndex="1709"/>
      <channel name="41 Next over (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1710"/>
      <channel name="41 Next Over (R)" color="255" centiseconds="30263" network="1" savedIndex="1712"/>
      <channel name="41 Next Over (G)" color="65280" centiseconds="30263" network="1" savedIndex="1713"/>
      <channel name="41 Next Over (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1714"/>
      <channel name="41 Right Flood (R)" color="255" centiseconds="30263" network="1" savedIndex="1716"/>
      <channel name="41 Right Flood (G)" color="65280" centiseconds="30263" network="1" savedIndex="1717"/>
      <channel name="41 Right Flood (B)" color="16711680" centiseconds="30263" network="1" savedIndex="1718"/>
      <channel name="blank" color="12615744" centiseconds="30263" savedIndex="1720"/>
      <channel name="Timing Channel" color="12615744" centiseconds="30263" savedIndex="2251">
Daniel Kulp
Framingham, MA

Offline flyinverted

  • Administrator
  • Hero Member
  • *****
  • Posts: 756
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #11 on: November 20, 2014, 03:17:31 PM »
Dan,

If possible on the next conversion update, if you could ignore the LOR CCR/CCB macro channels, that would be a huge help too.

They look like this in the LMS file.

<channel name="CCR01 - LR" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="151" network="1" savedIndex="216"/>
<channel name="CCR01 - MM" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="152" network="1" savedIndex="217"/>
<channel name="CCR01 - MS" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="153" network="1" savedIndex="218"/>
<channel name="CCR01 - ME" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="154" network="1" savedIndex="219"/>
<channel name="CCR01 - CM" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="155" network="1" savedIndex="220"/>
<channel name="CCR01 - CS" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="156" network="1" savedIndex="221"/>
<channel name="CCR01 - CI" color="12615744" centiseconds="15400" deviceType="LOR" unit="2" circuit="157" network="1" savedIndex="222"/>


Thanks!
Steve
Steve Giron
Maricopa County, AZ
xLights user with a boat-load of channels.

Do not ask to know all the answers, but ask to understand the question.

Offline jeffl

  • Full Member
  • ***
  • Posts: 146
    • View Profile
Re: Convert from LOR/LMS to XSEQ giving unexpected messages
« Reply #12 on: November 26, 2014, 07:41:02 PM »
I did a quick test and everything worked good after I stripped out the tracks and empty channels (what I call separators).  From a conversion standpoint, it would be nice if theses items could just be ignored during the conversion.